Template:3rd party drivers

From LinuxTVWiki
Revision as of 08:08, 15 January 2015 by Wirbel (talk | contribs) (In-Kernel Drivers)
Jump to: navigation, search

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 3rd party Drivers


  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.. :


  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)

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 system or kernel, only the driver and applications using the driver will be affected. Userspace drivers can also be used when debugging drivers for USB host controllers, as the userspace driver can't crash the system, making debugging easier.
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.
7. Application based drivers are modern since they use modern Linux interfaces (eg. stable Userspace USB Interfaces since 2006) which did not exist when legacy Kernel drivers were invented
1. Drivers need to be downloaded from the manufacturer and installed, whereas in-kernel drivers are included in most popular Linux desktop-oriented distributions.
2. 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.
3. 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.