From: Lee Revell <rlrevell@joe-job.com>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: [ALSA - driver 0000901]: The onboard audigyls chip on msi k8 diamond motherboard not recognized. Path supplied.
Date: Sat, 12 Feb 2005 19:47:07 -0500 [thread overview]
Message-ID: <1108255628.3273.20.camel@krustophenia.net> (raw)
In-Reply-To: <9d29558e3c3fabff090c6db74666f973@bugtrack.alsa-project.org>
On Sun, 2005-02-13 at 01:21 +0100, bugtrack@alsa-project.org wrote:
> *nods*, seems to be better:
>
> 0 [CA0106 ]: CA0106 - CA0106
> Live! by MSI [SB0438] at 0xde00 irq 233
Since it's been established that the CA0106 based devices have basically
nothing in common with the SBLive/emu10k1, can we please, please not
call it "Live!"? It's obvious from Creative's marketing that they want
to pass those cheap "software soundcards" off as equivalent to an
SBLive/Audigy. Please, let's not help them.
Lee
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-13 0:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 0:21 [ALSA - driver 0000901]: The onboard audigyls chip on msi k8 diamond motherboard not recognized. Path supplied bugtrack
2005-02-13 0:47 ` Lee Revell [this message]
2005-02-13 11:53 ` James Courtier-Dutton
2005-02-13 19:35 ` Lee Revell
-- strict thread matches above, loose matches on Subject: below --
2005-05-28 10:20 bugtrack
2005-03-19 17:17 bugtrack
2005-02-13 0:27 bugtrack
2005-02-13 0:08 bugtrack
2005-02-12 23:54 bugtrack
2005-02-12 23:18 bugtrack
2005-02-12 21:47 bugtrack
2005-02-12 13:36 bugtrack
2005-02-11 23:56 bugtrack
2005-02-11 22:49 bugtrack
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=1108255628.3273.20.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=James@superbug.co.uk \
--cc=alsa-devel@alsa-project.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.