All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Please explain the logic on the MACHINEOVERRIDES ordering for meta-fsl-ppc:qoriq
Date: Wed, 11 Feb 2015 12:20:35 -0500	[thread overview]
Message-ID: <54DB8F63.5020000@mindchasers.com> (raw)

Hi,

For the past few months, I have patched out the way meta-fsl-ppc qoriq 
constructs MACHINEOVERRIDES because I don't see the logic in it.  It's 
my preference that the overrides I set for my specific machine (e.g., 
p1010rdb, t1040rdb, or custom-machine) are found over the default 
overrides in meta-fsl-ppc (e.g., init-ifupdown/qoriq-ppc/interfaces).

By default, if I set "p1010rdb" as the MACHINE in local.conf I get:

MACHINEOVERRIDES="p1010:p1010rdb:qoriq-ppc:e500v2"

As you know, FILESPATH is in part built by using MACHINEOVERRIDES and 
the path is built working right to left, so a file in an e500v2 override 
is found before one under p1010rdb.

Shouldn't the more specific override be to the right?

I would think we want to produce the following:

MACHINEOVERRIDES="e500v2:qoriq-ppc:p1010:p1010rdb"

If I'm wrong, please help me to understand why.

If there is agreement, then I would like to submit patches to change the 
meta-fsl-ppc conf files.

Thanks

Bob



             reply	other threads:[~2015-02-11 17:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11 17:20 Bob Cochran [this message]
2015-02-13  0:53 ` Please explain the logic on the MACHINEOVERRIDES ordering for meta-fsl-ppc:qoriq 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=54DB8F63.5020000@mindchasers.com \
    --to=yocto@mindchasers.com \
    --cc=meta-freescale@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.