From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: Greg Stark <gsstark@mit.edu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: pchdtv 3000 cx88 audio very very low level
Date: Mon, 10 Apr 2006 15:38:31 +0200 [thread overview]
Message-ID: <20060410133831.GA22079@rhlx01.fht-esslingen.de> (raw)
In-Reply-To: <87d5ftmt5p.fsf@stark.xeocode.com>
Hi,
On Fri, Apr 07, 2006 at 09:06:42AM -0400, Greg Stark wrote:
> Andreas Mohr <andi@rhlx01.fht-esslingen.de> writes:
>
> > IOW, you need to examine the driver sources of cx88xx, cx8800, cx88_alsa,
> > btcx_risc, tveeprom (?) for some multiplexer bit mask and tweak/twiddle that
> > for your tuner until you manage to hear something properly.
>
> Hm. Except nobody else seems to have this problem with the pchdtv 3000 card.
> And there are plenty of HOWTOs and FAQs online for it. Perhaps nobody else is
> trying to use the NTSC tuner on it though.
A distant possibility might be that your card is a very specific rare revision
of that thing and thus doesn't have a proper card type entry for it due to
almost nobody else having that card.
In the TV card area (just as in the WLAN card area) there are quite some cards
sold under the *very same* name but wildly (or not so wildly but sufficiently)
differing hardware (those manufacturer b****rds burn in hell please, thanks).
> I'm assuming that if cx88_alsa found any audio devices on the card then it
> would create a card1 listed in /proc/asound/cards ? It isn't doing that
> currently. Apparently not all cx88 cards provide a mixer interface.
I'm not that familiar with ALSA user-space interface specifics (rather than
kernel-level), sorry.
Andreas Mohr
next prev parent reply other threads:[~2006-04-10 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 2:57 Greg Stark
2006-04-07 9:24 ` Andreas Mohr
2006-04-07 13:06 ` Greg Stark
2006-04-10 13:38 ` Andreas Mohr [this message]
2006-04-10 23:55 ` Michael Krufky
2006-04-11 7:42 ` Andreas Mohr
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=20060410133831.GA22079@rhlx01.fht-esslingen.de \
--to=andi@rhlx01.fht-esslingen.de \
--cc=gsstark@mit.edu \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®