All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>,
	James Courtier-Dutton <James@superbug.co.uk>
Subject: Re: SBLive! subsystem 8066
Date: Fri, 20 Jan 2006 21:22:53 -0500	[thread overview]
Message-ID: <1137810173.3241.95.camel@mindpipe> (raw)
In-Reply-To: <s5hlkxb7xg8.wl%tiwai@suse.de>

On Fri, 2006-01-20 at 16:04 +0100, Takashi Iwai wrote:
> At Tue, 17 Jan 2006 17:18:51 -0500,
> Lee Revell wrote:
> > 
> > ...is still "Unknown" by the ALSA driver.
> > 
> > Can we get something like this merged before the 1.0.11 release:
> > 
> > +       /* See ALSA bug #1036 - model is from windows driver */
> > +       {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80661102,
> > +        .driver = "EMU10K1", .name = "SB Live 5.1 [SB0220]", 
> > +        .id = "Live",
> > +        .emu10k1_chip = 1,
> > +        .ac97_chip = 1,
> > +        .sblive51 = 1} ,
> > 
> > It might be SB0222, I am not 100% certain.
> 
> Isn't it already in CVS?  The name is different (it's "SB Live 5.1
> Dell OEM [SB0220]", though).

I thought so too but "cvs diff" said it was not, and now ALSA CVS is
broken, AGAIN...

$ cvs diff pci/emu10k1/emu10k1_main.c
cvs [diff aborted]: end of file from server (consult above messages if
any)

Lee



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

  reply	other threads:[~2006-01-21  2:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 22:18 SBLive! subsystem 8066 Lee Revell
2006-01-20 15:04 ` Takashi Iwai
2006-01-21  2:22   ` Lee Revell [this message]
2006-01-21  2:30     ` Lee Revell

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=1137810173.3241.95.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=James@superbug.co.uk \
    --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.