Hi,
this week I bought a Elgato EyeTV Diversity USB stick for my iBook
that I also wanted to use with my Linux system. I thought it is a good
choice because the Supported Hardware list states for the Hauppauge
Nova-T stick that it's 'Identical to the USB Stick Elgato is
selling'. But mine has a different vendor and product id.
Simply adding a new entry beside the Hauppauge Nova-T stick using the
new ids didn't work. Using trail and error I was able to find the
right combination. I also was able to activate the remote
control. Since the other devices that use stk7070pd_frontend_attach0
and stk7070pd_frontend_attach1 as frontends doesn't activate the RC I
needed to start a section for my stick. If it doesn't hurt the other
devices to have a RC defined perhaps you should combine them.
The patches are based on the v4l-dvb code I got on Saturday using hg
clone http://linuxtv.org/hg/v4l-dvb. I have a 2.6.25 kernel. Would it
help to check if these patches works against the vanilla 2.6.25 too?
Here are some results/comments/questions:
This is what I get now:
Sep 14 08:52:07 grizzly kernel: usb 6-2: new high speed USB device using ehci_hcd and address 3
Sep 14 08:52:07 grizzly kernel: usb 6-2: configuration #1 chosen from 1 choice
Sep 14 08:52:07 grizzly kernel: usb 6-2: New USB device found, idVendor=0fd9, idProduct=0011
Sep 14 08:52:07 grizzly kernel: usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 14 08:52:07 grizzly kernel: usb 6-2: Product: EyeTV Diversity
Sep 14 08:52:07 grizzly kernel: usb 6-2: Manufacturer: Elgato
Sep 14 08:52:07 grizzly kernel: usb 6-2: SerialNumber: 080604003698
Sep 14 08:52:07 grizzly kernel: dib0700: loaded with support for 8 different device-types
Sep 14 08:52:07 grizzly kernel: dvb-usb: found a 'Elgato EyeTV Diversity' in cold state, will try to load a firmware
Sep 14 08:52:07 grizzly kernel: dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw'
Sep 14 08:52:07 grizzly kernel: dib0700: firmware started successfully.
Sep 14 08:52:08 grizzly kernel: dvb-usb: found a 'Elgato EyeTV Diversity' in warm state.
Sep 14 08:52:08 grizzly kernel: i2c-adapter i2c-2: SMBus Quick command not supported, can't probe for chips
Sep 14 08:52:08 grizzly kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Sep 14 08:52:08 grizzly kernel: DVB: registering new adapter (Elgato EyeTV Diversity)
Sep 14 08:52:08 grizzly kernel: i2c-adapter i2c-3: SMBus Quick command not supported, can't probe for chips
Sep 14 08:52:08 grizzly kernel: DVB: registering frontend 0 (DiBcom 7000PC)...
Sep 14 08:52:08 grizzly kernel: DiB0070: successfully identified
Sep 14 08:52:08 grizzly kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Sep 14 08:52:08 grizzly kernel: DVB: registering new adapter (Elgato EyeTV Diversity)
Sep 14 08:52:08 grizzly kernel: i2c-adapter i2c-4: SMBus Quick command not supported, can't probe for chips
Sep 14 08:52:08 grizzly kernel: DVB: registering frontend 1 (DiBcom 7000PC)...
Sep 14 08:52:08 grizzly kernel: DiB0070: successfully identified
Sep 14 08:52:08 grizzly kernel: input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1a.7/usb6/6-2/input/input5
Sep 14 08:52:08 grizzly kernel: dvb-usb: schedule remote query interval to 150 msecs.
Sep 14 08:52:08 grizzly kernel: dvb-usb: Elgato EyeTV Diversity successfully initialized and connected.
Sep 14 08:52:08 grizzly kernel: usbcore: registered new interface driver dvb_usb_dib0700
The following modules are loaded:
dvb_usb_dib0700 31240 0
dib7000p 15240 3 dvb_usb_dib0700
dib7000m 13252 1 dvb_usb_dib0700
dvb_usb 17996 1 dvb_usb_dib0700
dvb_core 71232 1 dvb_usb
dib3000mc 11464 1 dvb_usb_dib0700
dibx000_common 3012 3 dib7000p,dib7000m,dib3000mc
dib0070 7236 3 dvb_usb_dib0700
What about these i2c errors? Should I worry about them? Although if
not do you have an idea how I can get rid of them? 'i2c-adapter
i2c-2: SMBus Quick command not supported, can't probe for chips'
To use the remote control you have to set the module parameter
dvb_usb_dib0700_ir_proto=0 (NEC). Is there a possibility to hard-code
this in the driver? The standard protocol RC5 worked somehow, i.e. I
got reproducable numbers, but from time to time I got wrong numbers
and there was no system in the created numbers. With NEC protocol the
first number is always 0x45 and the second number is more or less a
simply serially numbered value starting with 1. So I would assume that
they really use NEC protocol which should be a parameter of the device
description in the code so that the driver uses the right setting by
default.
It works with both firmware versions: dvb-usb-dib0700-1.10.fw and
dvb-usb-dib0700-1.20.fw. I use a link for the 1.20 so that I don't
need to need to change the code.
Although it is stated that the diversity mode is currentl not
supported it seems to be necessary that both antenna plugs are
connected. I have an active antenna and I thought that without
diversity it would be the best to connect the antenna directly to the
adapter that I want to use. But in this combination 'scan' only
creates 'WARNING: >>> tuning failed!!!' messages. If I use the Y-cable
to connect the antenna to both adapters scan is able to find the TV
channels. Do you have an explanation for this behaviour?
Are there plans to add support for the diversity mode?
It maked my work to get the device running smooth that I was able to
work in a private v4l-dvb directory without the need to patch the
kernel sources and simply call 'make && make install' for the changed
modules in this private directory.
Regards
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dib0700_devices.c.patch
Type: text/x-diff
Size: 2828 bytes
Desc: not available
Url : http://www.linuxtv.org/pipermail/linux-dvb/attachments/20080914/febf039f/attachment.patch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dvb-usb-ids.h.patch
Type: text/x-diff
Size: 558 bytes
Desc: not available
Url : http://www.linuxtv.org/pipermail/linux-dvb/attachments/20080914/febf039f/attachment-0001.patch