From: Ondrej Zary <linux@rainbow-software.org>
To: linux-media@vger.kernel.org
Subject: [RFC PATCH 0/3] bttv: convert to generic TEA575x interface
Date: Tue, 14 May 2013 22:54:42 +0200 [thread overview]
Message-ID: <1368564885-20940-1-git-send-email-linux@rainbow-software.org> (raw)
Hello,
this patch series removes the tea575x code from bttv and uses the common
tea575x driver instead. Only set_frequency is implemented (signal/stereo
detection or seek would require more changes to bttv).
It works fine on Video Highway Xtreme but I don't have the Miro/Pinnacle or
Terratec Active Radio Upgrade to test.
Miro/Pinnacle seems to be simple and should work.
However, I don't understand the Terratec Active Radio Upgrade code. The HW
seems to need IOR, IOW and CSEL signals that were taken from ISA bus on
older cards (IOR and IOW directly and CSEL from some address decoder) and
are emulated here using GPIOs. But the code manipulating these signals in
bttv seems to be broken - it never asserts the IOR signal. If anyone has
this HW, please test if I got that right.
--
Ondrej Zary
next reply other threads:[~2013-05-14 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 20:54 Ondrej Zary [this message]
2013-05-14 20:54 ` [PATCH 1/3] tea575x-tuner: move HW init to a separate function Ondrej Zary
2013-05-14 20:54 ` [PATCH 2/3] bttv: stop abusing mbox_we for sw_status Ondrej Zary
2013-05-14 20:54 ` [PATCH 3/3] bttv: Convert to generic TEA575x interface Ondrej Zary
2013-06-03 8:46 ` Hans Verkuil
2013-07-26 12:59 ` Hans Verkuil
2013-06-03 8:50 ` [RFC PATCH 0/3] bttv: convert " Hans Verkuil
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=1368564885-20940-1-git-send-email-linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=linux-media@vger.kernel.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