Hello Michael,
On Tue, 23 Jan 2007, Michael Wünscher wrote:
> Hello to the list,
>
> in my Samsung R55 laptop there is an integrated dvb-t device.
>
> the listing of lsusb says it is a dibcom stk7700D wich should be a
> stk7700p in another design.
No, the STK7700D is normally the name for a DiBcom ref-design which has:
2 DiB7000P and 2 MT2266.
It is a diversity or dual DVB-T receiver.
The one you think it is, is called STK7700P3 (Single DiB7000P + XC3028) -
DVB_T only.
Of course the real end-manufacturer can do what he wants. So everything is
possible.
> So i tried to get the dib driver to work and added my device to the
> dib0700_device.c (source's from http://linuxtv.org/hg/v4l-dvb).
>
> dmesg:
>
> [ 14.468000] dib0700: loaded with support for 3 different device-types
> [ 14.516000] check for cold 10b8 1e14
> [ 14.516000] check for cold 10b8 1e78
> [ 14.516000] check for cold 2040 7050
> [ 14.516000] check for cold 7ca a807
> [ 14.516000] check for cold 185b 1e78
> [ 14.516000] check for cold 1584 6003
> [ 14.516000] check for cold 2040 9941
> [ 14.516000] check for cold 2040 9950
> [ 14.516000] check for cold 1164 1efc
> [ 14.516000] dvb-usb: found a 'YUAN Tech STK7700D with XC3028' in
> cold state, will try to load a firmware
> [ 14.664000] dvb-usb: downloading firmware from file
> 'dvb-usb-dib0700-01.fw'
> [ 14.840000] dib0700: firmware started successfully.
> [ 15.344000] dvb-usb: found a 'YUAN Tech STK7700D with XC3028' in
> warm state.
> [ 15.344000] power control: 1
> [ 15.344000] dvb-usb: will pass the complete MPEG2 transport stream to
> the software demuxer.
> [ 15.344000] DVB: registering new adapter (YUAN Tech STK7700D with
> XC3028).
> [ 15.560000] DVB: registering frontend 0 (DiBcom 7000PC)...
> [ 15.560000] Tuner: registering extension (MT2060 Silicon Tuner)
> [ 15.656000] mt2060 I2C read failed
> [ 15.656000] power control: 0
> [ 15.656000] dvb-usb: YUAN Tech STK7700D with XC3028 successfully
> initialized and connected.
> [ 15.656000] usbcore: registered new interface driver dvb_usb_dib0700
>
> -------
>
> This works until the tuner gets registered. (There were also an older
> posting http://www.mail-archive.com/linux-dvb@xxxxxxxxxxx/msg20994.html)
>
> I found out that there is a xc3028 tuner on the device. This based of
> investigating the windows driver. It includes a file named xc3028.rom
> and the inf file had the following line for the device:
This is not necessarily an indication, because the reference driver from
DiBcom contains all drivers for all devices. So there can be XYZ
mentioned, even without having that device on you hardware.
> %YUAN.DeviceDesc_cold% = MOD7000.Device,USB
> \VID_1164&PID_1EFC ; C version + 843 + 3028, NO AV S & NO FM
> %YUAN.DeviceDesc% = MOD7000.Device,USB
> \VID_1164&PID_1EFD&MI_00 ; C version + 843 + 3028, NO AV S & NO FM
But this comment is obvious - it seems to be really the XC3028 inside, but
without Analog Audio/Video and no FM.
> So i tried to understand the xc3028-tuner.c .
>
> I think i need to port the driver to the dvb-frontend framework to get
> it working?? or is there another way?
This is not done yet?
> My last question, Does anybody know what the 843 chip could be?
No. C-version is most likely the USB/Demod-revision, 3028 is the Xceive.
If it is really the xc3028, even more important is to find out which GPIO
are used to do a reset on the Xceive.
> Its written in the inf file of the windows driver. Because it is
> build-in the laptop i can not get a picture of the device :-(
Patrick.
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
