From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: yunguo.wei@windriver.com, Darren Hart <dvhart@linux.intel.com>,
Poky <poky@yoctoproject.org>,
Otavio Salvador <otavio@ossystems.com.br>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [poky] [PATCH 0/4] Updates in support of genericx86*
Date: Thu, 05 Sep 2013 12:06:34 +0100 [thread overview]
Message-ID: <1378379194.32427.33.camel@ted> (raw)
In-Reply-To: <CAJTo0LZb5hTNAjTJvL2ueRWqe1PWPUv3yU-fbobwjcAis-7JCg@mail.gmail.com>
On Thu, 2013-09-05 at 10:47 +0100, Burton, Ross wrote:
> On 5 September 2013 04:35, Darren Hart <dvhart@linux.intel.com> wrote:
> >> > Some of the oe-core changes could be contained in the meta-yocto-bsp layer, but
> >> > as these changes come from meta-intel, they are needed by multiple layers, and I
> >> > felt it might make more sense in oe-core. If people object to the mga or intel
> >> > xserver video drivers, I can respin those for meta-yocto-bsp.
> >>
> >> QEMU does not need them so they should be in meta-yocto-bsp.
> >
> > I'm fine with that if that is the consensus. Does anyone else care to
> > weigh in?
>
> By that logic nearly all the X drivers in oe-core should be in
> meta-yocto-bsp (synaptics, intel, modesetting, omap, omapfb, keyboard,
> mouse), but then we'd be forcing people using anything other than qemu
> to use meta-yocto-bsp (or duplicate the recipes). A more nuanced
> rationale for keeping modesettings/intel/etc is that whilst the driver
> isn't used on QEMU it is in use on a large number of machines so it
> can be centrally maintained in oe-core. I'm not convinced this holds
> for -mga (unless you're reading this from the late 90s) so it should
> be in meta-yocto-bsp.
There is some thinking going on at the moment about merging genericx86
and qemux86 since the two machines are converging and any differences
could be dealt with at runtime. To me, this is a key detail.
I agree that -mga is a push for OE-Core but the other drivers are useful
and I can see a case for moving them towards the core rather than having
several layers needing them.
Cheers,
Richard
next prev parent reply other threads:[~2013-09-05 11:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 0:18 [PATCH 0/4] Updates in support of genericx86* Darren Hart
2013-09-05 0:18 ` [PATCH 1/4] linux-firmware: Update SRCREV, pull in iwlwifi-7260 support Darren Hart
2013-09-05 1:04 ` Otavio Salvador
2013-09-05 3:34 ` Darren Hart
2013-09-05 6:57 ` [poky] " Saul Wold
2013-09-05 8:50 ` Richard Purdie
2013-09-05 14:49 ` Darren Hart
2013-09-05 0:18 ` [PATCH 2/4] xorg-driver-common: Add configure and install appends from meta-intel Darren Hart
2013-09-05 0:54 ` Otavio Salvador
2013-09-05 3:33 ` Darren Hart
2013-09-05 9:53 ` Burton, Ross
2013-09-05 11:37 ` Otavio Salvador
2013-09-05 11:40 ` Burton, Ross
2013-09-05 12:14 ` Richard Purdie
2013-09-05 12:23 ` Phil Blundell
2013-09-05 13:48 ` Burton, Ross
2013-09-05 15:32 ` Richard Purdie
2013-09-05 16:23 ` Burton, Ross
2013-09-05 15:00 ` Darren Hart
2013-09-05 0:18 ` [PATCH 3/4] xf86-video-mga: Pull in Matrox MGA support " Darren Hart
2013-09-05 9:57 ` Burton, Ross
2013-09-05 13:04 ` Tom Zanussi
2013-09-05 14:52 ` Darren Hart
2013-09-05 15:11 ` Burton, Ross
2013-09-05 15:21 ` Burton, Ross
[not found] ` <5229303F.1090209@windriver.com>
2013-09-10 2:37 ` Darren Hart
[not found] ` <522E9996.8000107@windriver.com>
2013-09-10 17:54 ` Darren Hart
2013-09-05 0:18 ` [PATCH 4/4] genericx86: Create a x86-common.inc base for the x86 BSPs Darren Hart
2013-09-05 1:16 ` [PATCH 0/4] Updates in support of genericx86* Otavio Salvador
2013-09-05 3:35 ` Darren Hart
2013-09-05 9:47 ` [poky] " Burton, Ross
2013-09-05 11:06 ` Richard Purdie [this message]
2013-09-05 11:40 ` Otavio Salvador
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=1378379194.32427.33.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=poky@yoctoproject.org \
--cc=ross.burton@intel.com \
--cc=yunguo.wei@windriver.com \
/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