Template:3rd party drivers: Difference between revisions
W3ird n3rd (talk | contribs) (explaining a few things) |
|||
| Line 5: | Line 5: | ||
<b>Advantages:</b><br/> |
<b>Advantages:</b><br/> |
||
1. |
1. It's possible your device will work.. for the moment.<br/> |
||
2. If the manufacturer provides open source drivers |
2. If the manufacturer provides open source drivers with an acceptable license, volunteers could technically implement this code in the Linux kernel for true support. However.. : |
||
<b>Disadvantages:</b><br/> |
<b>Disadvantages:</b><br/> |
||
1. The quality of the code (if open, there are also cases where you just get a binary blob) too often just isn't good enough and there's still too much work to be done to make the device work. There was probably a reason the manufacturer didn't just send their patches to the linux-media mailinglist.<br/> |
|||
1. If the manufacturer provides binary modules, or object files you might have to recompile the 3rd party driver every time you update your local kernel version. Compiling might require some additional dependencies (eg. linux source tree, specific toolchain for particular architectures etc. so it might not be so easy to install them everywhere<br /> |
|||
2. |
2. Depending on what exactly the manufacturer did, you may have to reinstall the drivers every time your kernel is updated.<br/> |
||
3. When the manufacturer stops updating the drivers, the drivers will quickly refuse to install as newer kernels are released.<br/> |
|||
In case a manufacturer provides open source drivers the patches can be sent to the linux-media mailinglist [mailto:majordomo@vger.kernel.org?body=subscribe%20linux-media Linux-Media Mailing List] (LMML)<br /> |
In case a manufacturer provides open source drivers the patches can be sent to the linux-media mailinglist [mailto:majordomo@vger.kernel.org?body=subscribe%20linux-media Linux-Media Mailing List] (LMML). Keep in mind however that if the license isn't compatible with the Linux kernel or the quality of the code isn't good enough, these will not become a part of the Linux kernel.<br /> |
||
== Closed source userspace drivers (mostly Sundtek) == |
|||
== Userspace Drivers == |
|||
<b>Advantages:</b><br/> |
<b>Advantages:</b><br/> |
||
1. |
1. Same driver for nearly all Linux versions starting from 2.6.15 on.<br/> |
||
2. No |
2. No need to reinstall drivers when your kernel is updated.<br/> |
||
3. Your device could work well.<br/> |
|||
3. Manufacturer might provide well support for the device you bought<br/> |
|||
4. Drivers can be profiled easily and more accurately than in kernelspace<br/> |
4. Drivers can be profiled easily and more accurately than in kernelspace.<br/> |
||
5. If the driver crashes |
5. If the driver crashes, it won't crash the kernel. (so the system could keep running).<br/> |
||
6. If the manufacturer would stop to support the drivers, the |
6. If the manufacturer would stop to support the drivers, the userspace driver will still continue to work with newer Linux systems since the Kernelspace <-> Userspace interfaces are fixed and are not meant to be changed.<br/> |
||
<b>Disadvantages:</b><br/> |
<b>Disadvantages:</b><br/> |
||
1. |
1. Drivers need to be downloaded from the manufacturer and installed, whereas in-kernel drivers are already available in your distro.<br/> |
||
2. If major changes would be made to userspace and the manufacturer does not update the driver, the driver might no longer work. This scenario is not very likely, but not impossible.<br/> |
|||
3. You can't look into the sources. For end-users this is generally not a problem, but for programmers and people who like to hack their devices or are trying to fix bugs, it would be a disadvantage. If you just want to watch television, this does not concern you.<br/> |
|||
4. Similarly, users who want (or work for a company that requires) a FOSS-only system couldn't use these drivers. This generally doesn't concern end-users.<br/> |
|||
</div> |
</div> |
||
Revision as of 06:40, 3 September 2014
Sometimes a manufacturer forks v4l-dvb all on their own and writes a driver for their device so they can claim Linux support.
In-Kernel Drivers
Advantages:
1. It's possible your device will work.. for the moment.
2. If the manufacturer provides open source drivers with an acceptable license, volunteers could technically implement this code in the Linux kernel for true support. However.. :
Disadvantages:
1. The quality of the code (if open, there are also cases where you just get a binary blob) too often just isn't good enough and there's still too much work to be done to make the device work. There was probably a reason the manufacturer didn't just send their patches to the linux-media mailinglist.
2. Depending on what exactly the manufacturer did, you may have to reinstall the drivers every time your kernel is updated.
3. When the manufacturer stops updating the drivers, the drivers will quickly refuse to install as newer kernels are released.
In case a manufacturer provides open source drivers the patches can be sent to the linux-media mailinglist Linux-Media Mailing List (LMML). Keep in mind however that if the license isn't compatible with the Linux kernel or the quality of the code isn't good enough, these will not become a part of the Linux kernel.
Closed source userspace drivers (mostly Sundtek)
Advantages:
1. Same driver for nearly all Linux versions starting from 2.6.15 on.
2. No need to reinstall drivers when your kernel is updated.
3. Your device could work well.
4. Drivers can be profiled easily and more accurately than in kernelspace.
5. If the driver crashes, it won't crash the kernel. (so the system could keep running).
6. If the manufacturer would stop to support the drivers, the userspace driver will still continue to work with newer Linux systems since the Kernelspace <-> Userspace interfaces are fixed and are not meant to be changed.
Disadvantages:
1. Drivers need to be downloaded from the manufacturer and installed, whereas in-kernel drivers are already available in your distro.
2. If major changes would be made to userspace and the manufacturer does not update the driver, the driver might no longer work. This scenario is not very likely, but not impossible.
3. You can't look into the sources. For end-users this is generally not a problem, but for programmers and people who like to hack their devices or are trying to fix bugs, it would be a disadvantage. If you just want to watch television, this does not concern you.
4. Similarly, users who want (or work for a company that requires) a FOSS-only system couldn't use these drivers. This generally doesn't concern end-users.