From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Darren Hart <dvhart@linux.intel.com>
Cc: yocto@yoctoproject.org, poky@yoctoproject.org, saul.wold@intel.com
Subject: Re: [PATCH 0/1] linux-yocto: enable audio for qemux86 and qemux86-64
Date: Mon, 28 Feb 2011 20:47:14 +0000 [thread overview]
Message-ID: <1298926034.26736.7859.camel@rex> (raw)
In-Reply-To: <4D6BEF31.1030400@linux.intel.com>
On Mon, 2011-02-28 at 10:53 -0800, Darren Hart wrote:
> On 02/22/2011 06:49 PM, Bruce Ashfield wrote:
> > Richard/Saul,
>
> Hi Bruce, I'm a little late to the party, but was wondering what your
> thoughts are on the whole OSS thing. It seems we should be as consistent
> as possible in our various Yocto Linux kernel images. Do we want to
> support OSS? I recall several years ago that OSS had drivers that Alsa
> did not and was needed for some boards - is that still the case? My
> feeling is, if possible, I'd like to just have alsa in our kernels and
> help reduce the raging redundancy in the audio API space.
I'd wondered about this too. In general I'd suggest Yocto's position is
to push for alsa drivers and see OSS as a legacy thing. As the author of
chunks of ALSA SoC code, I've put that into practise myself too! :)
Cheers,
Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Darren Hart <dvhart@linux.intel.com>
Cc: yocto@yoctoproject.org, poky@yoctoproject.org, saul.wold@intel.com
Subject: Re: [poky] [PATCH 0/1] linux-yocto: enable audio for qemux86 and qemux86-64
Date: Mon, 28 Feb 2011 20:47:14 +0000 [thread overview]
Message-ID: <1298926034.26736.7859.camel@rex> (raw)
In-Reply-To: <4D6BEF31.1030400@linux.intel.com>
On Mon, 2011-02-28 at 10:53 -0800, Darren Hart wrote:
> On 02/22/2011 06:49 PM, Bruce Ashfield wrote:
> > Richard/Saul,
>
> Hi Bruce, I'm a little late to the party, but was wondering what your
> thoughts are on the whole OSS thing. It seems we should be as consistent
> as possible in our various Yocto Linux kernel images. Do we want to
> support OSS? I recall several years ago that OSS had drivers that Alsa
> did not and was needed for some boards - is that still the case? My
> feeling is, if possible, I'd like to just have alsa in our kernels and
> help reduce the raging redundancy in the audio API space.
I'd wondered about this too. In general I'd suggest Yocto's position is
to push for alsa drivers and see OSS as a legacy thing. As the author of
chunks of ALSA SoC code, I've put that into practise myself too! :)
Cheers,
Richard
next prev parent reply other threads:[~2011-02-28 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 2:49 [PATCH 0/1] linux-yocto: enable audio for qemux86 and qemux86-64 Bruce Ashfield
2011-02-23 2:49 ` [PATCH 1/1] linux-yocto: enable audio for selected qemu targets Bruce Ashfield
2011-02-23 16:23 ` Richard Purdie
2011-02-28 18:53 ` [PATCH 0/1] linux-yocto: enable audio for qemux86 and qemux86-64 Darren Hart
2011-02-28 18:53 ` [poky] " Darren Hart
2011-02-28 20:47 ` Richard Purdie [this message]
2011-02-28 20:47 ` Richard Purdie
2011-02-28 20:48 ` Bruce Ashfield
2011-02-28 20:48 ` [poky] " Bruce Ashfield
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=1298926034.26736.7859.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=dvhart@linux.intel.com \
--cc=poky@yoctoproject.org \
--cc=saul.wold@intel.com \
--cc=yocto@yoctoproject.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 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.