Lines Matching refs:driver
51 of exclusive GPL licensing, and if you wish the driver
63 Interfaces: If your driver uses existing interfaces and behaves like
72 are shared with a windows driver kit and you want to
78 shouldn't use inline x86 assembler in your driver without
84 Clarity: It helps if anyone can see how to fix the driver. It helps
86 driver that intentionally obfuscates how the hardware works
90 driver is likely to be used on such a system and therefore it
94 that your driver correctly handles the suspend and resume, but
98 driver uses as little power as possible when it's not doing
99 anything. For the driver testing instructions see
104 Control: In general if there is active maintenance of a driver by
108 driver it is a good idea to state this in the comments,
109 and include an entry in MAINTAINERS for your driver.
114 Vendor: Being the hardware vendor and maintaining the driver is
115 often a good thing. If there is a stable working driver from
117 vendor' to get your driver chosen. Ideally work with the
118 existing driver author to build a single perfect driver.
120 Author: It doesn't matter if a large Linux company wrote the driver,
147 http://lwn.net/Articles/driver-porting/
156 How to NOT write kernel driver by Arjan van de Ven:
157 http://www.fenrus.org/how-to-not-write-a-device-driver-paper.pdf