All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Petr Štetiar" <ynezz@true.cz>
To: openembedded-devel@lists.openembedded.org
Subject: [RFC] ts72xx, ts73xx, ts74xx? How to handle properly similar	machines
Date: Thu, 14 Oct 2010 14:45:48 +0200	[thread overview]
Message-ID: <20101014124548.GJ28423@ibawizard.net> (raw)

Hi,

I've been asked if I could add support for the ts7400 board/machine in the OE.
It's not a big deal, it's just an addition of one patch to the kernel recipe.

While I'll be into it, I was thinking about adding the base for the possible
future addition of ts7300[2] boards also. Althought I own only ts7800 and
ts7250, the ts7200[4], ts7300 and ts7400 families looks like they have a lot
of common and it would be possible to have for example one kernel for all of
them.

The question is, how to handle this correctly in OE? On the IRC, I was pointed
to the SOC_FAMILY[3], but it says "The use of SOC_FAMILY as an override is
currently a distribution or local setting", what does it mean?

Would it be possible to create, say ts7234.inc file with shared stuff for all
the boards, and separate ts7{2,3,4}xx.conf files with the features for each
series, say ts73xx would contain FPGA/video related stuff etc, so the machine
specific overrides would be needed. 

Any thoughts? Thanks.

1. http://www.embeddedarm.com/products/board-detail.php?product=TS-7400
2. http://www.embeddedarm.com/products/arm-sbc.php#ts-7300-fpga-series
3. http://docs.openembedded.org/usermanual/html/commonuse_new_machine.html
4. http://www.embeddedarm.com/products/arm-sbc.php#ts-7200-200mhz-series

-- ynezz



             reply	other threads:[~2010-10-14 12:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14 12:45 Petr Štetiar [this message]
2010-10-14 13:22 ` [RFC] ts72xx, ts73xx, ts74xx? How to handle properly similar machines Koen Kooi
2010-10-14 13:50   ` Petr Štetiar
2010-10-18 11:49   ` Petr Štetiar

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=20101014124548.GJ28423@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.