All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2 errors in 2.6.12
Date: Sun, 19 Jun 2005 15:07:35 +0100	[thread overview]
Message-ID: <200506191507.35831.nick@linicks.net> (raw)

Replying to myself...

> Here is a page with the ID and chipsets of the cards:
> 
> http://www.digit-life.com/articles/livetolive51/
> 
> I am going to attempt to add my card into emu10k1_main.c to get it set
> right:
> 
> 0 [Unknown        ]: EMU10K1 - SB Live [Unknown]
>                      SB Live [Unknown] (rev.7, serial:0x80611102) at
>                      0xe000,
> irq 5
> 
> From that 'livetolive51' page I am told I have:
> SB0060 - SBlive! Value (PCI\VEN_1102&DEV_0002&SUBSYS_80611102)

This worked fine, but fishing around, I see 'new' cards ID's are added all the 
time:

http://cvs.sourceforge.net/viewcvs.py/alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c?rev=1.58&view=log

so eventually the [UKNOWN] bit will disappear and alsamixer settings will 
remain between different version kernels (2.6.1x[.x]) then.

Nick
-- 
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."

             reply	other threads:[~2005-06-19 14:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-19 14:07 Nick Warne [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-19 10:04 2 errors in 2.6.12 Nick Warne
2005-06-19 11:25 ` Nick Warne
2005-06-19  7:57 Michal Semler
     [not found] ` <20050728214851.44877164.akpm@osdl.org>
2005-07-31 11:51   ` Michal Semler
2005-07-31 17:31     ` Andrew Morton
2005-07-31 17:53       ` Michael Krufky
2005-08-01  9:16         ` CIJOML
     [not found]           ` <1122894516.5340.9.camel@pc08.localdom.local>
     [not found]             ` <20050801201017.G77710@nebuchadnezzar.smejdil.cz>
2005-08-01 19:55               ` hermann pitton
2005-08-01 20:02                 ` Michael Krufky
2005-08-01 18:03         ` CIJOML

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=200506191507.35831.nick@linicks.net \
    --to=nick@linicks.net \
    --cc=linux-kernel@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.