From: Takashi Iwai <tiwai@suse.de>
To: Jean Delvare <khali@linux-fr.org>
Cc: Lee Revell <rlrevell@joe-job.com>,
James Courtier-Dutton <James@superbug.co.uk>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Jaroslav Kysela <perex@suse.cz>
Subject: Re: Re: 2.6.12-rc1-mm3, sound card lost id
Date: Wed, 30 Mar 2005 14:24:32 +0200 [thread overview]
Message-ID: <s5hekdxgw3j.wl@alsa2.suse.de> (raw)
In-Reply-To: <20050329231345.281e7323.khali@linux-fr.org>
At Tue, 29 Mar 2005 23:13:45 +0200,
Jean Delvare wrote:
>
> Hi Lee,
>
> > Here is the patch (against ALSA CVS) in its preferred format. You
> > will probably have to apply it by hand. If the mixer settings can't
> > be restored you'll have to do it manually or edit asound.state by
> > hand.
> >
> > Lee
> >
> > Index: alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c
> > ===================================================================
> > RCS file: /cvsroot/alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c,v
> > retrieving revision 1.49
> > diff -u -r1.49 emu10k1_main.c
> > --- alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c 27 Mar 2005 14:00:54 -0000 1.49
> > +++ alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c 29 Mar 2005 20:51:44 -0000
> > @@ -693,6 +693,10 @@
> > .driver = "EMU10K1", .name = "SBLive! Platinum [CT4760P]",
> > .emu10k1_chip = 1,
> > .ac97_chip = 1} ,
> > + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80271102,
> > + .driver = "EMU10K1", .name = "SBLive! Value [CT4832]",
> > + .emu10k1_chip = 1,
> > + .ac97_chip = 1} ,
> > {.vendor = 0x1102, .device = 0x0002,
> > .driver = "EMU10K1", .name = "SB Live [Unknown]",
> > .emu10k1_chip = 1,
>
> Unsurprisingly, my card is now named CT4832. I had to edit
> /etc/asound.state manually to get my mixer settings back (with some
> warnings, but I get some sound).
>
> Not sure I quite see the idea of renaming from "Live", which the user
> will understand, to (I suppose) the exact chip name on the card, while
> the user has certainly no idea what it is. But heh I'm not an ALSA
> developer, there must be a good reason.
Changing the name to more descriptive one is a good thing, IMO.
But, of course, it's a regression if the system gets (somehow) broken
after the update.
We can add a hack to set id explicitly to be compatible with older
version...
Takashi
-------------------------------------------------------
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
prev parent reply other threads:[~2005-03-30 12:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050325002154.335c6b0b.akpm@osdl.org>
2005-03-26 10:19 ` 2.6.12-rc1-mm3, sound card lost id Jean Delvare
[not found] ` <20050326111945.5eb58343.khali@linux-fr.org>
2005-03-29 12:24 ` Takashi Iwai
2005-03-29 17:57 ` Jean Delvare
2005-03-29 20:17 ` Lee Revell
2005-03-29 20:46 ` Jean Delvare
2005-03-29 20:52 ` Lee Revell
2005-03-29 21:13 ` Jean Delvare
2005-03-29 21:18 ` Lee Revell
2005-03-29 20:53 ` James Courtier-Dutton
2005-03-30 7:18 ` Jaroslav Kysela
2005-03-30 12:24 ` Takashi Iwai [this message]
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=s5hekdxgw3j.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=James@superbug.co.uk \
--cc=akpm@osdl.org \
--cc=alsa-devel@alsa-project.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=rlrevell@joe-job.com \
/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