From: elchhome@gmx.de
To: alsa-devel@lists.sourceforge.net
Subject: Dell OEM Soundblaster Live 5.1 with different PCI ID
Date: Thu, 19 Dec 2002 10:45:22 +0100 [thread overview]
Message-ID: <3E019532.6080001@gmx.de> (raw)
Hello Friends,
Dell ships since a month an OEM Soundblaster Live 5.1 (sb0200) with a
different PCI ID
for original sblive you got 1102:0002
the Dell version has 1102:0006
I got no sound with the actual version of the sound driver.
Could anyone be so kind to incorporate this into the source code?
I am willing to supply all information which is needed.
If the problem was allready dealt with by other threads, please don't
flame me ;)
Thanks & regards
-------------------------------------------------------
This SF.NET email is sponsored by: Geek Gift Procrastinating?
Get the perfect geek gift now! Before the Holidays pass you by.
T H I N K G E E K . C O M http://www.thinkgeek.com/sf/
next reply other threads:[~2002-12-19 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 9:45 elchhome [this message]
2002-12-19 10:47 ` Dell OEM Soundblaster Live 5.1 with different PCI ID Takashi Iwai
2002-12-19 10:47 ` elchhome
-- strict thread matches above, loose matches on Subject: below --
2002-12-19 19:02 Jeffrey Kent Ridenour
2002-12-20 3:38 Jeff Ridenour
2002-12-20 15:02 ` Takashi Iwai
2002-12-21 14:38 ` Thorsten Becker
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=3E019532.6080001@gmx.de \
--to=elchhome@gmx.de \
--cc=alsa-devel@lists.sourceforge.net \
/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