From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: "Eduardo Valentin" <edubezval@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
Eduardo Valentin <eduardo.valentin@indt.org.br>,
Linux and Kernel Video <video4linux-list@redhat.com>,
Michael Krufky <mkrufky@linuxtv.org>,
Sakari Ailus <sakari.ailus@nokia.com>
Subject: Re: [PATCH 0/1] Add support for TEA5761 (from linux-omap)
Date: Wed, 4 Jun 2008 11:44:37 -0300 [thread overview]
Message-ID: <20080604114437.0cf0dd69@gaivota> (raw)
In-Reply-To: <a0580c510806040725i8070ce1n2445c5a422bb88a3@mail.gmail.com>
Hi Eduardo,
On Wed, 4 Jun 2008 10:25:23 -0400
"Eduardo Valentin" <edubezval@gmail.com> wrote:
> Hi Mauro and Michael,
>
> Thanks for pointing that there were a duplicated work. If there is any
> update on the current driver, I'll contact you. I'm not the author of
> this driver, but I'm interested in some points here.
>
> This chip is used on n800 FM radio. That's why this version came from
> linux-omap.
> Anyway, one quest that came from my mind, taking a brief look into
> this two drivers,
> I see they use different interfaces to register a FM radio driver, and
> more they are located
> under different places inside the tree. So, what is more recommended
> for FM radio drivers?
> being under drivers/media/radio/ or under drivers/media/common/tunners/ ?
> What is the API more recommended dvb_tuner_ops or video_device ? I
> wonder also what current applications are using.
Good point. some radio tuners are used inside video boards. Before, this were
located inside drivers/media/video. Now, they are at common/tuners. This seems
to be a better place.
It should be noticed that tea5761 is an I2C device. So, you'll probably need a
counterpart module, at media/radio, that will provice I2C access methods needed
on N800.
Cheers,
Mauro
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-06-04 14:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 15:25 [PATCH 0/1] Add support for TEA5761 (from linux-omap) Eduardo Valentin
2008-06-03 15:25 ` [PATCH 1/1] Add support for tea5761 chip Eduardo Valentin
2008-06-03 15:44 ` [PATCH 0/1] Add support for TEA5761 (from linux-omap) Michael Krufky
2008-06-03 21:56 ` Mauro Carvalho Chehab
2008-06-04 14:25 ` Eduardo Valentin
2008-06-04 14:44 ` Mauro Carvalho Chehab [this message]
2008-06-04 15:20 ` mkrufky
2008-06-04 20:13 ` Eduardo Valentin
2008-06-04 20:22 ` Mauro Carvalho Chehab
2008-06-04 21:06 ` mkrufky
2008-06-04 21:44 ` Eduardo Valentin
2008-06-05 15:24 ` Eduardo Valentin
2008-06-05 15:29 ` mkrufky
2008-06-29 12:04 ` Mauro Carvalho Chehab
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=20080604114437.0cf0dd69@gaivota \
--to=mchehab@infradead.org \
--cc=eduardo.valentin@indt.org.br \
--cc=edubezval@gmail.com \
--cc=mkrufky@linuxtv.org \
--cc=sakari.ailus@nokia.com \
--cc=tony@atomide.com \
--cc=video4linux-list@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