From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: alsa in-kernel vs. alsa-lib
Date: Fri, 31 Oct 2008 12:46:56 +0000 [thread overview]
Message-ID: <20081031124656.609f79c9@zaphod.digimed.co.uk> (raw)
In-Reply-To: <dad98e440810310405j24f21ad8kcb549ddcb46ba91e@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
On Fri, 31 Oct 2008 12:05:47 +0100, Pupino wrote:
> But i read this after building alsa-lib:
> * Please try in-kernel ALSA drivers instead of the alsa-drivers ebuild.
> * If alsa-drivers works for you where a recent kernel does not, we want
> * to know about this. Our e-mail address is alsa-bugs@gentoo.org
> * However, if you notice no sound output or instability, please try to
> * upgrade your kernel to a newer version first.
>
> and this makes me think i should get rid of those packages as it say
> "instead". Is this wrong? do we still need alsa-lib and co.?
It says "instead of the alsa-drivers ebuild". you use either the
in-kernel drivers or alsa-drivers, whichever you choose, you still need
alsa-lib.
--
Neil Bothwick
Captain, I sense millions of minds focused on my cleavage.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-31 12: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
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 [this message]
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=20081031124656.609f79c9@zaphod.digimed.co.uk \
--to=neil@digimed.co.uk \
--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