All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Petr Štetiar" <ynezz@true.cz>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] ts72xx, ts73xx, ts74xx? How to handle properly	similar machines
Date: Mon, 18 Oct 2010 13:49:43 +0200	[thread overview]
Message-ID: <20101018114943.GP28423@ibawizard.net> (raw)
In-Reply-To: <i9705t$i6g$1@dough.gmane.org>

Koen Kooi <k.kooi@student.utwente.nl> [2010-10-14 15:22:05]:

> It means you need to use angstrom or set is as override in local.conf

Ok, but would this work for example (it's not real life example)?

local.conf - SOC_FAMILY="ts7400"
machine/ts7xxx.inc - common stuff for all the boards
machine/ts72xx.conf - include ts7xxx.inc and add board specific stuff
machine/ts7250.conf - include ts72xx.conf and add board specific stuff
machine/ts7260.conf - include ts72xx.conf and CF support
machine/ts73xx.conf - include ts7xxx.inc and board specific stuff (FPGA + video)
machine/ts74xx.conf - include ts7xxx.inc and add SD card support

can I than use this as some kind of overrides? Say I'll need to have different
options in some of the packages and I would need to use something like this:

PACKAGE_ARCH += "${SOC_FAMILY}"
SRC_URI_append_ts7xxx += "file://common.patch"
SRC_URI_append_ts7260 += "file://compact-flash.patch"
SRC_URI_append_ts74xx += "file://sd-card.patch"
SRC_URI_append_ts73xx += "file://fpga.patch"

Because as I've seen the usage of the SOC_FAMILY in the recipes I don't think
it would be possible. Thanks for the answer, or more specific example.

-- ynezz



      parent reply	other threads:[~2010-10-18 11:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14 12:45 [RFC] ts72xx, ts73xx, ts74xx? How to handle properly similar machines Petr Štetiar
2010-10-14 13:22 ` Koen Kooi
2010-10-14 13:50   ` Petr Štetiar
2010-10-18 11:49   ` Petr Štetiar [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=20101018114943.GP28423@ibawizard.net \
    --to=ynezz@true.cz \
    --cc=openembedded-devel@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 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.