public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Lauri Laanmets <lauri.laanmets@proekspert.ee>
To: Markus Rechberger <mrechberger@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: DVB support for MSI DigiVox A/D II and KWorld 320U
Date: Fri, 13 Nov 2009 10:59:55 +0200 (EET)	[thread overview]
Message-ID: <3933453.18034.1258102795094.JavaMail.root@mail> (raw)
In-Reply-To: <d9def9db0911130047i2cc2eccyc9807f63fb5e9647@mail.gmail.com>

Hi

Sorry if I wasn't clear enough. I'm trying to get V4l code working. So I'm playing around with GPIO's and have managed to get the I2C communication working but something is still missing. I was thinking that because mcentral code worked, maybe some information can be taken over from it but the code is so much different, I do not understand it fully.

Or what should I try next?

Lauri

----- Original Message -----
From: "Markus Rechberger" <mrechberger@gmail.com>
To: "Lauri Laanmets" <lauri.laanmets@proekspert.ee>
Cc: linux-media@vger.kernel.org
Sent: Friday, November 13, 2009 10:47:03 AM
Subject: Re: DVB support for MSI DigiVox A/D II and KWorld 320U

On Fri, Nov 13, 2009 at 4:37 PM, Lauri Laanmets
<lauri.laanmets@proekspert.ee> wrote:
> Hello
>
> I have managed to attach the device without any error messages now but the tuning and playback of DVB still doesn't work. I get a lot of these error messages:
>
> [  247.268152] em28xx #0: reading i2c device failed (error=-110)
> [  247.268161] xc2028 1-0061: i2c input error: rc = -110 (should be 2)
>
> and
>
> [  433.232124] xc2028 1-0061: Loading SCODE for type=DTV6 ATSC OREN538 SCODE HAS_IF_5580 (60110020), id 0000000000000000.
> [  433.256017] xc2028 1-0061: Incorrect readback of firmware version.
> [  433.372019] xc2028 1-0061: Loading firmware for type=BASE F8MHZ (3), id 0000000000000000.
> [  437.940029] xc2028 1-0061: Loading firmware for type=D2620 DTV78 (108), id 0000000000000000.
>
> Do anybody have an idea what to do next? Or maybe somebody is willing to help me understanding the mcentral code because that one works fine.
>

Due some fundamental problems we do not recommend to use the
em28xx-new code, it can damage your device(!)

We are now working together with several manufacturers since we
accepted their restrictions we got indepth details about how to handle
those devices correctly in order to prevent damaged devices. Even if
it works fine for you it might break the device the next day. The only
way to get it right is to cooperate with the chip design companies.

Markus

  reply	other threads:[~2009-11-13  8:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <31497292.9391255416643929.JavaMail.root@mail>
2009-10-13  6:54 ` DVB support for MSI DigiVox A/D II and KWorld 320U Lauri Laanmets
2009-11-13  8:37   ` Fwd: " Lauri Laanmets
2009-11-13  8:47     ` Markus Rechberger
2009-11-13  8:59       ` Lauri Laanmets [this message]
2009-11-14 18:42 viktor
  -- strict thread matches above, loose matches on Subject: below --
2009-10-12 19:23 Lauri Laanmets
2009-10-12 20:13 ` Devin Heitmueller
2009-10-12 20:41   ` Lauri Laanmets
2009-10-12 20:45     ` Devin Heitmueller

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=3933453.18034.1258102795094.JavaMail.root@mail \
    --to=lauri.laanmets@proekspert.ee \
    --cc=linux-media@vger.kernel.org \
    --cc=mrechberger@gmail.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