Hide Forgot
Description of problem: DVB Elgato EyeTV Hybrid (0fd9:0018) not handled by driver Version-Release number of selected component (if applicable): kernel-PAE-2.6.35.11-83.fc14.i686 How reproducible: Always Steps to Reproduce: 1. Insert Elgato EyeTV hybrid USB stick (0fd9:0018) 2. 3. Actual results: No support. Expected results: It to be supported. Additional info: https://bugzilla.kernel.org/show_bug.cgi?id=16342 The device is not very new anymore so i aspect it to be supported but it isn't.
Can somebody please pick this up and start working on a driver?
Linux has become my favorite OS through the years. I have been using it from RedHat 4 on until now. I few years I have been waiting for support in Linux for my ATI Radeon videocard with tuner capabilities (which always has been working fine in MS Windows), but it has never come this far. So that's why i recently decided to give the ATI videocard up. And i bought myself an Elgato Eyetv Hybrid USB stick in the assumption that such hardware would be well supported in Linux as well and the device has all the capabilities i want. I regret my choice now because i am faced with another peace of hardware which isn't working in Linux. To bad. Sure, it's my own mistake since i should have done more research which USB device currently are. Nevertheless, I think that since these DVB USB device are growing in popularity so much it's not unexpectable for this device to be supported very soon, is it? At least, i hope so. Is anyone able to respond to this? Is there some information about the development of a driver for this device available yet? Or should i get rit of it and buy a different device? Regards, Eddie.
Is anyone able to respond to this? Is there some information about the development of a driver for this device available yet?
Come on people, this device is already present from 2008 on. We are living in 2011 now, it shouldn't have to take that long to add support for this device to the linux kernel, should it?
Please add support for DVB Elgato EyeTV Hybrid (0fd9:0018) to kernel.
About the missing support for the Elgato Eyetv Hybrid (USB device 0fd9:0018). A while ago i found on the internet info that Micronas has released a gpl'ed driver for the device. But it appears that nobody has been willing to do the work to get it upstream. However, I found a message at: http://www.mail-archive.com/em28xx@mcentral.de/msg01188.html Perhaps the person in that message can be contacted about the missing driver and details ? So it wouldn't be necessary to reinvent the wheel? And support for the device can be added easily?
Eddie, (In reply to comment #6) > About the missing support for the Elgato Eyetv Hybrid (USB device 0fd9:0018). > > A while ago i found on the internet info that Micronas has released a > gpl'ed driver for the device. > > But it appears that nobody has been > willing to do the work to get it upstream. > > However, I found a message at: > http://www.mail-archive.com/em28xx@mcentral.de/msg01188.html > > Perhaps the person in that message can be contacted about the missing > driver and details ? No. Markus won't help with open source drivers. He has a business selling proprietary closed-source drivers for his hardware. > So it wouldn't be necessary to reinvent the wheel? And support for the > device can be added easily? The DRX-K driver got merged upstream for 3.1, covering the digital TV support of the DRX-K chipset. This doesn't necessarely means that all devices using it are automatically supported. Someone with the hardware needs to discover the missing bits needed to reset DRX-K, enable IR, disable the analog part, etc. Also, the DRX-K driver was written with one specific DRX-K model in mind. Some minor adjustments may be needed to support other chipset models. In summary, someone with your device would need to put it to run in Windows, run some USB sniffer, and adjust the Linux driver to produce the same results. Well, maybe Elgato is close enough to Terratec H5. If so, just adding an entry at em28xx-cards may be enough, but the risk of doing that is that some input/output ports (GPIO) may be wrongly set, causing device oveheat.