drivers/parport/BUGS-parport
Source file repositories/reference/linux-study-clean/drivers/parport/BUGS-parport
File Facts
- System
- Linux kernel
- Corpus path
drivers/parport/BUGS-parport- Extension
[no extension]- Size
- 319 bytes
- Lines
- 10
- 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
Currently known (or at least suspected) bugs in parport:
o lp doesn't allow you to read status while printing is in progress (is
this still true?).
o parport_pc_ecp_read_block_pio() is broken. parport will revert to the
software-driven mode in ieee1284_ops.c
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.