From: Darren Hart <dvhart@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [PATCH] fri2: Add linux-yocto-tiny bbappend
Date: Wed, 21 Dec 2011 09:45:21 -0800 [thread overview]
Message-ID: <4EF21B31.70104@linux.intel.com> (raw)
In-Reply-To: <1324488919.19860.9.camel@ted>
On 12/21/2011 09:35 AM, Richard Purdie wrote:
> On Wed, 2011-12-21 at 09:05 -0800, Darren Hart wrote:
>>
>> On 12/21/2011 08:59 AM, Richard Purdie wrote:
>>> On Wed, 2011-12-21 at 01:09 -0800, Darren Hart wrote:
>>>> Provide a bbappend for linux-yocto-tiny with support EFI, SATA, and the EG20T.
>>>> This includes EFI framebuffer and USB HID support which normally would be
>>>> omitted from a tiny kernel, but it is our only functional console as the serial
>>>> port is still non-functional.
>>>>
>>>> Signed-off-by: Darren Hart <dvhart@linux.intel.com>
>>>> ---
>>>> .../linux/linux-yocto-tiny/defconfig | 613 ++++++++++++++++++++
>>>> .../linux/linux-yocto-tiny/eg20t.cfg | 40 ++
>>>> .../linux/linux-yocto-tiny/inforce.cfg | 21 +
>>>> .../recipes-kernel/linux/linux-yocto-tiny/sata.cfg | 7 +
>>>> .../linux/linux-yocto-tiny/usbhid.cfg | 9 +
>>>> .../linux/linux-yocto-tiny_3.0.bbappend | 13 +
>>>> 6 files changed, 703 insertions(+), 0 deletions(-)
>>>> create mode 100644 meta-fri2/recipes-kernel/linux/linux-yocto-tiny/defconfig
>>>> create mode 100644 meta-fri2/recipes-kernel/linux/linux-yocto-tiny/eg20t.cfg
>>>> create mode 100644 meta-fri2/recipes-kernel/linux/linux-yocto-tiny/inforce.cfg
>>>> create mode 100644 meta-fri2/recipes-kernel/linux/linux-yocto-tiny/sata.cfg
>>>> create mode 100644 meta-fri2/recipes-kernel/linux/linux-yocto-tiny/usbhid.cfg
>>>> create mode 100644 meta-fri2/recipes-kernel/linux/linux-yocto-tiny_3.0.bbappend
>>>
>>> I'd just note that if merged, this would make meta-fri2 depend on
>>> meta-tiny since we'd throw parsing errors if the .bbappend is present
>>> without the file its appending to.
>>>
>>> We might want to consider this as an example in the tiny layer itself
>>> for that reason.
>>
>> Hrm, good point. My goal was to eliminate meta-tiny altogether. I have
>> never built meta-intel without meta-yocto. Do we feel that dependency a
>> problem?
>
> I suggesting meta-dri2/meta-intel depending on meta-tiny is a problem.
> Where does meta-yocto come into this?
Actually, -ENOPEPSIYET, meta-yocto doesn't come into this as I defined
linux-yocto-tiny_3.0.bb in oe-core. meta-tiny doesn't come into this
either though. The poky-tiny patch series doesn't introduce a new layer.
meta-tiny was an experimental layer that created new images, tasks, and
bbappends to recipes rather than integrating them into poky proper.
I don't think we have any new dependencies here.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-12-21 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 9:09 [PATCH 0/1] Example meta-intel poky-tiny support for fri2 Darren Hart
2011-12-21 9:09 ` [PATCH] fri2: Add linux-yocto-tiny bbappend Darren Hart
2011-12-21 16:59 ` Richard Purdie
2011-12-21 17:05 ` Darren Hart
2011-12-21 17:35 ` Richard Purdie
2011-12-21 17:45 ` Darren Hart [this message]
2011-12-21 14:52 ` [PATCH 0/1] Example meta-intel poky-tiny support for fri2 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=4EF21B31.70104@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=richard.purdie@linuxfoundation.org \
--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.