From: Takashi Iwai <tiwai@suse.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Gerd Knorr <kraxel@suse.de>, Jaroslav Kysela <perex@suse.cz>,
Holger Waechtler <holger@qanu.de>,
dvb list <linux-dvb@linuxtv.org>,
alsa-devel@lists.sourceforge.net
Subject: Re: Problem with Avermedia 771
Date: Wed, 20 Oct 2004 17:20:15 +0200 [thread overview]
Message-ID: <s5hwtxlh0wg.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.HPX.4.33n.0410201649590.9471-100000@studcom.urz.uni-halle.de>
At Wed, 20 Oct 2004 17:02:34 +0200 (METDST),
Clemens Ladisch wrote:
>
> Takashi Iwai wrote:
> > > > So we'll have to build a whitelist from scratch from user feedback, and
> > > > maybe add a insmod option so you can ask the driver to grab the device
> > > > even if not whitelisted for easy use.
> >
> > The experimental patch for this is below.
>
> Below is the same patch with entries for WinTV cards (the old default
> entries were intended to handle those).
Thanks!
> I don't know of any other cards with working audio function (all
> feedback I got for other cards was negative).
>
> I'm going to write some documention, too.
Great.
Should the driver put some kernel info when the device is probed but
disabled? Something like:
bt87x: the device XXXX:YYYY is not in the list of supported devices.
For using this driver for unsupported devices, too,
specify load_all=1 module option.
One concern is again hotplug. This might be annoying although it's
harmless.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-20 15:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <416ED29A.7060200@qanu.de>
2004-10-15 10:11 ` Problem with Avermedia 771 Gerd Knorr
2004-10-15 11:03 ` Jaroslav Kysela
2004-10-15 11:58 ` [Alsa-devel] " Holger Waechtler
2004-10-18 13:01 ` Gerd Knorr
2004-10-18 14:50 ` Takashi Iwai
2004-10-19 16:13 ` Gerd Knorr
2004-10-20 13:06 ` Takashi Iwai
2004-10-20 13:17 ` Takashi Iwai
2004-10-20 15:02 ` Clemens Ladisch
2004-10-20 15:20 ` Takashi Iwai [this message]
2004-10-21 7:22 ` Clemens Ladisch
2004-10-21 8:59 ` [Alsa-devel] " Gerd Knorr
2004-10-21 10:05 ` Takashi Iwai
2004-10-21 10:18 ` Gerd Knorr
2004-10-21 10:38 ` Takashi Iwai
2004-10-21 11:43 ` Gerd Knorr
2004-10-21 12:11 ` Takashi Iwai
2004-10-21 16:36 ` Takashi Iwai
2004-10-25 9:36 ` Clemens Ladisch
2004-10-20 15:27 ` Gerd Knorr
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=s5hwtxlh0wg.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=holger@qanu.de \
--cc=kraxel@suse.de \
--cc=linux-dvb@linuxtv.org \
--cc=perex@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.