From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
openembedded-core@lists.openembedded.org, "Hart,
Darren" <darren.hart@intel.com>
Subject: Re: Deployment for machine X will remove its results from machine Y's deploy dir
Date: Thu, 27 Nov 2014 16:21:43 +0000 [thread overview]
Message-ID: <1417105303.15614.16.camel@linuxfoundation.org> (raw)
In-Reply-To: <547740A7.7000005@topic.nl>
On Thu, 2014-11-27 at 16:17 +0100, Mike Looijmans wrote:
> If I understand correctly, having two "MACHINE" share the same
> MACHINE_ARCH (which is the case for several intel boards too), is not
> actually allowed?
>
> Because you get the same kernel/bootloader for different machines then.
> That's what I wanted, and that triggered me finding this issue.
Its a very good question. As things stand today, there is a one to one
mapping between MACHINE_ARCH and MACHINE, the difference being the
removal of invalid characters for the package namespace. That implies
that no, its not allowed.
The intel boards you mention do something a little different, they
inject a new "arch" into the hierarchy and then several machines share
that common "arch".
I suspect the intel boards you mention do suffer from the issue you
mention in a related way and the fix may be to s/MACHINE/PACKAGE_ARCH/
in DEPLOY_DIR_IMAGE as previously mentioned. The difference is I suspect
they deploy for the first machine built and then not for any other.
Nitin/Darren may be interested in checking into that.
> Please realize that the example is just an example. The actual problem
> I'm experiencing is with the kernel and bootloader!
Right, the allarch behaviour is an illustration but not the underlying
problem you need to resolve (although its related).
Cheers,
Richard
next prev parent reply other threads:[~2014-11-27 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 8:35 Deployment for machine X will remove its results from machine Y's deploy dir Mike Looijmans
2014-11-27 12:02 ` Gary Thomas
2014-11-27 13:17 ` Richard Purdie
2014-11-27 14:22 ` Mike Looijmans
2014-11-27 14:41 ` Richard Purdie
2014-11-27 15:17 ` Mike Looijmans
2014-11-27 16:21 ` Richard Purdie [this message]
2014-11-28 7:09 ` Mike Looijmans
2014-11-28 10:18 ` Richard Purdie
2014-11-28 18:48 ` Mike Looijmans
2014-12-03 11:32 ` Mike Looijmans
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=1417105303.15614.16.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=darren.hart@intel.com \
--cc=koen@dominion.thruhere.net \
--cc=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox