public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Ringel <stefan.ringel@arcor.de>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Devin Heitmueller <dheitmueller@kernellabs.com>,
	linux-media@vger.kernel.org
Subject: Re: Terratec Cinergy Hybrid XE (TM6010 Mediachip)
Date: Mon, 25 Jan 2010 17:12:26 +0100	[thread overview]
Message-ID: <4B5DC2EA.3090706@arcor.de> (raw)
In-Reply-To: <4B5DAC3A.6000408@redhat.com>

Am 25.01.2010 15:35, schrieb Mauro Carvalho Chehab:
> Stefan Ringel wrote:
>   
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>  
>> Hi Davin,
>> I have a question. How are loaded the base firmware into xc3028, in
>> once or in a split ? It's importent for TM6010, the USB-Analyzer said
>> that it load it in once and then send a quitting reqeuest.
>>     
> The way the original driver for tm6000/tm6010 does varies from firmware
> version to firmware version. That part of the driver works fine for
> both tm6000 and tm6010, with the devices I used here, with firmwares 1.e 
> and 2.7. However, on tm6000, it sends the firmware on packages with
> up to 12 or 13 bytes, and it requires a delay before sending the next
> packet, otherwise the tm6000 hangs.
>
> Another problem is that the firmware load may fail (due to the bad
> implementation of the i2c on tm6000/tm6010). So, the code should ideally
> check if the firmware were loaded, by reading the firmware version at the
> end. However, reading from i2c is very problematic, since it sometimes
> read from the wrong place. On the tests I did here, the original drivers
> weren't reading back the firmware version, probably due to this bug.
>   
My hybrid-stick with tm6010 chip use a special request ( requests 0x32 +
0x33) for quitting i2c transfer. so it can write correct the firmware
and can read tuner number and versions. Actually I tested next patch for
sync between tuner and demodulator and I have data by scanning digital
channels (one time), but  other test dos not data. I've test firmware
load 13, 64  and 3500 bytes and all works.

Cheers,

Stefan Ringel

-- 
Stefan Ringel <stefan.ringel@arcor.de>


  reply	other threads:[~2010-01-25 16:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18 15:31 Terratec Cinergy Hybrid XE (TM6010 Mediachip) Stefan Ringel
2010-01-18 15:43 ` Devin Heitmueller
2010-01-18 20:05   ` Stefan Ringel
2010-01-18 20:08     ` Devin Heitmueller
2010-01-25 14:35 ` Mauro Carvalho Chehab
2010-01-25 16:12   ` Stefan Ringel [this message]
     [not found]     ` <4B5DF134.7080603@redhat.com>
     [not found]       ` <4B5DF360.40808@arcor.de>
     [not found]         ` <4B5DF73F.9030807@redhat.com>
2010-01-25 21:02           ` Stefan Ringel
     [not found]             ` <4B6093E4.40706@arcor.de>
2010-01-27 19:32               ` Stefan Ringel
2010-01-27 20:47                 ` Mauro Carvalho Chehab
2010-01-31 13:28                   ` Stefan Ringel
  -- strict thread matches above, loose matches on Subject: below --
2010-01-17 18:05 Stefan Ringel
2010-01-15  9:42 Stefan Ringel
2010-01-15  9:41 Stefan Ringel
2010-01-14 16:27 Stefan Ringel
2010-01-13 19:45 Stefan Ringel
2010-01-13 19:51 ` Devin Heitmueller
2010-01-10 19:04 Stefan Ringel

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=4B5DC2EA.3090706@arcor.de \
    --to=stefan.ringel@arcor.de \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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