Hi, On 10/5/07, Aidan Thornton <makosoft@xxxxxxxxxxxxxx> wrote: > Hi, > > On 10/5/07, David Campbell <david@xxxxxxxxxxxxxxxx> wrote: > > I include detail for a EM2870-based USB DVB-T tuner that doesn't seem to > > work properly using fedora 7 and the em28xx drivers from > > http://mcentral.de/wiki/index.php/Em2880. There's no brand or model > > number on the device externally or internally, box, or in the > > documentation, but the vendor code is eb1a "eMPIA Technology, Inc." > > Looks like the vendor couldn't be bothered to change the USB ID from > the default. If there's no brand or model number, I suppose that's not > surprising. > yes... > > You can see photos of the device and visible chips at: > > http://www.aaa.net.au/campbell/device.jpg (low-res) > > http://www.aaa.net.au/campbell/device_chips.jpg (high-res) > > > > Judging from http://www.bttv-gallery.de/ the device seems to have its > > similarities to the "Compro VideoMate U3 DVB-T stick", but some of the > > eprom entries are different. > > Let's see now - there's a ZL10353 DVB-T demod and a Philips 74HC4052D > analog multiplexer/demultiplexer. Somewhere on the device (possibly on > the other side of the board) there should be an em2870 and some sort > of tuner chip (probably an xc3028, as there's an i2c device at 0xc2). > I don't think it's particularly similar to the Compro VideoMate U3 - > that has a different layout and chips. The most similar card > hardware-wise is probably the Kworld 350U. > The tuner is usually near the antenna connector, probably behind that shielding.. > Assuming the tuner is an xc3028, it should be possible to add support > for the device. The main questions are how to detect it and what to > call it. You can try contacting Markus - he's the person behind that > particular version of the em28xx driver - but I think he's currently a > bit busy with other things. (I might be able to add support for the > device myself - I have my own version of the driver at > http://www.makomk.com/hg/v4l-dvb-makomk for various reasons - but it'd > be tricky. Do you have Windows XP and does it work under that?) > those devices usually have/had a qt1010 chip inside, very first releases also had xc3028 chips for dvb-t only. > > The driver finds it but doesn't seem to recognise one of the i2c > > devices: em28xx #0: found i2c device @ 0x16 [???] > > That's the ZL10353. I think it's the analog code that's not detecting > it; it's the digital part of the driver that handles this i2c device, > and it doesn't auto-detect. no it's not the zl10353, it must be another i2c device. This device requires a gpio setup for enabling the zl10353 on the i2c bus. > > > DMESG (I don't know why the driver says it can't find the eprom, and > > then dumps the contents of the eprom) > > I think it always says that when it finds a device with a generic > eMPIA USB ID and it can't recognise it, probably because the devices > that originally had this problem didn't have eproms. > yes, it prints it by default if no carddefinition was found in the driver for the particular card. The driver does some dirty probing relying on checking certain i2c addresses for devices or specific eeprom entries since the usbid isn't set to something unique in the driver. Markus _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
