From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org,
Richard Cagley <rcagley@gmail.com>
Subject: Re: how to create a new layer
Date: Fri, 23 May 2014 11:37:06 -0400 [thread overview]
Message-ID: <537F6B22.8070804@balister.org> (raw)
In-Reply-To: <1521334.KE7mPuYoZb@peggleto-mobl5.ger.corp.intel.com>
On 05/23/2014 03:11 AM, Paul Eggleton wrote:
> On Thursday 22 May 2014 15:46:01 Richard Cagley wrote:
>>> One other thing to note - if there are overrides for the previous machine
>>> (e.g. in bbappends you may see _zedboard-zynq7) you should change
>>> these to _me so that they still apply.
>>
>> What is the threshold for making a new machine? That is, if I just
>> have a .bbappend file I want, that should just involve creating a new
>> layer and putting the bbappend file in the correct location. I
>> shouldn't have to change anything else correct?
>>
>> For instance, if I just want to change the kernel configuration with a
>> frag file I can put linux-xlnx_3.8.bbappedn in
>> meta-me/recipes-kernel/linux and that's all I need?
>
> Yes, that should be all that is required - no need for your own machine
> configuration in this case.
>
>> I guess I'm just confused at what point I actually need a new machine.
>
> If you want to change the global configuration for the machine substantially
> from that in the original BSP, you may need to create your own machine
> configuration; but for the exact same hardware as the original BSP supports I
> would have thought that in most cases it would not be necessary.
Basically, I make a machine whenever I will have hardware specific
drivers, kernel configs, and device trees.
Philip
>
> Cheers,
> Paul
>
prev parent reply other threads:[~2014-05-23 15:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 18:26 how to create a new layer Richard Cagley
2014-05-21 19:26 ` Robert Calhoun
2014-05-21 20:05 ` Richard Cagley
2014-05-21 20:31 ` Philip Balister
2014-05-21 20:58 ` Richard Cagley
2014-05-22 7:10 ` Paul Eggleton
2014-05-22 22:46 ` Richard Cagley
2014-05-23 7:11 ` Paul Eggleton
2014-05-23 15:25 ` Richard Cagley
2014-05-23 15:37 ` Philip Balister [this message]
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=537F6B22.8070804@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=rcagley@gmail.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 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.