From: Markos Chandras <markaki2002@yahoo.gr>
To: gentoo-user@lists.gentoo.org
Cc: "Andrey Vul" <andrey.vul@gmail.com>
Subject: Re: [gentoo-user] alsa in-kernel vs. alsa-lib
Date: Fri, 31 Oct 2008 01:46:19 +0200 [thread overview]
Message-ID: <200810310146.19875.markaki2002@yahoo.gr> (raw)
In-Reply-To: <e38d12ff0810301604u30daf4afte1cac7b48d8bb6c1@mail.gmail.com>
On Friday 31 October 2008 01:04:42 Andrey Vul wrote:
> On Thu, Oct 30, 2008 at 6:42 PM, Pupino <pupinux@gmail.com> wrote:
> > Hi all,
> > i was used to intall alsa-lib and co. and use tools like alsamixer to
> > manage the audio on my gentoo; now i've tryied to switch to the
> > in-kernel way.
> > I've built the relevant part into the kernel, no module, but now i'm
> > stuck. If i try to emerge alsa-utils (wich has alsamixer) it pulls in
> > also alsa-lib, alsa-header, etc...
> > is this the correct behaviour? i tought i'll get rid of those
> > packages(-header, -lib) switching to the in-kernel drivers.
>
> alsa-lib and alsa-headers are unrelated to the kernel modules.
> alsa-lib and alsa-headers are userspace.
> If you ditch alsa-lib and go full kernel:
> Will you have sound? Maybe.
> Will alsa-using apps be able to use it? Absolutely not. They need alsa-lib.
From my experience i would recommend to use alsa-in-kernel + alsa-libs +
alsa-headers + alsa-utils + alsa-tools
This combination works perfect on my 3 gentoo machines
next prev parent reply other threads:[~2008-10-30 23:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 22:42 [gentoo-user] alsa in-kernel vs. alsa-lib Pupino
2008-10-30 23:04 ` Andrey Vul
2008-10-30 23:46 ` Markos Chandras [this message]
2008-10-30 23:52 ` Joshua Murphy
2008-10-31 10:30 ` [gentoo-user] " Nikos Chantziaras
2008-10-31 11:05 ` Pupino
2008-10-31 12:17 ` Patrick Holthaus
2008-10-31 12:46 ` Neil Bothwick
2008-10-31 15:43 ` Pupino
2008-10-31 14:08 ` Iain Buchanan
2008-10-31 14:32 ` Nikos Chantziaras
2008-10-31 2:53 ` [gentoo-user] " Iain Buchanan
2008-10-31 8:41 ` Markos Chandras
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=200810310146.19875.markaki2002@yahoo.gr \
--to=markaki2002@yahoo.gr \
--cc=andrey.vul@gmail.com \
--cc=gentoo-user@lists.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