Skip to content

Repository files navigation

RDrive - Rust Dynamic Driver Framework

A dynamic driver management framework for embedded systems written in Rust.

Architecture Overview

rdif-* Interface Crates

Hardware abstraction interface crates with Any for dynamic dispatch:

  • rdif-base: Core driver traits and error types
  • rdif-intc: Interrupt controller interface
  • rdif-clk: Clock management interface
  • rdif-serial: Serial communication interface
  • rdif-timer: Timer/counter interface
  • rdif-block: Block device interface
  • rdif-power: Power management interface
  • rdif-systick: System tick interface
  • rdif-net: Network interface

rdrive-macros

Procedural macros to simplify driver registration and module generation.

rdrive Core

The main driver container responsible for:

  • Driver registration and discovery
  • Device probing and initialization
  • Device lifecycle management
  • Type-safe device access

Device Ownership Model

Devices are managed through a long-term borrowing model using Device<T> wrappers. Unlike Mutex<T>, when a task borrows a device, it gains exclusive ownership. Other tasks attempting to borrow will receive an error with the owner's task ID, enabling forced task termination if needed.

Key features:

  • Lock-free operations once ownership is acquired
  • Weak pointer support for interrupt handlers
  • Cloning Device<T> creates weak references for fast indexing

Driver Registration

Drivers can be registered from different crates using the module_driver! macro:

use rdrive::{
module_driver,
register::{ProbeKind,ProbeLevel,ProbePriority,FdtInfo},
probe::OnProbeError,PlatformDevice,DriverGeneric,};structGicV3Driver{// Driver implementation}implDriverGenericforGicV3Driver{fnopen(&mutself) -> Result<(), rdrive::KError>{// Initialize hardwareOk(())}fnclose(&mutself) -> Result<(), rdrive::KError>{// Cleanup hardwareOk(())}}impl rdrive::driver::intc::InterfaceforGicV3Driver{// Implement interrupt controller interfacefnenable_irq(&mutself,irq: rdrive::IrqId) -> Result<(), rdrive::driver::intc::IntcError>{// Enable interrupt implementationOk(())}// ... other required methods}fnprobe_gicv3(fdt:FdtInfo<'_>,dev:PlatformDevice) -> Result<(),OnProbeError>{let node = fdt.node;letmut reg = node.reg().ok_or("No reg property")?;let gicd_reg = reg.next().ok_or("Missing GICD register")?;let gicr_reg = reg.next().ok_or("Missing GICR register")?;let driver = GicV3Driver::new(
gicd_reg.addressasusize,
gicr_reg.addressasusize,);
dev.register(driver);Ok(())}module_driver!{
name:"GICv3",
level:ProbeLevel::PreKernel,
priority:ProbePriority::INTC,
probe_kinds:&[ProbeKind::Fdt{
compatibles:&["arm,gic-v3"],
on_probe: probe_gicv3,}],}

System Integration

1. Linker Script Configuration

Add the following section to your linker script:

.driver.register : ALIGN(4K) {
_sdriver = .;
*(.driver.register .driver.register.*)
_edriver = .;
. = ALIGN(4K);
}

2. Driver Registration Discovery

use rdrive::register::DriverRegisterSlice;fndriver_registers() -> &'static[u8]{unsafeextern"C"{fn_sdriver();fn_edriver();}unsafe{ core::slice::from_raw_parts(
_sdriver as*constu8, _edriver asusize - _sdriver asusize)}}fnget_driver_registers() -> DriverRegisterSlice{DriverRegisterSlice::from_raw(driver_registers())}

3. System Initialization

use rdrive::{Platform, probe_pre_kernel, probe_all};use core::ptr::NonNull;fninit_drivers(){// Initialize with device treelet fdt_addr = /* device tree address */;let platform = Platform::Fdt{addr:NonNull::new(fdt_addr).unwrap(),};// Initialize the driver framework
rdrive::init(platform).unwrap();// Register all discovered drivers
rdrive::register_append(get_driver_registers().as_slice());// Probe critical drivers first (interrupt controllers, etc.)
rdrive::probe_pre_kernel().unwrap();// Initialize interrupt system// irq::init_main_cpu();// Probe remaining drivers
rdrive::probe_all(false).unwrap();// false = don't stop on failures}

4. Device Access

use rdrive::{get_list, get_one, driver::Intc};fnuse_devices(){// Get all interrupt controllerslet intc_list = get_list::<Intc>();for intc in intc_list {println!("Found INTC: {:?}", intc.descriptor());}// Get the first available interrupt controllerifletSome(intc) = get_one::<Intc>(){// Use the device - this gives exclusive accessmatch intc.try_lock(){Ok(mut locked_intc) => {// Safe to use locked_intc without additional synchronization
locked_intc.enable_irq(42.into()).unwrap();}Err(owner_id) => {println!("Device busy, owned by task: {:?}", owner_id);}}}}

Supported Probe Methods

  • Device Tree (FDT): Automatic device discovery from device tree
  • Static Configuration: Manual device registration (planned)

Examples

See the examples/ directory for complete usage examples:

  • examples/enumerate/: Basic driver enumeration and device tree parsing

References

For complete integration examples, see:

About

A rust dyn driver manager.

Resources

Stars

3 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
GitHub - drivercraft/rdrive: A rust dyn driver manager. · GitHub
Skip to content

