The information contained here is likely non-exhaustive and, despite best efforts to do otherwise, may contain errors. (Please help to keep these lists up-to-date so that they are useful for everyone!)

by posting a question about the device directly to the LMML (but please do conduct a search first, as it may already have been discussed!)

Note: when it comes to support, it is generally a good idea to try the current V4L-DVB sources because some device drivers can be very new and thus may have not made their way into the mainstream kernel.

In any regard, in respect to the above listed suggestions, you may find it to be the case that your device is actually already supported or that experimental support is available.

Because the component constitution on many devices are often similar or identical, there may be devices that are unlisted but may actually work with the existing driver framework for previously supported devices. In such a case, your non-listed but working device will likely be reported in your system messages as being one of those previously supported devices. If you encounter such an occurrence, please do report your success on the LMML so that proper detection/identification of your device can be added within the drivers.

Lastly, it bears worth repeating the request: Please help to keep these lists up-to-date so that they are useful for everyone!

Experimental Support

Currently none.

Currently Unsupported DVB-S2 USB Devices

If you own one or more devices from the following list and you want to help with support development, please contact the Linux-Media Mailing List (LMML). Note that if your device is similar to or contains components for which driver development is currently being undertaken, then it is possible that you will pique the(se) developer's interest and can obtain some assistance that, possibly, leads to full support for your device.

However, please note that inquiries to the mailing list:

should NOT be treated as an order drop-off line/queue. You're soliciting help from volunteer developers who work on V4L-DVB matters in their spare time, and such work can be non-trivial (i.e. requiring even _thousands_ of hours work). So being demanding is one sure route to being ignored. (Honestly, this point really shouldn't even need to be written, but you'd be surprised at the number of irrational individuals who write into the mailing list demanding this or that).

may pass without even garnering a response -- that's a distinct by-product of the fact that there are only a limited number of developers, whom might be able to help, that are associated with the project. Often times, even if they wished to help, their energies are entirely tied up with other projects. In such cases, the best path might be to try to spearhead the driver development for your device yourself, or arrange to hire someone who can.

Supported by 3rd Party Drivers

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

Advantages:

It's possible your device will work.. for the moment.

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:

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.

Depending on what exactly the manufacturer did, you may have to reinstall the drivers every time your kernel is updated.

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.

NOTE:
As linux media drivers are character based, drivers can be also written using libfuse's character device in userspace example.
If written that way, an out-of-kernel driver can be written, which fully integrates to udev without the disadvantage of closed source or incompatibility to other drivers. Such driver would rely on kernel fuse and character device in user space support as well as libfuse.

Closed source userspace drivers (mostly Sundtek)

Advantages:

Same driver may be usable for different Linux versions, depending on what vendor did.

No need to reinstall drivers when your kernel is updated.

Drivers can be profiled easily and more accurately than in kernelspace.

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.

If the manufacturer would stop to support the drivers, the userspace driver may still continue to work with newer Linux systems

Disadvantages:

No interoperation with udev, since kernel interfaces are not used and uevents not send.

Needs non-standard constructs to create device nodes or hack into system using LD_PRELOAD (bad idea.)

Kernel doesnt autoload devices, since kernel is not aware of those devices.

Drivers need to be downloaded from the manufacturer and installed, whereas in-kernel drivers are included in most popular Linux desktop-oriented distributions.

You can't look into the sources. While this may be not a problem for end-users, it prevents hacking devices and trying to fix bugs.

Similarly, users who want (or work for a company that requires) a FOSS-only system couldn't use these drivers. This also prevents inclusion in most Linux distributions.