From: Rod Boyce <buildroot@teamboyce.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] ALSA for build root
Date: Sat, 26 May 2007 15:35:04 +0100 [thread overview]
Message-ID: <46584598.5090504@teamboyce.co.uk> (raw)
In-Reply-To: <KRKghF7Kp6q2.1lf2WpS3@mailout.dof.se>
Ulf Samuelsson wrote:
> ________________ ?rende: [Buildroot] ALSA for build root F?rfattare: Rod Boyce <buildroot@teamboyce.co.uk> Datum: 2007 maj 25:e 14:50
> All,
>
> I have been adding ALSA to the build root package system I am only able
> to test on a x86 platform. Is anybody else interested in ALSA for
> build-root? I have also been adding libogg and libvorbis would it be OK
> if I submitted a combined patch or would you prefer 2 separate patches?
> Is anybody else working on this who would like an advanced copy to test
> out and or compare against?
>
> This would include the following packages:
> alsa-lib-1.0.14rc4
> alsa-utils-1.0.14rc4
> libogg-1.1.3
> libvorbis-1.1.2
>
>
> Regards,
> Rod Boyce
>
>
> I know that some guys are working on moving the
> existing AVR32 ALSA stuff
> to buildroot.
> You might want to include
> the ALSA patches found
> at avr32linux.org
>
> Best Regards
> Ulf Samuelsson
>
>
>
Ulf & All,
My preference would be to submit what I have so others can play and
submit their patches after testing.
I am ready to e-mail my patch now without the AVR32 changes.
Regards,
Rod Boyce
next parent reply other threads:[~2007-05-26 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <KRKghF7Kp6q2.1lf2WpS3@mailout.dof.se>
2007-05-26 14:35 ` Rod Boyce [this message]
2007-05-25 14:49 [Buildroot] ALSA for build root Rod Boyce
2007-05-25 15:13 ` Daniel Laird
2007-05-25 18:56 ` Peter at busybox.net
2007-05-25 19:03 ` Stuart Wood
2007-05-26 14:45 ` Rod Boyce
2007-05-29 7:03 ` Hans-Christian Egtvedt
2007-05-29 20:00 ` Bernhard Fischer
2007-05-29 20:04 ` Bernhard Fischer
2007-05-29 23:01 ` Rod Boyce
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=46584598.5090504@teamboyce.co.uk \
--to=buildroot@teamboyce.co.uk \
--cc=buildroot@busybox.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.