Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel T Chen <crimsun@fungus.sh.nu>
To: Klaus Schulz <kls.schlz@googlemail.com>,
	Travis Place <wishie@wishie.net>,
	alsa-devel@alsa-project.org
Subject: Re: Ubuntu - Alsa Installation Script
Date: Thu, 30 Oct 2008 16:12:10 -0400	[thread overview]
Message-ID: <490A151A.3090109@fungus.sh.nu> (raw)
In-Reply-To: <20081030195509.GB13678@sirena.org.uk>

On 10/30/2008 03:55 PM, Mark Brown wrote:

>
> You probably want to look into hooking the kernel parts of ALSA into
> DKMS for this - doing that would be useful for users on all distros, not
> just Ubuntu.  It's a standard for building out of tree modules for
> distro kernels automatically which ought to deal with this for you.
Luke Yelavich and I have briefly discussed using DKMS foralsa-driver in
Ubuntu 9.04, because maintaining it in-tree is problematic given the pace
at which quirks are added (e.g., pci/hda/patch_*.c).  At the developers
summit in Mountain View, CA, in December, we'll be investigating the
feasibility of using DKMS to compile newer drivers as hardware is
hotplugged.  At least one gotcha is present:  how does one determine which
modules are relevant (i.e., predicting the future is, uh, hard)?  Preparing
an integrated HDA codec is straightforward, but what for a USB audio
device?

  reply	other threads:[~2008-10-30 20:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30  8:03 Ubuntu - Alsa Installation Script Klaus Schulz
2008-10-30 16:00 ` Travis Place
2008-10-30 16:25   ` Klaus Schulz
2008-10-30 19:55     ` Mark Brown
2008-10-30 20:12       ` Daniel T Chen [this message]
2008-10-31 11:17         ` Mark Brown

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=490A151A.3090109@fungus.sh.nu \
    --to=crimsun@fungus.sh.nu \
    --cc=alsa-devel@alsa-project.org \
    --cc=kls.schlz@googlemail.com \
    --cc=wishie@wishie.net \
    /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