From: Takashi Iwai <tiwai@suse.de>
To: linux-sound@vger.kernel.org
Subject: Re: Realtek ALC650E support in 2.[45]?
Date: Tue, 01 Jul 2003 09:18:50 +0000 [thread overview]
Message-ID: <marc-linux-sound-105705131930053@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-105696297412952@msgid-missing>
At Mon, 30 Jun 2003 21:52:19 +1000,
CaT wrote:
>
> On Mon, Jun 30, 2003 at 12:03:50PM +0200, Takashi Iwai wrote:
> > At Mon, 30 Jun 2003 18:49:43 +1000,
> > CaT wrote:
> > > Anyways, does it support it? I'd prefer fully OS driver support and
> > > don't mind using patches but prefer to be able to compile the driver
> > > into the kernel as I like the lack of messyness that comes with
> > > monolithic kernels.
> >
> > ALC650(E) is the AC97 codec chip. There must be an audio core in
> > addition, most likely Intel ICH chips or VIA 82xx chips. Both are
> > supported by ALSA, snd-intel8x0 and snd-via8xx drivers, respectively.
> > On OSS, they are i810_audio and via82cxxx_audio drivers.
> >
> > ALC650E is a revision E of ALC650, which has some minor extensions
> > (like S/PDIF support) but mostly identical with ALC650.
> > So both should work.
>
> Aha. Ok. What about with an Nvidia2 backend (MCP-T) to all this?
it's (almost) compatible with Intel ICH and works with the recent
intel driver above.
Takashi
next prev parent reply other threads:[~2003-07-01 9:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 8:49 Realtek ALC650E support in 2.[45]? CaT
2003-06-30 10:03 ` Takashi Iwai
2003-06-30 11:52 ` CaT
2003-07-01 9:18 ` Takashi Iwai [this message]
2003-07-01 15:25 ` CaT
-- strict thread matches above, loose matches on Subject: below --
2003-06-30 8:49 CaT
2003-06-30 10:03 ` Takashi Iwai
2003-06-30 11:52 ` CaT
2003-07-01 9:18 ` Takashi Iwai
2003-07-01 15:25 ` CaT
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=marc-linux-sound-105705131930053@msgid-missing \
--to=tiwai@suse.de \
--cc=linux-sound@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 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.