]>
Commit | Line | Data |
---|---|---|
9a69f508 SQ |
1 | This is a list of things that need to be done to get this driver out of the |
2 | staging directory. | |
38358415 AD |
3 | |
4 | - Implement the gasket framework's functionality through UIO instead of | |
5 | introducing a new user-space drivers framework that is quite similar. | |
6 | ||
7 | UIO provides the necessary bits to implement user-space drivers. Meanwhile | |
8 | the gasket APIs adds some extra conveniences like PCI BAR mapping, and | |
9 | MSI interrupts. Add these features to the UIO subsystem, then re-implement | |
10 | the Apex driver as a basic UIO driver instead (include/linux/uio_driver.h) | |
11 | ||
9a69f508 | 12 | - Document sysfs files with Documentation/ABI/ entries. |
38358415 | 13 | |
9a69f508 | 14 | - Use misc interface instead of major number for driver version description. |
38358415 | 15 | |
9a69f508 | 16 | - Add descriptions of module_param's |
38358415 | 17 | |
9a69f508 | 18 | - apex_get_status() should actually check status. |
38358415 | 19 | |
9a69f508 SQ |
20 | - "drivers" should never be dealing with "raw" sysfs calls or mess around with |
21 | kobjects at all. The driver core should handle all of this for you | |
22 | automaically. There should not be a need for raw attribute macros. |