All of lore.kernel.org
 help / color / mirror / Atom feed
From: elchhome@gmx.de
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Dell OEM Soundblaster Live 5.1 with different PCI ID
Date: Thu, 19 Dec 2002 11:47:48 +0100	[thread overview]
Message-ID: <3E01A3D4.20908@gmx.de> (raw)
In-Reply-To: s5hu1hauvxh.wl@alsa2.suse.de

Hello Takashi,

thanks for your fast answer :)
I will give you feedback at latest monday, because I am not at home at 
the moment
you are right, this is emu10k1 not audigy
regards
Andreas


Takashi Iwai schrieb:

>At Thu, 19 Dec 2002 10:45:22 +0100,
>elchhome@gmx.de wrote:
>  
>
>>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?
>>    
>>
>
>please try the attached patch.
>this will add the entry as emu10k1 (sb live!).  it seems that the chip
>is emu10k1, not audigy.
>if it works, please let me know.  i'll commit it to cvs.
>
>
>thanks,
>
>Takashi
>  
>




-------------------------------------------------------
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/

  reply	other threads:[~2002-12-19 10:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19  9:45 Dell OEM Soundblaster Live 5.1 with different PCI ID elchhome
2002-12-19 10:47 ` Takashi Iwai
2002-12-19 10:47   ` elchhome [this message]
  -- 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=3E01A3D4.20908@gmx.de \
    --to=elchhome@gmx.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --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.