Project Summary
This project enables the user to read from and/or write to any generic memory location(s) on a device running the 2.6 Linux OS (or later). This includes "regular" RAM as well as hardware IO Memory that's mapped into the kernel virtual address space. In fact, the driver will perform the mapping, given the hardware base address and length.
The read/write utility programs run in user-land and talk to the underlying kernel driver via the ioctl system call.
This could be extremely useful for driver authors, kernel developers, etc who want to peek/poke memory for learning, debug, testing, register lookups/writes and similar purposes.
In a Nutshell, Device Memory Read/Write...
- ...
- ...
- ...
-
...
took an estimated 1 years of effort (COCOMO model)
starting with its first commit in July, 2011
ending with its most recent commit about 1 year ago
Quick Reference
MIT
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Use Patent Claims
Forbidden
Sub-License
Hold Liable
Required
Distribute Original
Disclose Source
Include Copyright
State Changes
Include License
Include Install Instructions
These details are provided for information only. No information here is legal advice and should not be used as such.
This Project has No vulnerabilities Reported Against it
Did You Know...
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
learn about Open Hub updates and features on the Open Hub blog
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
you can embed statistics from Open Hub on your site
30 Day SummarySep 21 2026 — Oct 21 2026
|
12 Month SummaryOct 21 2025 — Oct 21 2026
|
