Re: [Alsa-devel] Re: 2.6.12-rc1-mm3, sound card lost id

[Takashi Iwai]

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/