Repository files navigation

RDrive - Rust Dynamic Driver Framework

A dynamic driver management framework for embedded systems written in Rust.

Architecture Overview

rdif-* Interface Crates

Hardware abstraction interface crates with Any for dynamic dispatch:

  • rdif-base: Core driver traits and error types
  • rdif-intc: Interrupt controller interface
  • rdif-clk: Clock management interface
  • rdif-serial: Serial communication interface
  • rdif-timer: Timer/counter interface
  • rdif-block: Block device interface
  • rdif-power: Power management interface
  • rdif-systick: System tick interface
  • rdif-net: Network interface

rdrive-macros

Procedural macros to simplify driver registration and module generation.

rdrive Core

The main driver container responsible for:

  • Driver registration and discovery
  • Device probing and initialization
  • Device lifecycle management
  • Type-safe device access

Device Ownership Model

Devices are managed through a long-term borrowing model using Device<T> wrappers. Unlike Mutex<T>, when a task borrows a device, it gains exclusive ownership. Other tasks attempting to borrow will receive an error with the owner's task ID, enabling forced task termination if needed.

Key features:

  • Lock-free operations once ownership is acquired
  • Weak pointer support for interrupt handlers
  • Cloning Device<T> creates weak references for fast indexing

Driver Registration

Drivers can be registered from different crates using the module_driver! macro:

use rdrive::{
module_driver,
register::{ProbeKind,ProbeLevel,ProbePriority,FdtInfo},
probe::OnProbeError,PlatformDevice,DriverGeneric,};structGicV3Driver{// Driver implementation}implDriverGenericforGicV3Driver{fnopen(&mutself) -> Result<(), rdrive::KError>{// Initialize hardwareOk(())}fnclose(&mutself) -> Result<(), rdrive::KError>{// Cleanup hardwareOk(())}}impl rdrive::driver::intc::InterfaceforGicV3Driver{// Implement interrupt controller interfacefnenable_irq(&mutself,irq: rdrive::IrqId) -> Result<(), rdrive::driver::intc::IntcError>{// Enable interrupt implementationOk(())}// ... other required methods}fnprobe_gicv3(fdt:FdtInfo<'_>,dev:PlatformDevice) -> Result<(),OnProbeError>{let node = fdt.node;letmut reg = node.reg().ok_or("No reg property")?;let gicd_reg = reg.next().ok_or("Missing GICD register")?;let gicr_reg = reg.next().ok_or("Missing GICR register")?;let driver = GicV3Driver::new(
gicd_reg.addressasusize,
gicr_reg.addressasusize,);
dev.register(driver);Ok(())}module_driver!{
name:"GICv3",
level:ProbeLevel::PreKernel,
priority:ProbePriority::INTC,
probe_kinds:&[ProbeKind::Fdt{
compatibles:&["arm,gic-v3"],
on_probe: probe_gicv3,}],}

System Integration

1. Linker Script Configuration

Add the following section to your linker script:

.driver.register : ALIGN(4K) {
_sdriver = .;
*(.driver.register .driver.register.*)
_edriver = .;
. = ALIGN(4K);
}

2. Driver Registration Discovery

use rdrive::register::DriverRegisterSlice;fndriver_registers() -> &'static[u8]{unsafeextern"C"{fn_sdriver();fn_edriver();}unsafe{ core::slice::from_raw_parts(
_sdriver as*constu8, _edriver asusize - _sdriver asusize)}}fnget_driver_registers() -> DriverRegisterSlice{DriverRegisterSlice::from_raw(driver_registers())}

3. System Initialization

use rdrive::{Platform, probe_pre_kernel, probe_all};use core::ptr::NonNull;fninit_drivers(){// Initialize with device treelet fdt_addr = /* device tree address */;let platform = Platform::Fdt{addr:NonNull::new(fdt_addr).unwrap(),};// Initialize the driver framework
rdrive::init(platform).unwrap();// Register all discovered drivers
rdrive::register_append(get_driver_registers().as_slice());// Probe critical drivers first (interrupt controllers, etc.)
rdrive::probe_pre_kernel().unwrap();// Initialize interrupt system// irq::init_main_cpu();// Probe remaining drivers
rdrive::probe_all(false).unwrap();// false = don't stop on failures}

4. Device Access

use rdrive::{get_list, get_one, driver::Intc};fnuse_devices(){// Get all interrupt controllerslet intc_list = get_list::<Intc>();for intc in intc_list {println!("Found INTC: {:?}", intc.descriptor());}// Get the first available interrupt controllerifletSome(intc) = get_one::<Intc>(){// Use the device - this gives exclusive accessmatch intc.try_lock(){Ok(mut locked_intc) => {// Safe to use locked_intc without additional synchronization
locked_intc.enable_irq(42.into()).unwrap();}Err(owner_id) => {println!("Device busy, owned by task: {:?}", owner_id);}}}}

Supported Probe Methods

  • Device Tree (FDT): Automatic device discovery from device tree
  • Static Configuration: Manual device registration (planned)

Examples

See the examples/ directory for complete usage examples:

  • examples/enumerate/: Basic driver enumeration and device tree parsing

References

For complete integration examples, see:

About

A rust dyn driver manager.

Resources

Stars

3 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - drivercraft/rdrive: A rust dyn driver manager. · GitHub
Skip to content

