From: Steven Toth <stoth@kernellabs.com>
To: linux-media@vger.kernel.org
Cc: hermann pitton <hermann-pitton@arcor.de>,
Mike Isely <isely@isely.net>, Andy Walls <awalls@radix.net>,
Roger <rogerx@sdf.lonestar.org>
Subject: Re: s5h1411_readreg: readreg error (ret == -5)
Date: Mon, 15 Jun 2009 10:41:10 -0400 [thread overview]
Message-ID: <4A365D86.1070803@kernellabs.com> (raw)
In-Reply-To: <1244851654.3777.3.camel@pc07.localdom.local>
hermann pitton wrote:
> [snip]
>> The most undiscovered configurations seem to be such ones about antenna
>> inputs and their switching. Again according to Hartmut, and he did not
>> know exactly what is going on here, some for us and him at this point
>> unknown checksums are used to derive even that information :(
>>
>> For what I can see, and I might be of course still wrong, we can also
>> not determine plain digital tuner types, digital demodulator types of
>> any kind and the type of possibly present second and third tuners, but
>> at least their addresses, regularly shared by multiple chips, become
>> often visible. (some OEMs have only 0xff still for all that)
>
> forgot, and not any LNB supplies behind some i2c bridges, shared or not
> on whatever.
The use of Hauppauge eeproms I consider advisory at best. Yes, they have
reasonably good fields to identify tuners, IR but a number of recent silicon
additions (last 3 years) to the product line is not fully implemented in the
eeproms. Some of the important feature decisions is done purely in software
based on sub id for example.
In general I agree with Hermann's comments, that is, where possible making
maximum use of the eeprom.
--
Steven Toth - Kernel Labs
http://www.kernellabs.com
next prev parent reply other threads:[~2009-06-15 14:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 7:40 s5h1411_readreg: readreg error (ret == -5) Roger
2009-06-11 4:05 ` Mike Isely
2009-06-11 14:53 ` Steven Toth
2009-06-11 18:48 ` Mike Isely
2009-06-11 22:28 ` Roger
2009-06-12 20:33 ` Mike Isely
2009-06-12 21:12 ` Andy Walls
2009-06-12 21:27 ` Mike Isely
2009-06-12 22:39 ` hermann pitton
2009-06-13 0:07 ` hermann pitton
2009-06-13 3:08 ` Roger
2009-06-15 14:41 ` Steven Toth [this message]
2009-06-13 3:06 ` Roger
2009-06-13 3:12 ` Andy Walls
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=4A365D86.1070803@kernellabs.com \
--to=stoth@kernellabs.com \
--cc=awalls@radix.net \
--cc=hermann-pitton@arcor.de \
--cc=isely@isely.net \
--cc=linux-media@vger.kernel.org \
--cc=rogerx@sdf.lonestar.org \
/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