drivers/parport/TODO-parport
Source file repositories/reference/linux-study-clean/drivers/parport/TODO-parport
File Facts
- System
- Linux kernel
- Corpus path
drivers/parport/TODO-parport- Extension
[no extension]- Size
- 585 bytes
- Lines
- 21
- Domain
- Driver Families
- Bucket
- drivers/parport
- Inferred role
- Driver Families: drivers/parport
- Status
- atlas-only
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
Things to be done.
0. Fix the bugs (see BUGS-parport).
1. Proper documentation.
2. A better lp.c:
a) ECP support would be nice. This can only work if both the port and
the printer support it.
b) Handle status readback automatically. IEEE1284 printers can post status
bits when they have something to say. We should read out and deal
with (maybe just log) whatever the printer wants to tell the world.
3. Support more hardware (eg m68k).
4. A better PLIP (make use of bidirectional/ECP/EPP ports).
See <URL:http://people.redhat.com/twaugh/parport/>.
Annotation
- Atlas domain: Driver Families / drivers/parport.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.