Sound like a lot of work, and it would be easier just to buy a functional tuner :) Guess I'm busy enough. However, I did manage to find some more info, for someone to use someday :) /Morten Model: EU 2008 USB Contoller: Empia EM2884 Stereo A/V Decoder: Micronas AVF 49x08 Hybrid Channel Decoder: Micronas DRX-K DRX3926K:A1 0.9.0 On Fri, Jan 22, 2010 at 5:27 PM, Devin Heitmueller <dheitmueller@xxxxxxxxxxxxxx> wrote: > On Fri, Jan 22, 2010 at 11:18 AM, Morten Friesgaard > <friesgaard@xxxxxxxxx> wrote: >> Actually I don't understand why this em28xx driver is the only one >> being patched, guess that reduces backward compability!? :-P > > There are many drivers actively being developed. What I'm trying to > say is that the new version of the EyeTV Hybrid is not an em28xx based > hardware design. > >> Well, I haven't given up, but no one has given me any pointers but /dev/null >> If this em28xx module would be startable with the usb id "0fd9:0018", >> I could tryout the old driver. >> If you say the hardware design is completely different, I guess it >> should still be possible to mount the usb device and fetch anything >> from the device (e.g. tvtime -d /dev/usbdev). The driver would be a >> matter of controlling the device to tune to the correct channel etc. > > No, that is not how USB drivers work. You have to know how to program > the various chips on the device (the bridge, demodulator, decoder, > tuner), as well as knowing how to decode the packets coming back from > the device. If you want to get an understanding as to how complex the > drivers are then feel free to look at some of them in the v4l-dvb > source code. You can get a better understanding as to how these > devices are designed here: > > KernelLabs Blog: How Tuners Work... > http://www.kernellabs.com/blog/?p=1045 > >> When new hardware is introduced, how do you guys break down the task >> and implement a driver? (how much can be borrow from the mac os x >> drivers?) > > It largely depends on the device. Usually you start by cracking it > open and seeing what chips it contains, and from there you can see > which components currently have a driver and which do not. Whether > the various components are already supported usually drives whether a > whole new driver is required or just a board profile in an existing > driver. And whether datasheets are available publicly dictates how > easy/hard it is to write a driver (the datasheets are usually *not* > available for modern devices, or only available under NDA). > > Devin > > -- > Devin J. Heitmueller - Kernel Labs > http://www.kernellabs.com > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
