All of lore.kernel.org
 help / color / mirror / Atom feed
From: dacin <dacin@hotpop.com>
To: Douglas J Hunley <doug@hunley.homeip.net>, linux-kernel@vger.kernel.org
Subject: Re: MONOLITHIC sound (was Re: 2.6 sound drivers?)
Date: Fri, 18 Jul 2003 01:39:08 +0530	[thread overview]
Message-ID: <3F170264.6030103@hotpop.com> (raw)
In-Reply-To: 200307171513.00158.doug@hunley.homeip.net

Douglas J Hunley wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>dacin shocked and awed us all by speaking:
>  
>
>>Ummm read this....
>>http://www.alsa-project.org/~valentyn/other-formats/Alsa-sound-mini-HOWTO.h
>>tml http://alsa.opensrc.org/index.php?page=emu10k1
>>http://alsa-project.org/alsa-doc/doc-php/template.php3?company=Creative+Lab
>>s&card=Soundblaster+Live&chip=EMU10K1&module=emu10k1
>>    
>>
>
>I too am trying the 2.6 kernel per Linus' desires and also have an SBLive! . 
>However, I absolutely *destest* kernel modules. To my knowledge, ALSA has 
>been exclusively module-oriented. I'm going to assume that in 2.6 you can 
>build ALSA into a monolithic kernel. Is this assumtion valid? If so, will the 
>referenced documents above apply to getting my sound working? Or are there 
>other documents/resources that I need to be reading to get non-modular ALSA 
>working? Thanks.
>- -- 
>
 lspci -v | grep audio
 02:0e.0 Multimedia audio controller: Creative Labs SB Live!   EMU10k1 
 (rev 08)

 Me checked ta alsa in 2.6.0-test1 as modules as well as inbuilt, it 
workz but nt rockz. Sound in mid
 freq is distorted, and yep all ta tone *bass/treble* do work.
 Ummm I don't think u need to read other documents *provided u did went 
thru it thoroughly*.
 
Dacodecz
=================================================================================
Crawling on ta shadow of darknezz.



  reply	other threads:[~2003-07-17 20:04 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
2003-07-17 19:12               ` MONOLITHIC sound (was Re: 2.6 sound drivers?) Douglas J Hunley
2003-07-17 20:09                 ` dacin [this message]
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=3F170264.6030103@hotpop.com \
    --to=dacin@hotpop.com \
    --cc=doug@hunley.homeip.net \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.