From: hermann pitton <hermann-pitton@arcor.de>
To: "tomlohave@gmail.com" <tomlohave@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: patch for lifeview hybrid mini
Date: Tue, 17 Aug 2010 02:24:45 +0200 [thread overview]
Message-ID: <1282004685.8749.50.camel@pc07.localdom.local> (raw)
In-Reply-To: <4C67790D.3060600@gmail.com>
Hi,
Am Sonntag, den 15.08.2010, 07:20 +0200 schrieb tomlohave@gmail.com:
> Hi,
>
> the proposed patch is 6 month old and the owner of the card does not
> give any more sign of life for the support of the radio.
> can someone review it and push it as is?
>
> Cheers,
>
> Signed-off-by: thomas genty<tomlohave@gmail.com>
>
Thomas, just some quick notes, since nobody else cares.
The m$ regspy gpio logs do show only gpio22 changing for analog and
DVB-T and this should be the out of reference AGC control on a hopefully
single hybrid tuner on that device called DUO.
Remember, gpios not set in the mask of the analog part of the device do
not change/switch anything, but those set there will change to zero even
without explicit gpio define for that specific analog input.
Out of historical reasons, we don't have this in our logs for DVB, also
else they would be littered by the changing gpios for the TS/MPEG
interface, but should be OK. We don't need to mark DVB related gpio
stuff in the analog gpio mask, since we need to use some sort of hack to
switch gpios on saa713x in DVB mode.
dvb and v4l still don't know much about what each other subsystem does
on that, but we have some progress.
So, for now, I don't know for what gpio21 high in analog TV mode should
be good, since the m$ driver seems not to do anything on that one, for
what we have so far. Also it is common on later LifeView stuff (arrgh),
but always is present in related logs then too.
If ever needed,
despite of that line inputs and muxes are also totally unconfirmed, and
radio is plain madness ...
drop the radio support for now, mark the external inputs as untested and
I give some reviewed by so far with headaches.
If we can't get more from here anymore, we must let it bounce.
Cheers,
Hermann
next prev parent reply other threads:[~2010-08-17 0:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-15 5:20 patch for lifeview hybrid mini tomlohave
2010-08-17 0:24 ` hermann pitton [this message]
2010-08-23 14:15 ` tomlohave
[not found] ` <4C72804F.1090201@gmail.com>
2010-08-23 23:49 ` hermann pitton
2010-08-24 6:35 ` [linux-dvb] " tomlohave
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=1282004685.8749.50.camel@pc07.localdom.local \
--to=hermann-pitton@arcor.de \
--cc=linux-media@vger.kernel.org \
--cc=tomlohave@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