linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dacin <dacin@hotpop.com>
To: nbensa@yahoo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 sound drivers?
Date: Fri, 18 Jul 2003 00:16:20 +0530	[thread overview]
Message-ID: <3F16EEFC.3000803@hotpop.com> (raw)
In-Reply-To: 200307171308.54518.nbensa@gmx.net

Norberto BENSA wrote:

>Terje Kvernes wrote:
>  
>
>>Norberto BENSA <nbensa@gmx.net> writes:
>>    
>>
>>>Last time I've checked ALSA, it didn't support bass and treble,
>>>that's why I'm using OSS (emu10k1)
>>>      
>>>
>>  I have treble and base support on my emu10k1 via ALSA.
>>    
>>
>
>How could this be true if:
>
>Ian Hastie wrote:
>  
>
>>ALSA's support seems usable, but still doesn't allow you to programme the
>>DSP with your own code.  OSS uses this to enable such things as bass and
>>treble controls, as well as a selection of audio effects with code
>>provided.  Anyone know if ALSA will allow this kind of thing in the future?
>>    
>>
>
>???
>
>Anyone (Terje, Ed) care to say HOW did you enabled treble and bass in emu10k1 
>(ALSA) or you will continuously say "it works for me" without saying anything 
>useful?
>

Ummm read this....
http://www.alsa-project.org/~valentyn/other-formats/Alsa-sound-mini-HOWTO.html
http://alsa.opensrc.org/index.php?page=emu10k1
http://alsa-project.org/alsa-doc/doc-php/template.php3?company=Creative+Labs&card=Soundblaster+Live&chip=EMU10K1&module=emu10k1


Dacodecz
=================================================================================================
3 finger salute for void



  parent reply	other threads:[~2003-07-17 18:43 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16 22:58 2.6 sound drivers? Robert L. Harris
2003-07-16 23:10 ` Rudo Thomas
2003-07-16 23:29   ` Robert L. Harris
2003-07-16 23:46     ` Rudo Thomas
2003-07-16 23:10 ` Mike Fedyk
2003-07-16 23:30   ` Robert L. Harris
2003-07-16 23:39     ` Mike Fedyk
2003-07-16 23:46     ` David Ford
2003-07-17  0:08       ` Robert L. Harris
2003-07-17  1:07         ` Wes Janzen
2003-07-17  1:42         ` James H. Cloos Jr.
2003-07-17  7:26     ` Martin Schlemmer
2003-07-17  8:57       ` Eugene Teo
2003-07-17  9:22         ` Takashi Iwai
2003-07-17 11:19           ` Ookhoi
2003-07-17 11:31             ` Ed Sweetman
2003-07-17 12:10               ` Alan Cox
2003-07-17 13:11                 ` Ookhoi
2003-07-17 11:32             ` Takashi Iwai
2003-07-16 23:37 ` Jeff Garzik
2003-07-16 19:25   ` Max Valdez
2003-07-17  1:05     ` Jeff Garzik
2003-07-17  2:18       ` Norberto BENSA
2003-07-17 13:13         ` Ian Hastie
2003-07-17 13:25           ` Takashi Iwai
2003-07-17 13:19         ` Terje Kvernes
2003-07-17 16:08           ` Norberto BENSA
2003-07-17 11:22             ` Max Valdez
2003-07-17 16:54             ` Takashi Iwai
2003-07-17 18:43               ` Norberto BENSA
2003-07-17 19:44               ` Ian Hastie
2003-07-18  9:45                 ` Takashi Iwai
2003-07-17 18:46             ` dacin [this message]
2003-07-17 19:12               ` MONOLITHIC sound (was Re: 2.6 sound drivers?) Douglas J Hunley
2003-07-17 20:09                 ` dacin
2003-07-16 23:39   ` 2.6 sound drivers? Robert L. Harris
2003-07-16 23:57     ` Matt Reppert

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=3F16EEFC.3000803@hotpop.com \
    --to=dacin@hotpop.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbensa@yahoo.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;
as well as URLs for NNTP newsgroup(s).