public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ovidiu Ghinet <ovidiu@hortolomei.iasi.rdsnet.ro>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] About alsa-driver
Date: Sat, 21 Jun 2003 15:48:56 +0300 (EEST)	[thread overview]
Message-ID: <Pine.LNX.4.56.0306211548260.22010@hortolomei.iasi.rdsnet.ro> (raw)



Sorry to pop in without preliminary apointment :))

I have a small suggestion about alsa-driver 

You see i have two kernels 2.4.21 and 2.5.72, more to say is that i have 
configured sound for my pci card (cs4281) buid in, NOT as a module this 
maked me think that:

/etc/init.d/alsasound: must be modified to not check for /proc/asound

/etc/init.d/alsasound: must be modified to try to modprobe snd-somethings 
only with 2.4 kernels and only for 2.5 kernels with sound drivers compiled 
as modules (witch is not an optional thing to do even if you do the 
following IMPORTANT change)

/etc/init.d/alsasound: SHOULD BE PART OF THE alsa-utils NOT FROM 
alsa-driver
And i say that because:
	- if we run 2.5 kernels there is no need to install those modules 
that alsa-driber ebuild anyway will not succed in compiling if no 2.4.x 
sources founded in /usr/src/linux... making people scream and shout...
	- /etc/init.d/alsasound needs "alsactl" anyway on boths kernel 
aproches...
	
/etc/modules.d/alsa: remains a problematic issue we can leave it to 
"alsa-driver" in the hope that if the user knows how to compile a 2.5.x 
kernel with alsa drivers as modules, NOT build in, will also know how 
to make a /etc/modules.d/alsa but BETTER to not asume such things 
/etc/modules.d/alsa in my opinion can also be part of "alsa-utils"




	In my virtually reality mind i think that making 
/etc/init.d/alsasound part of "alsa-utils" and /etc/modules.d/alsa part of 
"alsa-driver" can make our life easier (if we want 2.5.x kernel THAT WILL 
BE SOON 2.6 so... HURRY UP MY FRIEND)

					Ovidiu Ghinet 





--
gentoo-dev@gentoo.org mailing list


                 reply	other threads:[~2003-06-21 12:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.LNX.4.56.0306211548260.22010@hortolomei.iasi.rdsnet.ro \
    --to=ovidiu@hortolomei.iasi.rdsnet.ro \
    --cc=gentoo-dev@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox