| stable-api-nonsense.rst (1d2375f048b7da90402c7a40fb3606b320c3f76f) | stable-api-nonsense.rst (8f7e6d134bda563c9b3abac14de11e89eb4c86d7) |
|---|---|
| 1.. _stable_api_nonsense: 2 3The Linux Kernel Driver Interface 4================================== 5 6(all of your questions answered and then some) 7 8Greg Kroah-Hartman <greg@kroah.com> --- 155 unchanged lines hidden (view full) --- 164---------- 165 166So, if you have a Linux kernel driver that is not in the main kernel 167tree, what are you, a developer, supposed to do? Releasing a binary 168driver for every different kernel version for every distribution is a 169nightmare, and trying to keep up with an ever changing kernel interface 170is also a rough job. 171 | 1.. _stable_api_nonsense: 2 3The Linux Kernel Driver Interface 4================================== 5 6(all of your questions answered and then some) 7 8Greg Kroah-Hartman <greg@kroah.com> --- 155 unchanged lines hidden (view full) --- 164---------- 165 166So, if you have a Linux kernel driver that is not in the main kernel 167tree, what are you, a developer, supposed to do? Releasing a binary 168driver for every different kernel version for every distribution is a 169nightmare, and trying to keep up with an ever changing kernel interface 170is also a rough job. 171 |
| 172Simple, get your kernel driver into the main kernel tree (remember we 173are talking about GPL released drivers here, if your code doesn't fall 174under this category, good luck, you are on your own here, you leech). If your 175driver is in the tree, and a kernel interface changes, it will be fixed 176up by the person who did the kernel change in the first place. This 177ensures that your driver is always buildable, and works over time, with 178very little effort on your part. | 172Simple, get your kernel driver into the main kernel tree (remember we are 173talking about drivers released under a GPL-compatible license here, if your 174code doesn't fall under this category, good luck, you are on your own here, 175you leech). If your driver is in the tree, and a kernel interface changes, 176it will be fixed up by the person who did the kernel change in the first 177place. This ensures that your driver is always buildable, and works over 178time, with very little effort on your part. |
| 179 180The very good side effects of having your driver in the main kernel tree 181are: 182 183 - The quality of the driver will rise as the maintenance costs (to the 184 original developer) will decrease. 185 - Other developers will add features to your driver. 186 - Other people will find and fix bugs in your driver. --- 18 unchanged lines hidden --- | 179 180The very good side effects of having your driver in the main kernel tree 181are: 182 183 - The quality of the driver will rise as the maintenance costs (to the 184 original developer) will decrease. 185 - Other developers will add features to your driver. 186 - Other people will find and fix bugs in your driver. --- 18 unchanged lines hidden --- |