From: Lee Revell <rlrevell@joe-job.com>
To: Stephen Warren <SWarren@nvidia.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Merging alsa-kernel-1.0.7 into kernel 2.6.9
Date: Thu, 18 Nov 2004 23:50:59 -0500 [thread overview]
Message-ID: <1100839859.11044.33.camel@krustophenia.net> (raw)
In-Reply-To: <DBFABB80F7FD3143A911F9E6CFD477B002A7F808@hqemmail02.nvidia.com>
On Thu, 2004-11-18 at 20:41 -0800, Stephen Warren wrote:
> I'm working on a project where we don't use modules for the kernel at
> all - for various reasons such as target environment simplicity - very
> hard-coded boot scripts, no huge sysvinit based interactive 'desktop'
> system etc.
>
> We need ALSA support, and specifically, alsa-driver 1.0.7 release fixes
> some problems for the target hardware we're using.
>
> So, I'm attempting to merge the content of alsa-driver 1.0.7 into the
> kernel source tree, and to build ALSA support as non-modules.
If the range of hardware you need to support is cmall enough it might be
easier to start with the ALSA in your kernel tarball and forward port
any driver fixes you need.
HTH,
Lee
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
next prev parent reply other threads:[~2004-11-19 4:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 4:41 Merging alsa-kernel-1.0.7 into kernel 2.6.9 Stephen Warren
2004-11-19 4:50 ` Lee Revell [this message]
2004-11-19 18:33 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2004-11-19 16:25 Stephen Warren
2004-11-19 18:32 ` Lee Revell
2004-11-19 20:52 Stephen Warren
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=1100839859.11044.33.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=SWarren@nvidia.com \
--cc=alsa-devel@lists.sourceforge.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 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.