Repository files navigation

RDrive - Rust Dynamic Driver Framework

A dynamic driver management framework for embedded systems written in Rust.

Architecture Overview

rdif-* Interface Crates

Hardware abstraction interface crates with Any for dynamic dispatch:

  • rdif-base: Core driver traits and error types
  • rdif-intc: Interrupt controller interface
  • rdif-clk: Clock management interface
  • rdif-serial: Serial communication interface
  • rdif-timer: Timer/counter interface
  • rdif-block: Block device interface
  • rdif-power: Power management interface
  • rdif-systick: System tick interface
  • rdif-net: Network interface

rdrive-macros

Procedural macros to simplify driver registration and module generation.

rdrive Core

The main driver container responsible for:

  • Driver registration and discovery
  • Device probing and initialization
  • Device lifecycle management
  • Type-safe device access

Device Ownership Model

Devices are managed through a long-term borrowing model using Device<T> wrappers. Unlike Mutex<T>, when a task borrows a device, it gains exclusive ownership. Other tasks attempting to borrow will receive an error with the owner's task ID, enabling forced task termination if needed.

Key features:

  • Lock-free operations once ownership is acquired
  • Weak pointer support for interrupt handlers
  • Cloning Device<T> creates weak references for fast indexing

Driver Registration

Drivers can be registered from different crates using the module_driver! macro:

use rdrive::{
module_driver,
register::{ProbeKind,ProbeLevel,ProbePriority,FdtInfo},
probe::OnProbeError,PlatformDevice,DriverGeneric,};structGicV3Driver{// Driver implementation}implDriverGenericforGicV3Driver{fnopen(&mutself) -> Result<(), rdrive::KError>{// Initialize hardwareOk(())}fnclose(&mutself) -> Result<(), rdrive::KError>{// Cleanup hardwareOk(())}}impl rdrive::driver::intc::InterfaceforGicV3Driver{// Implement interrupt controller interfacefnenable_irq(&mutself,irq: rdrive::IrqId) -> Result<(), rdrive::driver::intc::IntcError>{// Enable interrupt implementationOk(())}// ... other required methods}fnprobe_gicv3(fdt:FdtInfo<'_>,dev:PlatformDevice) -> Result<(),OnProbeError>{let node = fdt.node;letmut reg = node.reg().ok_or("No reg property")?;let gicd_reg = reg.next().ok_or("Missing GICD register")?;let gicr_reg = reg.next().ok_or("Missing GICR register")?;let driver = GicV3Driver::new(
gicd_reg.addressasusize,
gicr_reg.addressasusize,);
dev.register(driver);Ok(())}module_driver!{
name:"GICv3",
level:ProbeLevel::PreKernel,
priority:ProbePriority::INTC,
probe_kinds:&[ProbeKind::Fdt{
compatibles:&["arm,gic-v3"],
on_probe: probe_gicv3,}],}

System Integration

1. Linker Script Configuration

Add the following section to your linker script:

.driver.register : ALIGN(4K) {
_sdriver = .;
*(.driver.register .driver.register.*)
_edriver = .;
. = ALIGN(4K);
}

2. Driver Registration Discovery

use rdrive::register::DriverRegisterSlice;fndriver_registers() -> &'static[u8]{unsafeextern"C"{fn_sdriver();fn_edriver();}unsafe{ core::slice::from_raw_parts(
_sdriver as*constu8, _edriver asusize - _sdriver asusize)}}fnget_driver_registers() -> DriverRegisterSlice{DriverRegisterSlice::from_raw(driver_registers())}

3. System Initialization

use rdrive::{Platform, probe_pre_kernel, probe_all};use core::ptr::NonNull;fninit_drivers(){// Initialize with device treelet fdt_addr = /* device tree address */;let platform = Platform::Fdt{addr:NonNull::new(fdt_addr).unwrap(),};// Initialize the driver framework
rdrive::init(platform).unwrap();// Register all discovered drivers
rdrive::register_append(get_driver_registers().as_slice());// Probe critical drivers first (interrupt controllers, etc.)
rdrive::probe_pre_kernel().unwrap();// Initialize interrupt system// irq::init_main_cpu();// Probe remaining drivers
rdrive::probe_all(false).unwrap();// false = don't stop on failures}

4. Device Access

use rdrive::{get_list, get_one, driver::Intc};fnuse_devices(){// Get all interrupt controllerslet intc_list = get_list::<Intc>();for intc in intc_list {println!("Found INTC: {:?}", intc.descriptor());}// Get the first available interrupt controllerifletSome(intc) = get_one::<Intc>(){// Use the device - this gives exclusive accessmatch intc.try_lock(){Ok(mut locked_intc) => {// Safe to use locked_intc without additional synchronization
locked_intc.enable_irq(42.into()).unwrap();}Err(owner_id) => {println!("Device busy, owned by task: {:?}", owner_id);}}}}

Supported Probe Methods

  • Device Tree (FDT): Automatic device discovery from device tree
  • Static Configuration: Manual device registration (planned)

Examples

See the examples/ directory for complete usage examples:

  • examples/enumerate/: Basic driver enumeration and device tree parsing

References

For complete integration examples, see:

About

A rust dyn driver manager.

Resources

Stars

3 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - drivercraft/rdrive: A rust dyn driver manager. · GitHub
Skip to content

