linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Norberto BENSA <nbensa@gmx.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 sound drivers?
Date: Thu, 17 Jul 2003 15:43:50 -0300	[thread overview]
Message-ID: <200307171543.53110.nbensa@gmx.net> (raw)
In-Reply-To: <s5hr84pytyi.wl@alsa2.suse.de>

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1058 bytes --]

Takashi Iwai wrote:
> the treble/bass code is implemented statically.
> (so it is also on OSS emu10k1 as default, btw.)
>
> note that there is an additional switch to activate bass/treble.
> as default, this is set off.  turn it on via alsamixer to get
> effects.

Ah, OK. Thank you. I'll take a look.


> > 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?
>
> hey, they told you right :)

Sorry. I didn't meant to be harsh but I haven't seen anything but "ALSA 
supports emu10k1" or "emu10k1 is very well supported under ALSA." I just 
wanted to know how to get tone control under ALSA and no one seems to share 
that information. Or perhaps I miss a couple of e-mails from this list? I 
can't find this one for example:

	Message-Id: <200307170107.03793.nbensa@gmx.net>

Seems like LKML swallowed that one. If that's the case, and I missed someone's 
reply, please forgive me.

Best regards,
Norberto


[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-07-17 18:40 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 [this message]
2003-07-17 19:44               ` Ian Hastie
2003-07-18  9:45                 ` Takashi Iwai
2003-07-17 18:46             ` dacin
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=200307171543.53110.nbensa@gmx.net \
    --to=nbensa@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbensa@yahoo.com \
    --cc=tiwai@suse.de \
    /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).