sound blaster name
Quoted 1 line · matthieu castet
Any new about this ?
Yes, James' patch is in ALSA CVS.
This should be submitted for the -stable tree, as some people are upgrading to 2.6.12 and losing their mixer settings.
Lee
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Hi,
Quoted 10 lines · Lee Revell
Quoted 1 line · matthieu castet
Any new about this ?
Yes, James' patch is in ALSA CVS.
This should be submitted for the -stable tree, as some people are upgrading to 2.6.12 and losing their mixer settings.
Yes but what about the missing entries that weren't added in the *cvs* and that I list in this mail [1] ?
thanks
Matthieu
[1]
Someone on lkml give this link : http://www.digit-life.com/articles/livetolive51/.
It containt some forgotten ids (CT4760, mothreboard series, EMU APS). SB0103 seem to be a full version (not value)
matthieu
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Quoted 22 lines · matthieu castet
Hi,
Quoted 11 lines · Lee Revell
Quoted 1 line · matthieu castet
Any new about this ?
Yes, James' patch is in ALSA CVS.
This should be submitted for the -stable tree, as some people are upgrading to 2.6.12 and losing their mixer settings.
Yes but what about the missing entries that weren't added in the *cvs* and that I list in this mail [1] ?
thanks
Matthieu
Quoted 10 lines
[1]
Someone on lkml give this link :
http://www.digit-life.com/articles/livetolive51/.It containt some forgotten ids (CT4760, mothreboard series, EMU APS). SB0103 seem to be a full version (not value)
matthieu
I thought I added those already to the CVS.
Matthieu, are there some still missing?
James
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Hi,
Quoted 6 lines · James Courtier-Dutton
matthieu castet wrote:
I thought I added those already to the CVS.
Matthieu, are there some still missing?
{.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80611102,
.driver = "EMU10K1", .name = "SBLive! Player 5.1 [SB0060]", .id = "Live", .emu10k1_chip = 1, .ac97_chip = 1, .sblive51 = 1}
is present 2 times.
SBLive motherboard (PCI\VEN_1102&DEV_0002&SUBSYS_002F1102) SBLive motherboard (PCI\VEN_1102&DEV_0002&SUBSYS_80251102) SBLive motherboard (PCI\VEN_1102&DEV_0002&SUBSYS_80631102) don't seem to be in cvs.
SB0103 don't seem to be a value version but a full version
Matthieu
PS :
I found other id on http://bbs.zol.com.cn/new/static_book2/17/924/17_226924.shtml, but I am too tired to list the missing one (there list 34 cards for EMU10K1, cvs has only 18, there are some for audigy)
[1102\0002]
; EMU10K1 Audio Chipset (SB Live!)
00201102=CT4850 SBLive! Value
00211102=CT4620 SBLive!
002F1102=Integrated SBLive!
00411102=CT4820 SBLive!
40011102=E-mu APS
80221102=CT4780 SBLive! Value
80231102=CT4790 SoundBlaster PCI512 OEM
80241102=CT4760 SBLive!
80251102=Integrated SBLive!
80261102=CT4830 SBLive! Value
80271102=CT4832 SBLive! Value
80281102=CT4870 SBLive! Value
80291102=CT4872 SBLive!
802A1102=CT4890 SB PCI256
802B1102=CT4891 SB PCI256
80311102=CT4831 SBLive! Value
80321102=CT4871 SBLive! Value
80331102=CT4893 SB PCI256
80351102=CT0060 SBLive!
80401102=CT4760 SBLive!
80501102=CT4820 SB PCI512
80511102=CT4850 SBLive! Value
80611102=SB0060 SBLive! 5.1
80621102=SB0100 SBLive! 5.1
80631102=Integrated SBLive! 5.1
80641102=SB0102 SBLive! 5.1
80651102=SB0220 SBLive! 5.1 Digital
80661102=SB0220 SBLive! 5.1 Digital
80671102=SB0220 SBLive! 5.1 Digital
80681102=CT0061 SBLive!
80691102=SB0101 SBLive! 5.1 Value
806A1102=SB0103 SBLive! 5.1
806B1102=SB0105 SBLive! 5.1
80711102=SB0150 Sound Blaster PCI512
[1102\0004]
; EMU10K2 Audio Chipset (SB Audigy Series)
00411102=CT4820 Audigy
00421102=CT0070 Audigy
00431102=CT0072 Audigy
00511102=SB0090 Audigy Platinum (EX)
00531102=CT0090 Audigy Player
10021102=SB0240 Audigy 2 Platinum 6.1
10031102=SB0243 Audigy 2 (OEM'd For Dell??)
10071102=SB0240 Audigy 2 Platinum 6.1
20021102=SB0350 Audigy ZS
20071102=SB0380 Audigy4 PRO
[1102\0007]
; Audigy LS Series
10011102=SB0310 Audigy LS
10021102=SB0312 Audigy LS
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Quoted 3 lines · matthieu castet
Someone on lkml give this link :
http://www.digit-life.com/articles/livetolive51/.
Wow, that dude is one serious hacker. He took a soldering iron to his soundcard to change the PCI ID just to unlock some features in the Windows driver? Couldn't you do that with strings(1) and a hex editor?
Lee
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Quoted 23 lines · matthieu castet
Hi,
Quoted 6 lines · James Courtier-Dutton
matthieu castet wrote:
I thought I added those already to the CVS.
Matthieu, are there some still missing?{.vendor =
0x1102, .device =0x0002, .subsystem =0x80611102,.driver = "EMU10K1", .name = "SBLive! Player 5.1 [SB0060]", .id = "Live", .emu10k1_chip = 1, .ac97_chip = 1, .sblive51 = 1}is present 2 times.
SBLive motherboard (PCI\VEN_1102&DEV_0002&SUBSYS_002F1102) SBLive motherboard (PCI\VEN_1102&DEV_0002&SUBSYS_80251102) SBLive motherboard (PCI\VEN_1102&DEV_0002&SUBSYS_80631102) don't seem to be in cvs.
Quoted 7 lines
SB0103 don't seem to be a value version but a full version
Matthieu
PS :
I found other id on http://bbs.zol.com.cn/new/static_book2/17/924/17_226924.shtml, but I am too tired to list the missing one (there list 34 cards for EMU10K1, cvs has only 18, there are some for audigy)
I attached a patch that sort the card by id, it will be a lot's easier to find the missing ones...
emu10k1_main.c.new renamed from emu10k1_main.c +37 -43
@@ -714,54 +714,49 @@ .emu10k2_chip = 1, .ca0102_chip = 1, .ac97_chip = 1} , - {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x40011102, - .driver = "EMU10K1", .name = "E-mu APS [4001]", - .id = "APS", - .emu10k1_chip = 1, - .ecard = 1} , - {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80611102, - .driver = "EMU10K1", .name = "SBLive! Player 5.1 [SB0060]", + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x806B1102, + .driver = "EMU10K1", .name = "SBLive! [SB0105]", .id = "Live", .emu10k1_chip = 1, .ac97_chip = 1, .sblive51 = 1} , - {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80641102, - .driver = "EMU10K1", .name = "SB Live 5.1", + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x806A1102, + .driver = "EMU10K1", .name = "SBLive! Value [SB0103]", .id = "Live", .emu10k1_chip = 1, .ac97_chip = 1, .sblive51 = 1} , - {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80401102, - .driver = "EMU10K1", .name = "SBLive! Platinum [CT4760P]", - .id = "Live", - .emu10k1_chip = 1, - .ac97_chip = 1} , - {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x00211102, - .driver = "EMU10K1", .name = "SBLive! [CT4620]", + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80691102, + .driver = "EMU10K1", .name = "SBLive! Value [SB0101]", .id = "Live", .emu10k1_chip = 1, .ac97_chip = 1, .sblive51 = 1} , - {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x00201102, - .driver = "EMU10K1", .name = "SBLive! Value [CT4670]", + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80641102, + .driver = "EMU10K1", .name = "SB Live 5.1", .id = "Live", .emu10k1_chip = 1, .ac97_chip = 1, .sblive51 = 1} , - {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80221102, - .driver = "EMU10K1", .name = "SBLive! Value [CT4780]", + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80611102, + .driver = "EMU10K1", .name = "SBLive! Player 5.1 [SB0060]", .id = "Live", .emu10k1_chip = 1, .ac97_chip = 1, .sblive51 = 1} , - {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80231102, - .driver = "EMU10K1", .name = "SB PCI512 [CT4790]", + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80511102, + .driver = "EMU10K1", .name = "SBLive! Value [CT4850]", .id = "Live", .emu10k1_chip = 1, .ac97_chip = 1, .sblive51 = 1} , - {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80261102, - .driver = "EMU10K1", .name = "SBLive! Value [CT4830]", + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80401102, + .driver = "EMU10K1", .name = "SBLive! Platinum [CT4760P]", + .id = "Live", + .emu10k1_chip = 1, + .ac97_chip = 1} , + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80321102, + .driver = "EMU10K1", .name = "SBLive! Value [CT4871]", .id = "Live", .emu10k1_chip = 1, .ac97_chip = 1,
@@ -772,50 +767,49 @@ .emu10k1_chip = 1, .ac97_chip = 1, .sblive51 = 1} , - {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80271102, - .driver = "EMU10K1", .name = "SBLive! Value [CT4832]", + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80281102, + .driver = "EMU10K1", .name = "SBLive! Value [CT4870]", .id = "Live", .emu10k1_chip = 1, .ac97_chip = 1, .sblive51 = 1} , - {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80511102, - .driver = "EMU10K1", .name = "SBLive! Value [CT4850]", + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80271102, + .driver = "EMU10K1", .name = "SBLive! Value [CT4832]", .id = "Live", .emu10k1_chip = 1, .ac97_chip = 1, .sblive51 = 1} , - {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80281102, - .driver = "EMU10K1", .name = "SBLive! Value [CT4870]", + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80261102, + .driver = "EMU10K1", .name = "SBLive! Value [CT4830]", .id = "Live", .emu10k1_chip = 1, .ac97_chip = 1, .sblive51 = 1} , - {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80321102, - .driver = "EMU10K1", .name = "SBLive! Value [CT4871]", + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80231102, + .driver = "EMU10K1", .name = "SB PCI512 [CT4790]", .id = "Live", .emu10k1_chip = 1, .ac97_chip = 1, .sblive51 = 1} , - {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80611102, - .driver = "EMU10K1", .name = "SBLive! Value [SB0060]", + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80221102, + .driver = "EMU10K1", .name = "SBLive! Value [CT4780]", .id = "Live", .emu10k1_chip = 1, .ac97_chip = 1, .sblive51 = 1} , - {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80691102, - .driver = "EMU10K1", .name = "SBLive! Value [SB0101]", - .id = "Live", + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x40011102, + .driver = "EMU10K1", .name = "E-mu APS [4001]", + .id = "APS", .emu10k1_chip = 1, - .ac97_chip = 1, - .sblive51 = 1} , - {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x806A1102, - .driver = "EMU10K1", .name = "SBLive! Value [SB0103]", + .ecard = 1} , + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x00211102, + .driver = "EMU10K1", .name = "SBLive! [CT4620]", .id = "Live", .emu10k1_chip = 1, .ac97_chip = 1, .sblive51 = 1} , - {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x806B1102, - .driver = "EMU10K1", .name = "SBLive! [SB0105]", + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x00201102, + .driver = "EMU10K1", .name = "SBLive! Value [CT4670]", .id = "Live", .emu10k1_chip = 1, .ac97_chip = 1,
Hi,
Quoted 1 line · matthieu castet
Hi,
here is the missing/misnamed cards :
maybe 5.1 flags should be adjusted...
Quoted 73 lines
[1102\0002]
; EMU10K1 Audio Chipset (SB Live!)
002F1102=Integrated SBLive!
00411102=CT4820 SBLive!
80241102=CT4760 SBLive!
80251102=Integrated SBLive!
80291102=CT4872 SBLive!
802A1102=CT4890 SB PCI256
802B1102=CT4891 SB PCI256
80331102=CT4893 SB PCI256
80351102=CT0060 SBLive!
80401102=CT4760 SBLive!
80501102=CT4820 SB PCI512
80621102=SB0100 SBLive! 5.1
80631102=Integrated SBLive! 5.1
80641102=SB0102 SBLive! 5.1
80651102=SB0220 SBLive! 5.1 Digital
80661102=SB0220 SBLive! 5.1 Digital
80671102=SB0220 SBLive! 5.1 Digital
80681102=CT0061 SBLive!
806A1102=SB0103 SBLive! 5.1 -> mark as value
806B1102=SB0105 SBLive! 5.1 -> not marked as 5.1
80711102=SB0150 Sound Blaster PCI512
[1102\0004]
; EMU10K2 Audio Chipset (SB Audigy Series)
00411102=CT4820 Audigy
00421102=CT0070 Audigy
00431102=CT0072 Audigy
00511102=SB0090 Audigy Platinum (EX) -> not marked as Platinum
10031102=SB0243 Audigy 2 (OEM'd For Dell??)
Quoted 8 lines
[1102\0007]
; Audigy LS Series
10011102=SB0310 Audigy LS
10021102=SB0312 Audigy LS
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Quoted 3 lines · matthieu castet
I attached a patch that sort the card by id, it will be a lot's easier to find the missing ones...
In cvs, thank you.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Hi,
Quoted 10 lines · James Courtier-Dutton
Quoted 3 lines · matthieu castet
I attached a patch that sort the card by id, it will be a lot's easier to find the missing ones...
In cvs, thank you.
thanks,
I there an easy way to know if the .sblive51 flag is needed ?
Does it is needed only for 3G SB card (SBxxx version or those marked as 5.1) ?
Matthieu
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Quoted 3 lines · matthieu castet
I there an easy way to know if the .sblive51 flag is needed ? Does it is needed only for 3G SB card (SBxxx version or those marked as 5.1) ?
I think it's need for any SBLive! (not Audigy) that has an analog center/LFE output.
Maybe you could extract this information from the kX driver.
Lee
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Quoted 9 lines · Lee Revell
Quoted 2 lines · matthieu castet
I there an easy way to know if the .sblive51 flag is needed ?
Does it is needed only for 3G SB card (SBxxx version or those marked as 5.1) ?I think it's need for any SBLive! (not Audigy) that has an analog center/LFE output.
On my card (CT4670) the 2 possibles analog output are normal (controled by master) and rear (controled by wave surround). So it is not needed ?
thanks
Matthieu
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Quoted 11 lines · Lee Revell
Quoted 2 lines · matthieu castet
I there an easy way to know if the .sblive51 flag is needed ?
Does it is needed only for 3G SB card (SBxxx version or those marked as 5.1) ?I think it's need for any SBLive! (not Audigy) that has an analog center/LFE output.
Maybe you could extract this information from the kX driver.
on opencreative driver they use :
* 5.1: Enable the additional AC97 Slots and unmute extra channels on AC97 codec */
if (codec->codec_read(codec, AC97_EXTENDED_ID) & 0x0080){
printk(KERN_INFO "emu10k1: SBLive! 5.1 card
detected\n");
sblive_writeptr(card, AC97SLOT, 0,
AC97SLOT_CNTR | AC97SLOT_LFE);
codec->codec_write(codec, AC97_SURROUND_MASTER,
0x0);
}It correspond to AC97_EA_SDAC.
I don't know if it is a safe way...
Matthieu
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Quoted 26 lines · matthieu castet
Quoted 7 lines · Lee Revell
Quoted 2 lines · matthieu castet
I there an easy way to know if the .sblive51 flag is needed ?
Does it is needed only for 3G SB card (SBxxx version or those marked as 5.1) ?Quoted 5 lines
I think it's need for any SBLive! (not Audigy) that has an analog center/LFE output.
Maybe you could extract this information from the kX driver.
on opencreative driver they use :
* 5.1: Enable the additional AC97 Slots and unmute extra channels on AC97 codec */
if (codec->codec_read(codec, AC97_EXTENDED_ID) & 0x0080){ printk(KERN_INFO "emu10k1: SBLive! 5.1 card detected\n"); sblive_writeptr(card, AC97SLOT, 0, AC97SLOT_CNTR | AC97SLOT_LFE); codec->codec_write(codec, AC97_SURROUND_MASTER, 0x0); }
Quoted 1 line
It correspond to
AC97_EA_SDAC.
AC97_EI_SDAC
Quoted 5 lines
I don't know if it is a safe way...
Matthieu
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Quoted 11 lines · matthieu castet
Quoted 10 lines · Lee Revell
Quoted 3 lines · matthieu castet
I there an easy way to know if the .sblive51 flag is needed ? Does it is needed only for 3G SB card (SBxxx version or those marked as 5.1) ?
I think it's need for any SBLive! (not Audigy) that has an analog center/LFE output.
Quoted 7 lines
Quoted 2 lines
Maybe you could extract this information from the kX driver.
on opencreative driver they use :
* 5.1: Enable the additional AC97 Slots and unmute extra channels on AC97 codec */
if (codec->codec_read(codec, AC97_EXTENDED_ID) & 0x0080){
Interesting, I'll look into this. I guess you mean the OSS driver?
Lee
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Quoted 8 lines · matthieu castet
Quoted 7 lines · Lee Revell
Quoted 3 lines · matthieu castet
I there an easy way to know if the .sblive51 flag is needed ? Does it is needed only for 3G SB card (SBxxx version or those marked as 5.1) ?
Quoted 6 lines
Quoted 3 lines
I think it's need for any SBLive! (not Audigy) that has an analog center/LFE output.
On my card (CT4670) the 2 possibles analog output are normal (controled by master) and rear (controled by wave surround).
So it is not needed ?
Correct.
Lee
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Quoted 17 lines · Lee Revell
Quoted 15 lines · matthieu castet
Quoted 12 lines · Lee Revell
Quoted 2 lines · matthieu castet
I there an easy way to know if the .sblive51 flag is needed ?
Does it is needed only for 3G SB card (SBxxx version or those marked as 5.1) ?I think it's need for any SBLive! (not Audigy) that has an analog center/LFE output.
Maybe you could extract this information from the kX driver.
Quoted 8 lines
Quoted 4 lines
on opencreative driver they use :
* 5.1: Enable the additional AC97 Slots and unmute extra channels on AC97 codec */
if (codec->codec_read(codec, AC97_EXTENDED_ID) & 0x0080){Interesting, I'll look into this. I guess you mean the OSS driver?
yes http://sourceforge.net/projects/emu10k1/ driver.
Matthieu
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Quoted 28 lines · matthieu castet
Quoted 8 lines · Lee Revell
Quoted 3 lines · matthieu castet
I there an easy way to know if the .sblive51 flag is needed ? Does it is needed only for 3G SB card (SBxxx version or those marked as 5.1) ?
Quoted 5 lines
I think it's need for any SBLive! (not Audigy) that has an analog center/LFE output.
Maybe you could extract this information from the kX driver.
on opencreative driver they use :
* 5.1: Enable the additional AC97 Slots and unmute extra channels on AC97 codec */
if (codec->codec_read(codec, AC97_EXTENDED_ID) & 0x0080){ printk(KERN_INFO "emu10k1: SBLive! 5.1 card detected\n"); sblive_writeptr(card, AC97SLOT, 0, AC97SLOT_CNTR | AC97SLOT_LFE); codec->codec_write(codec, AC97_SURROUND_MASTER, 0x0); }
Quoted 6 lines
It correspond to
AC97_EA_SDAC.
I don't know if it is a safe way...Matthieu
It is not a safe way of detecting it.
The approach I am going to take is mark each entry in the source code as tested and the email address of someone with the card.
Then, over time we will have eventually tested all of them and also have a contact email address if it needs retesting.
James
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Quoted 41 lines · James Courtier-Dutton
Quoted 31 lines · matthieu castet
Quoted 9 lines · Lee Revell
Quoted 3 lines · matthieu castet
I there an easy way to know if the .sblive51 flag is needed ? Does it is needed only for 3G SB card (SBxxx version or those marked as 5.1) ?
Quoted 5 lines
I think it's need for any SBLive! (not Audigy) that has an analog center/LFE output.
Maybe you could extract this information from the kX driver.
on opencreative driver they use :
* 5.1: Enable the additional AC97 Slots and unmute extra channels on AC97 codec */
if (codec->codec_read(codec, AC97_EXTENDED_ID) & 0x0080){ printk(KERN_INFO "emu10k1: SBLive! 5.1 card detected\n"); sblive_writeptr(card, AC97SLOT, 0, AC97SLOT_CNTR | AC97SLOT_LFE); codec->codec_write(codec, AC97_SURROUND_MASTER, 0x0); }Quoted 6 lines
It correspond to
AC97_EA_SDAC.
I don't know if it is a safe way...Matthieu
Quoted 5 lines
It is not a safe way of detecting it.
The approach I am going to take is mark each entry in the source code as tested and the email address of someone with the card.
Then, over time we will have eventually tested all of them and also have a contact email address if it needs retesting.
ok, for CT4670 you could remove the flag and add my email adress.
Matthieu
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Quoted 11 lines · Lee Revell
Quoted 9 lines · matthieu castet
Quoted 7 lines · Lee Revell
Quoted 2 lines · matthieu castet
I there an easy way to know if the .sblive51 flag is needed ?
Does it is needed only for 3G SB card (SBxxx version or those marked as 5.1) ?
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
I think it's need for any SBLive! (not Audigy) that has an analog center/LFE output.
On my card (CT4670) the 2 possibles analog output are normal (controled by master) and rear (controled by wave surround). So it is not needed ?
I attach a patch a remove 5.1 flag for my card
emu10k1_main.c.new renamed from emu10k1_main.c +2 -2
@@ -811,12 +811,12 @@ .emu10k1_chip = 1, .ac97_chip = 1, .sblive51 = 1} , + /* Tested by [email protected] 7st July 2005 */ {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x00201102, .driver = "EMU10K1", .name = "SBLive! Value [CT4670]", .id = "Live", .emu10k1_chip = 1, - .ac97_chip = 1, - .sblive51 = 1} , + .ac97_chip = 1,} , {.vendor = 0x1102, .device = 0x0002, .driver = "EMU10K1", .name = "SB Live [Unknown]", .id = "Live",