From: Takashi Iwai <tiwai@suse.de>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: alsa-devel@alsa-project.org, linux-media@vger.kernel.org,
Ondrej Zary <linux@rainbow-software.org>,
jirislaby@gmail.com,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: radio-maestro broken (conflicts with snd-es1968)
Date: Mon, 14 Mar 2011 10:53:33 +0100 [thread overview]
Message-ID: <s5hei6ahvtu.wl%tiwai@suse.de> (raw)
In-Reply-To: <201103121952.39850.hverkuil@xs4all.nl>
At Sat, 12 Mar 2011 19:52:39 +0100,
Hans Verkuil wrote:
>
> On Saturday, March 12, 2011 19:19:00 Ondrej Zary wrote:
> > Hello,
> > the radio-maestro driver is badly broken. It's intended to drive the radio on
> > MediaForte ESS Maestro-based sound cards with integrated radio (like
> > SF64-PCE2-04). But it conflicts with snd_es1968, ALSA driver for the sound
> > chip itself.
> >
> > If one driver is loaded, the other one does not work - because a driver is
> > already registered for the PCI device (there is only one). This was probably
> > broken by conversion of PCI probing in 2006:
> > ttp://lkml.org/lkml/2005/12/31/93
> >
> > How to fix it properly? Include radio functionality in snd-es1968 and delete
> > radio-maestro?
>
> Interesting. I don't know anyone among the video4linux developers who has
> this hardware, so the radio-maestro driver hasn't been tested in at least
> 6 or 7 years.
>
> The proper fix would be to do it like the fm801.c alsa driver does: have
> the radio functionality as an i2c driver. In fact, it would not surprise
> me at all if you could use the tea575x-tuner.c driver (in sound/i2c/other)
> for the es1968 and delete the radio-maestro altogether.
I guess simply porting radio-maestro codes into snd-es1968 would work
without much hustles, and it's a bit safe way to go for now; smaller
changes have less chance for breakage, and as little people seem using
this driver, it'd be better to take a safer option, IMO.
If we have active testers for both devices, it's nicer to go forward
to clean-up works indeed, though.
thanks,
Takashi
> Both are for the tea575x tuner, although radio-maestro seems to have better
> support for the g_tuner operation. It doesn't seem difficult to add that to
> tea575x-tuner.c.
>
> The fm801 code for driving the tea575x is pretty horrible and it should be
> possible to improve that. I suspect that those read/write/mute functions
> really belong in tea575x-tuner.c and that only the low-level gpio actions
> need to be in the fm801/es1968 drivers.
>
> Hope this helps.
>
> Regards,
>
> Hans
>
> BTW: if anyone has spare hardware for testing the radio-maestro/tea575x-tuner,
> then I'm interested.
>
> --
> Hans Verkuil - video4linux developer - sponsored by Cisco
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
next prev parent reply other threads:[~2011-03-14 9:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 18:19 radio-maestro broken (conflicts with snd-es1968) Ondrej Zary
2011-03-12 18:52 ` Hans Verkuil
2011-03-14 9:53 ` Takashi Iwai [this message]
2011-03-14 9:59 ` Hans Verkuil
2011-03-14 10:08 ` Takashi Iwai
2011-03-14 10:28 ` Ondrej Zary
2011-03-14 10:29 ` [alsa-devel] " Takashi Iwai
2011-03-14 11:57 ` Hans Verkuil
2011-03-19 15:32 ` [RFC PATCH 1/3] tea575x-tuner: various improvements Ondrej Zary
2011-03-21 11:48 ` Takashi Iwai
2011-03-22 18:39 ` Mauro Carvalho Chehab
2011-03-22 19:02 ` Hans Verkuil
2011-03-25 21:40 ` Ondrej Zary
2011-03-26 10:19 ` Hans Verkuil
2011-03-29 19:25 ` Ondrej Zary
2011-03-29 19:39 ` Hans Verkuil
2011-03-19 15:33 ` [RFC PATCH 2/3] tea575x-tuner: remove dev_nr Ondrej Zary
2011-03-19 15:33 ` [RFC PATCH 3/3] es1968: add radio (tea575x tuner) support Ondrej Zary
2011-03-19 16:23 ` [RFC PATCH 4/3] remove radio-maestro Ondrej Zary
2011-03-22 18:44 ` Mauro Carvalho Chehab
2011-03-23 7:13 ` Takashi Iwai
2011-03-22 19:03 ` Hans Verkuil
2011-03-14 9:46 ` radio-maestro broken (conflicts with snd-es1968) Takashi Iwai
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=s5hei6ahvtu.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=hverkuil@xs4all.nl \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@rainbow-software.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;
as well as URLs for NNTP newsgroup(s).