Repository files navigation

RDrive - Rust Dynamic Driver Framework

A dynamic driver management framework for embedded systems written in Rust.

Architecture Overview

rdif-* Interface Crates

Hardware abstraction interface crates with Any for dynamic dispatch:

  • rdif-base: Core driver traits and error types
  • rdif-intc: Interrupt controller interface
  • rdif-clk: Clock management interface
  • rdif-serial: Serial communication interface
  • rdif-timer: Timer/counter interface
  • rdif-block: Block device interface
  • rdif-power: Power management interface
  • rdif-systick: System tick interface
  • rdif-net: Network interface

rdrive-macros

Procedural macros to simplify driver registration and module generation.

rdrive Core

The main driver container responsible for:

  • Driver registration and discovery
  • Device probing and initialization
  • Device lifecycle management
  • Type-safe device access

Device Ownership Model

Devices are managed through a long-term borrowing model using Device<T> wrappers. Unlike Mutex<T>, when a task borrows a device, it gains exclusive ownership. Other tasks attempting to borrow will receive an error with the owner's task ID, enabling forced task termination if needed.

Key features:

  • Lock-free operations once ownership is acquired
  • Weak pointer support for interrupt handlers
  • Cloning Device<T> creates weak references for fast indexing

Driver Registration

Drivers can be registered from different crates using the module_driver! macro:

use rdrive::{
module_driver,
register::{ProbeKind,ProbeLevel,ProbePriority,FdtInfo},
probe::OnProbeError,PlatformDevice,DriverGeneric,};structGicV3Driver{// Driver implementation}implDriverGenericforGicV3Driver{fnopen(&mutself) -> Result<(), rdrive::KError>{// Initialize hardwareOk(())}fnclose(&mutself) -> Result<(), rdrive::KError>{// Cleanup hardwareOk(())}}impl rdrive::driver::intc::InterfaceforGicV3Driver{// Implement interrupt controller interfacefnenable_irq(&mutself,irq: rdrive::IrqId) -> Result<(), rdrive::driver::intc::IntcError>{// Enable interrupt implementationOk(())}// ... other required methods}fnprobe_gicv3(fdt:FdtInfo<'_>,dev:PlatformDevice) -> Result<(),OnProbeError>{let node = fdt.node;letmut reg = node.reg().ok_or("No reg property")?;let gicd_reg = reg.next().ok_or("Missing GICD register")?;let gicr_reg = reg.next().ok_or("Missing GICR register")?;let driver = GicV3Driver::new(
gicd_reg.addressasusize,
gicr_reg.addressasusize,);
dev.register(driver);Ok(())}module_driver!{
name:"GICv3",
level:ProbeLevel::PreKernel,
priority:ProbePriority::INTC,
probe_kinds:&[ProbeKind::Fdt{
compatibles:&["arm,gic-v3"],
on_probe: probe_gicv3,}],}

System Integration

1. Linker Script Configuration

Add the following section to your linker script:

.driver.register : ALIGN(4K) {
_sdriver = .;
*(.driver.register .driver.register.*)
_edriver = .;
. = ALIGN(4K);
}

2. Driver Registration Discovery

use rdrive::register::DriverRegisterSlice;fndriver_registers() -> &'static[u8]{unsafeextern"C"{fn_sdriver();fn_edriver();}unsafe{ core::slice::from_raw_parts(
_sdriver as*constu8, _edriver asusize - _sdriver asusize)}}fnget_driver_registers() -> DriverRegisterSlice{DriverRegisterSlice::from_raw(driver_registers())}

3. System Initialization

use rdrive::{Platform, probe_pre_kernel, probe_all};use core::ptr::NonNull;fninit_drivers(){// Initialize with device treelet fdt_addr = /* device tree address */;let platform = Platform::Fdt{addr:NonNull::new(fdt_addr).unwrap(),};// Initialize the driver framework
rdrive::init(platform).unwrap();// Register all discovered drivers
rdrive::register_append(get_driver_registers().as_slice());// Probe critical drivers first (interrupt controllers, etc.)
rdrive::probe_pre_kernel().unwrap();// Initialize interrupt system// irq::init_main_cpu();// Probe remaining drivers
rdrive::probe_all(false).unwrap();// false = don't stop on failures}

4. Device Access

use rdrive::{get_list, get_one, driver::Intc};fnuse_devices(){// Get all interrupt controllerslet intc_list = get_list::<Intc>();for intc in intc_list {println!("Found INTC: {:?}", intc.descriptor());}// Get the first available interrupt controllerifletSome(intc) = get_one::<Intc>(){// Use the device - this gives exclusive accessmatch intc.try_lock(){Ok(mut locked_intc) => {// Safe to use locked_intc without additional synchronization
locked_intc.enable_irq(42.into()).unwrap();}Err(owner_id) => {println!("Device busy, owned by task: {:?}", owner_id);}}}}

Supported Probe Methods

  • Device Tree (FDT): Automatic device discovery from device tree
  • Static Configuration: Manual device registration (planned)

Examples

See the examples/ directory for complete usage examples:

  • examples/enumerate/: Basic driver enumeration and device tree parsing

References

For complete integration examples, see:

About

A rust dyn driver manager.

Resources

Stars

