Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: matthieu castet <castet.matthieu@free.fr>
To: Lee Revell <rlrevell@joe-job.com>
Cc: James Courtier-Dutton <James@superbug.co.uk>,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: [Alsa-user] sound blaster name
Date: Sun, 03 Jul 2005 21:16:24 +0200	[thread overview]
Message-ID: <42C83988.2000503@free.fr> (raw)
In-Reply-To: <1120417619.7915.3.camel@mindpipe>

Lee Revell wrote:
> On Sun, 2005-07-03 at 20:50 +0200, matthieu castet wrote:
> 
>>Lee Revell wrote:
>>
>>>On Sun, 2005-07-03 at 15:19 +0200, matthieu castet wrote:
>>>
>>>
>>>>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){
> 
> 
> 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

  reply	other threads:[~2005-07-03 19:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42B3E474.7000301@free.fr>
     [not found] ` <42B3ECD5.6030500@superbug.co.uk>
     [not found]   ` <42B3F28B.4030307@free.fr>
     [not found]     ` <42B3F484.5060004@free.fr>
     [not found]       ` <42B3F83C.90305@superbug.co.uk>
     [not found]         ` <42B5A056.4010608@free.fr>
     [not found]           ` <42BC6451.8020303@free.fr>
2005-06-24 21:04             ` [Alsa-user] sound blaster name Lee Revell
2005-07-02 23:09               ` matthieu castet
2005-07-02 23:26                 ` James Courtier-Dutton
2005-07-02 23:47                   ` [Alsa-user] " matthieu castet
2005-07-03 11:11                     ` matthieu castet
2005-07-03 11:59                       ` [Alsa-user] " James Courtier-Dutton
2005-07-03 13:19                         ` matthieu castet
2005-07-03 18:14                           ` Lee Revell
2005-07-03 18:30                             ` matthieu castet
2005-07-03 19:07                               ` Lee Revell
2005-07-07 16:50                                 ` matthieu castet
2005-07-03 18:50                             ` matthieu castet
2005-07-03 18:52                               ` matthieu castet
2005-07-03 19:06                               ` Lee Revell
2005-07-03 19:16                                 ` matthieu castet [this message]
2005-07-03 19:56                               ` James Courtier-Dutton
2005-07-03 20:01                                 ` matthieu castet
2005-07-03 11:19                     ` matthieu castet
2005-07-03  5:08                 ` 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=42C83988.2000503@free.fr \
    --to=castet.matthieu@free.fr \
    --cc=James@superbug.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --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