From: Gerd Knorr <kraxel@suse.de>
To: Takashi Iwai <tiwai@suse.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: Tue, 19 Oct 2004 18:13:40 +0200 [thread overview]
Message-ID: <20041019161340.GA12001@bytesex> (raw)
In-Reply-To: <s5h3c0cjd24.wl@alsa2.suse.de>
> > (1) The ones where you can get audio data out of PCI function .1
> > (4) Cards where PCI function .1 is simply unused, i.e. you get either
> > nothing or just noise if you try to record audio from there.
> > I think the alsa driver should only try to use cards which fall into
> > group (1), not everything but (2). Problem with that is that it simply
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > isn't known for most cards whenever they are in group (1) or (4).
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> I see the device list in drivers/media/video/bttv-cards.c as mentioned
> in Gerd's original post. Which ones can be as the white list entries
> for ALSA?
Well, the problem is that no such list exists right now, I didn't keep
track of whenever Function .1 can do audio or not in bttvs card database
because bttv doesn't care, it does video only ...
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.
I know it works with my wintv (0070:13eb), but thats it :-/
Gerd
-------------------------------------------------------
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-19 16:13 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 [this message]
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
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=20041019161340.GA12001@bytesex \
--to=kraxel@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=holger@qanu.de \
--cc=linux-dvb@linuxtv.org \
--cc=perex@suse.cz \
--cc=tiwai@suse.de \
/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.