3 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' GitHub - drivercraft/rdrive: A rust dyn driver manager. · GitHub
Skip to content

Repository files navigation

RDrive - Rust Dynamic Driver Framework

A dynamic driver management framework for embedded systems written in Rust.

Architecture Overview

rdif-* Interface Crates

Hardware abstraction interface crates with Any for dynamic dispatch:

  • rdif-base: Core driver traits and error types
  • rdif-intc: Interrupt controller interface
  • rdif-clk: Clock management interface
  • rdif-serial: Serial communication interface
  • rdif-timer: Timer/counter interface
  • rdif-block: Block device interface
  • rdif-power: Power management interface
  • rdif-systick: System tick interface
  • rdif-net: Network interface

rdrive-macros

Procedural macros to simplify driver registration and module generation.

rdrive Core

The main driver container responsible for:

  • Driver registration and discovery
  • Device probing and initialization
  • Device lifecycle management
  • Type-safe device access

Device Ownership Model

Devices are managed through a long-term borrowing model using Device<T> wrappers. Unlike Mutex<T>, when a task borrows a device, it gains exclusive ownership. Other tasks attempting to borrow will receive an error with the owner's task ID, enabling forced task termination if needed.

Key features:

  • Lock-free operations once ownership is acquired
  • Weak pointer support for interrupt handlers
  • Cloning Device<T> creates weak references for fast indexing

Driver Registration

Drivers can be registered from different crates using the module_driver! macro:

use rdrive::{
module_driver,
register::{ProbeKind,ProbeLevel,ProbePriority,FdtInfo},
probe::OnProbeError,PlatformDevice,DriverGeneric,};structGicV3Driver{// Driver implementation}implDriverGenericforGicV3Driver{fnopen(&mutself) -> Result<(), rdrive::KError>{// Initialize hardwareOk(())}fnclose(&mutself) -> Result<(), rdrive::KError>{// Cleanup hardwareOk(())}}impl rdrive::driver::intc::InterfaceforGicV3Driver{// Implement interrupt controller interfacefnenable_irq(&mutself,irq: rdrive::IrqId) -> Result<(), rdrive::driver::intc::IntcError>{// Enable interrupt implementationOk(())}// ... other required methods}fnprobe_gicv3(fdt:FdtInfo<'_>,dev:PlatformDevice) -> Result<(),OnProbeError>{let node = fdt.node;letmut reg = node.reg().ok_or("No reg property")?;let gicd_reg = reg.next().ok_or("Missing GICD register")?;let gicr_reg = reg.next().ok_or("Missing GICR register")?;let driver = GicV3Driver::new(
gicd_reg.addressasusize,
gicr_reg.addressasusize,);
dev.register(driver);Ok(())}module_driver!{
name:"GICv3",
level:ProbeLevel::PreKernel,
priority:ProbePriority::INTC,
probe_kinds:&[ProbeKind::Fdt{
compatibles:&["arm,gic-v3"],
on_probe: probe_gicv3,}],}

System Integration

1. Linker Script Configuration

Add the following section to your linker script:

.driver.register : ALIGN(4K) {
_sdriver = .;
*(.driver.register .driver.register.*)
_edriver = .;
. = ALIGN(4K);
}

2. Driver Registration Discovery

use rdrive::register::DriverRegisterSlice;fndriver_registers() -> &'static[u8]{unsafeextern"C"{fn_sdriver();fn_edriver();}unsafe{ core::slice::from_raw_parts(
_sdriver as*constu8, _edriver asusize - _sdriver asusize)}}fnget_driver_registers() -> DriverRegisterSlice{DriverRegisterSlice::from_raw(driver_registers())}

3. System Initialization

use rdrive::{Platform, probe_pre_kernel, probe_all};use core::ptr::NonNull;fninit_drivers(){// Initialize with device treelet fdt_addr = /* device tree address */;let platform = Platform::Fdt{addr:NonNull::new(fdt_addr).unwrap(),};// Initialize the driver framework
rdrive::init(platform).unwrap();// Register all discovered drivers
rdrive::register_append(get_driver_registers().as_slice());// Probe critical drivers first (interrupt controllers, etc.)
rdrive::probe_pre_kernel().unwrap();// Initialize interrupt system// irq::init_main_cpu();// Probe remaining drivers
rdrive::probe_all(false).unwrap();// false = don't stop on failures}

4. Device Access

use rdrive::{get_list, get_one, driver::Intc};fnuse_devices(){// Get all interrupt controllerslet intc_list = get_list::<Intc>();for intc in intc_list {println!("Found INTC: {:?}", intc.descriptor());}// Get the first available interrupt controllerifletSome(intc) = get_one::<Intc>(){// Use the device - this gives exclusive accessmatch intc.try_lock(){Ok(mut locked_intc) => {// Safe to use locked_intc without additional synchronization
locked_intc.enable_irq(42.into()).unwrap();}Err(owner_id) => {println!("Device busy, owned by task: {:?}", owner_id);}}}}

Supported Probe Methods

  • Device Tree (FDT): Automatic device discovery from device tree
  • Static Configuration: Manual device registration (planned)

Examples

See the examples/ directory for complete usage examples:

  • examples/enumerate/: Basic driver enumeration and device tree parsing

References

For complete integration examples, see:

About

A rust dyn driver manager.

Resources

Stars

