public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Knowles <alan@akbkhome.com>
To: Markus Rechberger <mrechberger@gmail.com>
Cc: video4linux-list@redhat.com
Subject: Re: ASUS My Cinema-U3100Mini/DMB-TH (Legend Slilicon 8934)
Date: Fri, 25 Jul 2008 23:18:19 +0800	[thread overview]
Message-ID: <4889EEBB.9000307@akbkhome.com> (raw)
In-Reply-To: <d9def9db0807250406h6e2afeb1u614b8ba2ef8bebd3@mail.gmail.com>

I'm pretty certain this is the wrong code for my device, I'm guessing 
it's the code for a My Cinema-U3100Mini/DVBT  rather than the DMB-TH card.

Since I can't test the code, I'll leave that in the mailing list so if 
someone want's to tidy it up to merge with v4l, then it should save them 
a bit of work.

I presume it was written in-house or by a contract engineer, so they cut 
a few corners to get the job done.

Regards
Alan



Markus Rechberger wrote:
> On Fri, Jul 25, 2008 at 1:03 PM, Markus Rechberger
> <mrechberger@gmail.com> wrote:
>   
>> Hi,
>>
>> On Fri, Jul 25, 2008 at 12:26 PM, Alan Knowles <alan@akbkhome.com> wrote:
>>     
>>> Just a small update on this - I suspect ASUS released the wrong tarball for
>>> this device - as comparing the output from 'strings dib3000mc.ko' to the
>>> source code finds quite a few things missing..
>>>
>>> Waiting on a response from ASUS now.
>>>
>>>       
>> after a first look over it the code seems to be a bit "inconsitent"
>>
>> eg.:
>>
>> +static struct mt2060_config stk3000p_adimtv102_config = {
>> +       (0xC2>>1)
>> +};
>>
>> ...
>>
>> +       if (dvb_attach(adimtv102_attach, adap->fe, tun_i2c,
>> &stk3000p_adimtv102_config, if1) == NULL) {
>> ----
>>
>> whereas:
>> mt2060.h:
>>
>> (the size of the struct is the same but the purpose of the elements
>> are probably not)
>> struct mt2060_config {
>>        u8 i2c_address;
>>        u8 clock_out; /* 0 = off, 1 = CLK/4, 2 = CLK/2, 3 = CLK/1 */
>> };
>>
>> adimtv102.h:
>>
>> struct adimtv102_config {
>>        u8 i2c_address;
>>        u8 is_through_asic;
>> };
>> #if defined(CONFIG_DVB_TUNER_ADIMTV102) ||
>> (defined(CONFIG_DVB_TUNER_ADIMTV102_MODULE) && defined(MODULE))
>> extern struct dvb_frontend * adimtv102_attach(struct dvb_frontend *fe,
>> struct i2c_adapter *i2c, struct adimtv102_config *cfg, u16 if1);
>> #else
>> static inline struct dvb_frontend * adimtv102_attach(struct
>> dvb_frontend *fe, struct i2c_adapter *i2c, struct adimtv102_config
>> *cfg, u16 if1)
>> {
>>        printk(KERN_WARNING "%s: driver disabled by Kconfig\n", __FUNCTION__);
>>        return NULL;
>> }
>>
>> within the whole code if1 isn't needed (the adimtv102.h header is just
>> copied from mt2060) some cleanup still seems to be required there but
>> it's already a good start.
>>
>>     
>
> The lgs8934 implementation should also not depend on the dibcom module
> (which can be seen in your diff).
>
>   
>> Markus
>>
>>     
>>> Regards
>>> Alan
>>>
>>> Alan Knowles wrote:
>>>       
>>>> I've been looking at the drivers for  My Cinema-U3100Mini/DMB-TH
>>>>
>>>> The source is available directly from ASUS now.
>>>> http://dlcdnet.asus.com/pub/ASUS/vga/tvtuner/source_code.zip
>>>>
>>>> I've diffed it to the version they have used, and applied it, and fixed it
>>>> against the current source
>>>> http://www.akbkhome.com/svn/asus_dvb_driver/v4l-dvb-diff-from-current.diff
>>>>
>>>> In addition there are the drivers for the ADI MTV102 silicon tuner driver
>>>> http://www.akbkhome.com/svn/asus_dvb_driver/frontends/
>>>> (all the adimtv* files)
>>>>
>>>> The source code appears to use a slightly differ usb stick to the one's I
>>>> have.
>>>> 0x1748  (cold)  / 0x1749 (warm)
>>>> where as I've got
>>>> 0x1721(cold) /  0x1722 (warm)
>>>>
>>>> It looks like they hacked up dib3000mc.c, rather than writing a new driver
>>>>
>>>> I've got to the point where it builds, firmware installs etc. (firmware is
>>>> available inside the deb packages)
>>>> http://dlcdnet.asus.com/pub/ASUS/vga/tvtuner/asus-dmbth-20080528_tar.zip
>>>>
>>>> The driver initializes correctly when plugged in.
>>>> [302520.686782] dvb-usb: ASUSTeK DMB-TH successfully deinitialized and
>>>> disconnected.
>>>> [302530.550018] dvb-usb: found a 'ASUSTeK DMB-TH' in warm state.
>>>> [353408.577741] dvb-usb: will pass the complete MPEG2 transport stream to
>>>> the software demuxer.
>>>> [353408.680977] DVB: registering new adapter (ASUSTeK DMB-TH)
>>>> [302530.670387]  Cannot find LGS8934
>>>> [302530.670596] DVB: registering frontend 0 (Legend Slilicon 8934)...
>>>> [302530.670668] adimtv102_readreg 0x00
>>>> [302530.676090] adimtv102_readreg 0x01
>>>> [302530.681578] adimtv102_readreg 0x02
>>>> [302530.687077] adimtv102: successfully identified (ff ff ff)
>>>> [302530.688577] dvb-usb: ASUSTeK DMB-TH successfully initialized and
>>>> connected.
>>>> [302530.688624] usbcore: registered new interface driver dvb_usb_dibusb_mc
>>>> [353413.776593] adimtv102_init
>>>>
>>>> when w_scan is run, it outputs activity...
>>>> [353416.533576] lgs8934_SetAutoMode!
>>>> [353416.553928] lgs8934_auto_detect!
>>>> [353418.285686] lgs8934_auto_detect, lock 0
>>>> [353418.285686] adimtv102_set_params freq=184500
>>>> [353418.378803] MTV102>>tp->freq=184 PLLF=d8000 PLLFREQ=1472000
>>>>  MTV10x_REFCLK=16384 !
>>>> ......
>>>>
>>>> however fails to pick up any channels...
>>>>
>>>> I'm trying to connect to these -
>>>> http://en.wikipedia.org/wiki/Digital_television_in_Hong_Kong
>>>>
>>>> Any ideas welcome..
>>>>
>>>> Regards
>>>> Alan
>>>>
>>>> --
>>>> video4linux-list mailing list
>>>> Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
>>>> https://www.redhat.com/mailman/listinfo/video4linux-list
>>>>         
>>> --
>>> video4linux-list mailing list
>>> Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
>>> https://www.redhat.com/mailman/listinfo/video4linux-list
>>>
>>>       

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  reply	other threads:[~2008-07-25 15:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25  7:36 ASUS My Cinema-U3100Mini/DMB-TH (Legend Slilicon 8934) Alan Knowles
2008-07-25 10:26 ` Alan Knowles
2008-07-25 11:03   ` Markus Rechberger
2008-07-25 11:06     ` Markus Rechberger
2008-07-25 15:18       ` Alan Knowles [this message]
2008-07-25 15:49         ` Markus Rechberger
2008-07-25 16:06 ` Markus Rechberger
2008-07-26  0:16   ` Alan Knowles

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4889EEBB.9000307@akbkhome.com \
    --to=alan@akbkhome.com \
    --cc=mrechberger@gmail.com \
    --cc=video4linux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox