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: Sat, 26 Jul 2008 08:16:25 +0800	[thread overview]
Message-ID: <488A6CD9.6060107@akbkhome.com> (raw)
In-Reply-To: <d9def9db0807250906q4918121awceb6e0f938088e6d@mail.gmail.com>


snip .....
>> [353408.680977] DVB: registering new adapter (ASUSTeK DMB-TH)
>> [302530.670387]  Cannot find LGS8934
>>     
>
> this is basically the problem here.
>
>   
Which along with:

= the binary modules released by asus for the eeepc for this device 
(which I've heard works)

dib3000mc.ko       dvb-core.ko               dvb-usb-dibusb-mc.ko
dibx000_common.ko  dvb-usb-dibusb-common.ko  dvb-usb.ko

* note - no adimtv module...? - I'm guessing it uses one of the existing 
tuners..

doing a strings on dib3000mc.ko finds a few interesting items:

# strings dib3000mc.ko  | grep -i dmbth

u3100DMBTH set freq=%d
u3100dmbth init
u3100dmbth 8GL5 init <-- a known ledgend chip for DMB-TH (and the code 
is not in the tarball)
u3100dmbth 8934 init
U3100-DMBTH Device ID: %d
 
So since those strings are missing from the source file, I'm pretty 
convinced they released the wrong code..

Regards
Alan


--
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-26  0:16 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
2008-07-25 15:49         ` Markus Rechberger
2008-07-25 16:06 ` Markus Rechberger
2008-07-26  0:16   ` Alan Knowles [this message]

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=488A6CD9.6060107@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