3 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - drivercraft/rdrive: A rust dyn driver manager. · GitHub
Skip to content

Repository files navigation

RDrive - Rust Dynamic Driver Framework

A dynamic driver management framework for embedded systems written in Rust.

Architecture Overview

rdif-* Interface Crates

Hardware abstraction interface crates with Any for dynamic dispatch:

  • rdif-base: Core driver traits and error types
  • rdif-intc: Interrupt controller interface
  • rdif-clk: Clock management interface
  • rdif-serial: Serial communication interface
  • rdif-timer: Timer/counter interface
  • rdif-block: Block device interface
  • rdif-power: Power management interface
  • rdif-systick: System tick interface
  • rdif-net: Network interface

rdrive-macros

Procedural macros to simplify driver registration and module generation.

rdrive Core

The main driver container responsible for:

  • Driver registration and discovery
  • Device probing and initialization
  • Device lifecycle management
  • Type-safe device access

Device Ownership Model

Devices are managed through a long-term borrowing model using Device<T> wrappers. Unlike Mutex<T>, when a task borrows a device, it gains exclusive ownership. Other tasks attempting to borrow will receive an error with the owner's task ID, enabling forced task termination if needed.

Key features:

  • Lock-free operations once ownership is acquired
  • Weak pointer support for interrupt handlers
  • Cloning Device<T> creates weak references for fast indexing

Driver Registration

Drivers can be registered from different crates using the module_driver! macro:

use rdrive::{
module_driver,
register::{ProbeKind,ProbeLevel,ProbePriority,FdtInfo},
probe::OnProbeError,PlatformDevice,DriverGeneric,};structGicV3Driver{// Driver implementation}implDriverGenericforGicV3Driver{fnopen(&mutself) -> Result<(), rdrive::KError>{// Initialize hardwareOk(())}fnclose(&mutself) -> Result<(), rdrive::KError>{// Cleanup hardwareOk(())}}impl rdrive::driver::intc::InterfaceforGicV3Driver{// Implement interrupt controller interfacefnenable_irq(&mutself,irq: rdrive::IrqId) -> Result<(), rdrive::driver::intc::IntcError>{// Enable interrupt implementationOk(())}// ... other required methods}fnprobe_gicv3(fdt:FdtInfo<'_>,dev:PlatformDevice) -> Result<(),OnProbeError>{let node = fdt.node;letmut reg = node.reg().ok_or("No reg property")?;let gicd_reg = reg.next().ok_or("Missing GICD register")?;let gicr_reg = reg.next().ok_or("Missing GICR register")?;let driver = GicV3Driver::new(
gicd_reg.addressasusize,
gicr_reg.addressasusize,);
dev.register(driver);Ok(())}module_driver!{
name:"GICv3",
level:ProbeLevel::PreKernel,
priority:ProbePriority::INTC,
probe_kinds:&[ProbeKind::Fdt{
compatibles:&["arm,gic-v3"],
on_probe: probe_gicv3,}],}

System Integration

1. Linker Script Configuration

Add the following section to your linker script:

.driver.register : ALIGN(4K) {
_sdriver = .;
*(.driver.register .driver.register.*)
_edriver = .;
. = ALIGN(4K);
}

2. Driver Registration Discovery

use rdrive::register::DriverRegisterSlice;fndriver_registers() -> &'static[u8]{unsafeextern"C"{fn_sdriver();fn_edriver();}unsafe{ core::slice::from_raw_parts(
_sdriver as*constu8, _edriver asusize - _sdriver asusize)}}fnget_driver_registers() -> DriverRegisterSlice{DriverRegisterSlice::from_raw(driver_registers())}

3. System Initialization

use rdrive::{Platform, probe_pre_kernel, probe_all};use core::ptr::NonNull;fninit_drivers(){// Initialize with device treelet fdt_addr = /* device tree address */;let platform = Platform::Fdt{addr:NonNull::new(fdt_addr).unwrap(),};// Initialize the driver framework
rdrive::init(platform).unwrap();// Register all discovered drivers
rdrive::register_append(get_driver_registers().as_slice());// Probe critical drivers first (interrupt controllers, etc.)
rdrive::probe_pre_kernel().unwrap();// Initialize interrupt system// irq::init_main_cpu();// Probe remaining drivers
rdrive::probe_all(false).unwrap();// false = don't stop on failures}

4. Device Access

use rdrive::{get_list, get_one, driver::Intc};fnuse_devices(){// Get all interrupt controllerslet intc_list = get_list::<Intc>();for intc in intc_list {println!("Found INTC: {:?}", intc.descriptor());}// Get the first available interrupt controllerifletSome(intc) = get_one::<Intc>(){// Use the device - this gives exclusive accessmatch intc.try_lock(){Ok(mut locked_intc) => {// Safe to use locked_intc without additional synchronization
locked_intc.enable_irq(42.into()).unwrap();}Err(owner_id) => {println!("Device busy, owned by task: {:?}", owner_id);}}}}

Supported Probe Methods

  • Device Tree (FDT): Automatic device discovery from device tree
  • Static Configuration: Manual device registration (planned)

Examples

See the examples/ directory for complete usage examples:

  • examples/enumerate/: Basic driver enumeration and device tree parsing

References

For complete integration examples, see:

About

A rust dyn driver manager.

Resources

Stars

3 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - drivercraft/rdrive: A rust dyn driver manager. · GitHub
Skip to content

Repository files navigation

RDrive - Rust Dynamic Driver Framework

A dynamic driver management framework for embedded systems written in Rust.

Architecture Overview

rdif-* Interface Crates

Hardware abstraction interface crates with Any for dynamic dispatch:

  • rdif-base: Core driver traits and error types
  • rdif-intc: Interrupt controller interface
  • rdif-clk: Clock management interface
  • rdif-serial: Serial communication interface
  • rdif-timer: Timer/counter interface
  • rdif-block: Block device interface
  • rdif-power: Power management interface
  • rdif-systick: System tick interface
  • rdif-net: Network interface

rdrive-macros

Procedural macros to simplify driver registration and module generation.

rdrive Core

The main driver container responsible for:

  • Driver registration and discovery
  • Device probing and initialization
  • Device lifecycle management
  • Type-safe device access

Device Ownership Model

Devices are managed through a long-term borrowing model using Device<T> wrappers. Unlike Mutex<T>, when a task borrows a device, it gains exclusive ownership. Other tasks attempting to borrow will receive an error with the owner's task ID, enabling forced task termination if needed.

Key features:

  • Lock-free operations once ownership is acquired
  • Weak pointer support for interrupt handlers
  • Cloning Device<T> creates weak references for fast indexing

Driver Registration

Drivers can be registered from different crates using the module_driver! macro:

use rdrive::{
module_driver,
register::{ProbeKind,ProbeLevel,ProbePriority,FdtInfo},
probe::OnProbeError,PlatformDevice,DriverGeneric,};structGicV3Driver{// Driver implementation}implDriverGenericforGicV3Driver{fnopen(&mutself) -> Result<(), rdrive::KError>{// Initialize hardwareOk(())}fnclose(&mutself) -> Result<(), rdrive::KError>{// Cleanup hardwareOk(())}}impl rdrive::driver::intc::InterfaceforGicV3Driver{// Implement interrupt controller interfacefnenable_irq(&mutself,irq: rdrive::IrqId) -> Result<(), rdrive::driver::intc::IntcError>{// Enable interrupt implementationOk(())}// ... other required methods}fnprobe_gicv3(fdt:FdtInfo<'_>,dev:PlatformDevice) -> Result<(),OnProbeError>{let node = fdt.node;letmut reg = node.reg().ok_or("No reg property")?;let gicd_reg = reg.next().ok_or("Missing GICD register")?;let gicr_reg = reg.next().ok_or("Missing GICR register")?;let driver = GicV3Driver::new(
gicd_reg.addressasusize,
gicr_reg.addressasusize,);
dev.register(driver);Ok(())}module_driver!{
name:"GICv3",
level:ProbeLevel::PreKernel,
priority:ProbePriority::INTC,
probe_kinds:&[ProbeKind::Fdt{
compatibles:&["arm,gic-v3"],
on_probe: probe_gicv3,}],}

System Integration

1. Linker Script Configuration

Add the following section to your linker script:

.driver.register : ALIGN(4K) {
_sdriver = .;
*(.driver.register .driver.register.*)
_edriver = .;
. = ALIGN(4K);
}

2. Driver Registration Discovery

use rdrive::register::DriverRegisterSlice;fndriver_registers() -> &'static[u8]{unsafeextern"C"{fn_sdriver();fn_edriver();}unsafe{ core::slice::from_raw_parts(
_sdriver as*constu8, _edriver asusize - _sdriver asusize)}}fnget_driver_registers() -> DriverRegisterSlice{DriverRegisterSlice::from_raw(driver_registers())}

3. System Initialization

use rdrive::{Platform, probe_pre_kernel, probe_all};use core::ptr::NonNull;fninit_drivers(){// Initialize with device treelet fdt_addr = /* device tree address */;let platform = Platform::Fdt{addr:NonNull::new(fdt_addr).unwrap(),};// Initialize the driver framework
rdrive::init(platform).unwrap();// Register all discovered drivers
rdrive::register_append(get_driver_registers().as_slice());// Probe critical drivers first (interrupt controllers, etc.)
rdrive::probe_pre_kernel().unwrap();// Initialize interrupt system// irq::init_main_cpu();// Probe remaining drivers
rdrive::probe_all(false).unwrap();// false = don't stop on failures}

4. Device Access

use rdrive::{get_list, get_one, driver::Intc};fnuse_devices(){// Get all interrupt controllerslet intc_list = get_list::<Intc>();for intc in intc_list {println!("Found INTC: {:?}", intc.descriptor());}// Get the first available interrupt controllerifletSome(intc) = get_one::<Intc>(){// Use the device - this gives exclusive accessmatch intc.try_lock(){Ok(mut locked_intc) => {// Safe to use locked_intc without additional synchronization
locked_intc.enable_irq(42.into()).unwrap();}Err(owner_id) => {println!("Device busy, owned by task: {:?}", owner_id);}}}}

Supported Probe Methods

  • Device Tree (FDT): Automatic device discovery from device tree
  • Static Configuration: Manual device registration (planned)

Examples

See the examples/ directory for complete usage examples:

  • examples/enumerate/: Basic driver enumeration and device tree parsing

References

For complete integration examples, see:

About

A rust dyn driver manager.

Resources

Stars

3 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); GitHub - drivercraft/rdrive: A rust dyn driver manager. · GitHub
Skip to content

Repository files navigation

RDrive - Rust Dynamic Driver Framework

A dynamic driver management framework for embedded systems written in Rust.

Architecture Overview

rdif-* Interface Crates

Hardware abstraction interface crates with Any for dynamic dispatch:

  • rdif-base: Core driver traits and error types
  • rdif-intc: Interrupt controller interface
  • rdif-clk: Clock management interface
  • rdif-serial: Serial communication interface
  • rdif-timer: Timer/counter interface
  • rdif-block: Block device interface
  • rdif-power: Power management interface
  • rdif-systick: System tick interface
  • rdif-net: Network interface

rdrive-macros

Procedural macros to simplify driver registration and module generation.

rdrive Core

The main driver container responsible for:

  • Driver registration and discovery
  • Device probing and initialization
  • Device lifecycle management
  • Type-safe device access

Device Ownership Model

Devices are managed through a long-term borrowing model using Device<T> wrappers. Unlike Mutex<T>, when a task borrows a device, it gains exclusive ownership. Other tasks attempting to borrow will receive an error with the owner's task ID, enabling forced task termination if needed.

Key features:

  • Lock-free operations once ownership is acquired
  • Weak pointer support for interrupt handlers
  • Cloning Device<T> creates weak references for fast indexing

Driver Registration

Drivers can be registered from different crates using the module_driver! macro:

use rdrive::{
module_driver,
register::{ProbeKind,ProbeLevel,ProbePriority,FdtInfo},
probe::OnProbeError,PlatformDevice,DriverGeneric,};structGicV3Driver{// Driver implementation}implDriverGenericforGicV3Driver{fnopen(&mutself) -> Result<(), rdrive::KError>{// Initialize hardwareOk(())}fnclose(&mutself) -> Result<(), rdrive::KError>{// Cleanup hardwareOk(())}}impl rdrive::driver::intc::InterfaceforGicV3Driver{// Implement interrupt controller interfacefnenable_irq(&mutself,irq: rdrive::IrqId) -> Result<(), rdrive::driver::intc::IntcError>{// Enable interrupt implementationOk(())}// ... other required methods}fnprobe_gicv3(fdt:FdtInfo<'_>,dev:PlatformDevice) -> Result<(),OnProbeError>{let node = fdt.node;letmut reg = node.reg().ok_or("No reg property")?;let gicd_reg = reg.next().ok_or("Missing GICD register")?;let gicr_reg = reg.next().ok_or("Missing GICR register")?;let driver = GicV3Driver::new(
gicd_reg.addressasusize,
gicr_reg.addressasusize,);
dev.register(driver);Ok(())}module_driver!{
name:"GICv3",
level:ProbeLevel::PreKernel,
priority:ProbePriority::INTC,
probe_kinds:&[ProbeKind::Fdt{
compatibles:&["arm,gic-v3"],
on_probe: probe_gicv3,}],}

System Integration

1. Linker Script Configuration

Add the following section to your linker script:

.driver.register : ALIGN(4K) {
_sdriver = .;
*(.driver.register .driver.register.*)
_edriver = .;
. = ALIGN(4K);
}

2. Driver Registration Discovery

use rdrive::register::DriverRegisterSlice;fndriver_registers() -> &'static[u8]{unsafeextern"C"{fn_sdriver();fn_edriver();}unsafe{ core::slice::from_raw_parts(
_sdriver as*constu8, _edriver asusize - _sdriver asusize)}}fnget_driver_registers() -> DriverRegisterSlice{DriverRegisterSlice::from_raw(driver_registers())}

3. System Initialization

use rdrive::{Platform, probe_pre_kernel, probe_all};use core::ptr::NonNull;fninit_drivers(){// Initialize with device treelet fdt_addr = /* device tree address */;let platform = Platform::Fdt{addr:NonNull::new(fdt_addr).unwrap(),};// Initialize the driver framework
rdrive::init(platform).unwrap();// Register all discovered drivers
rdrive::register_append(get_driver_registers().as_slice());// Probe critical drivers first (interrupt controllers, etc.)
rdrive::probe_pre_kernel().unwrap();// Initialize interrupt system// irq::init_main_cpu();// Probe remaining drivers
rdrive::probe_all(false).unwrap();// false = don't stop on failures}

4. Device Access

use rdrive::{get_list, get_one, driver::Intc};fnuse_devices(){// Get all interrupt controllerslet intc_list = get_list::<Intc>();for intc in intc_list {println!("Found INTC: {:?}", intc.descriptor());}// Get the first available interrupt controllerifletSome(intc) = get_one::<Intc>(){// Use the device - this gives exclusive accessmatch intc.try_lock(){Ok(mut locked_intc) => {// Safe to use locked_intc without additional synchronization
locked_intc.enable_irq(42.into()).unwrap();}Err(owner_id) => {println!("Device busy, owned by task: {:?}", owner_id);}}}}

Supported Probe Methods

  • Device Tree (FDT): Automatic device discovery from device tree
  • Static Configuration: Manual device registration (planned)

Examples

See the examples/ directory for complete usage examples:

  • examples/enumerate/: Basic driver enumeration and device tree parsing

References

For complete integration examples, see:

About

A rust dyn driver manager.

Resources

Stars

3 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages