From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] base.bbclass: add support for SOC_FAMILY in COMPATIBLE_MACHINES
Date: Thu, 05 Aug 2010 01:56:19 +0200 [thread overview]
Message-ID: <i3cun3$aoh$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTi=8efwOur=U1Od-fMS7BdHGEBjydwYWona_NgVh@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04-08-10 23:37, Khem Raj wrote:
> On Wed, Aug 4, 2010 at 1:24 PM, Maupin, Chase <chase.maupin@ti.com> wrote:
>>> -----Original Message-----
>>> From: openembedded-devel-bounces@lists.openembedded.org
>>> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
>>> Khem Raj
>>> Sent: Wednesday, August 04, 2010 2:49 PM
>>> To: openembedded-devel@lists.openembedded.org
>>> Subject: Re: [oe] [PATCH] base.bbclass: add support for SOC_FAMILY in
>>> COMPATIBLE_MACHINES
>>>
>>> On Wed, Aug 4, 2010 at 2:54 AM, Phil Blundell <philb@gnu.org> wrote:
>>>> On Tue, 2010-08-03 at 16:47 -0500, Chase Maupin wrote:
>>>>> * Add support for using SOC_FAMILY in the COMPATIBLE_MACHINES
>>>>> setting for a recipe.
>>>>> * This will allow recipes to work for entire families of
>>>>> devices without having to maintain/update the compatible
>>>>> devices as new devices are added into a family
>>>>
>>>> I don't suppose you'd consider refactoring your MACHINE names in order
>>>> to allow a simple regex in COMPATIBLE_MACHINE?
>>>
>>> that would be a good approach too. Has it been
>>> considered.
>>
>> As I mentioned before, we are matching the machine names to the name of the actual device. Unfortunately, not every device that falls into an SOC family has a similar name and cannot all be dictated by us. For example in omap3 SOC_FAMILY there is:
>
> and omap3 family is armv7-a or cortex-a8 based can it have different
> CPUs and be still categorized as omap3
> is there omap3 specific you need which is not covered with armv7-a or cortex-a8
DSP, SGX, IVA, DSS, AESE, ISP, take your pick.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMWf4jMkyGM64RGpERAnM2AKCR2UEEdmgB/WFr0F9UZ55DqffJ0ACgrROX
7OIjSOU9ki67zIi8c1Xx66k=
=nZ7Z
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-08-04 23:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 21:47 [PATCH] base.bbclass: add support for SOC_FAMILY in COMPATIBLE_MACHINES Chase Maupin
2010-08-04 0:19 ` Denys Dmytriyenko
2010-08-04 5:20 ` Khem Raj
2010-08-04 11:17 ` Michael 'Mickey' Lauer
2010-08-04 11:48 ` Phil Blundell
2010-08-04 14:11 ` Maupin, Chase
2010-08-04 16:50 ` Denys Dmytriyenko
2010-08-04 21:50 ` Phil Blundell
2010-08-04 16:13 ` Denys Dmytriyenko
2010-08-04 16:59 ` Graeme Gregory
2010-08-04 17:21 ` Denys Dmytriyenko
2010-08-04 19:41 ` Graeme Gregory
2010-08-04 9:13 ` Koen Kooi
2010-08-04 9:44 ` Frans Meulenbroeks
2010-08-04 19:02 ` Tom Rini
2010-08-04 9:54 ` Phil Blundell
2010-08-04 19:49 ` Khem Raj
2010-08-04 20:24 ` Maupin, Chase
2010-08-04 21:37 ` Khem Raj
2010-08-04 23:56 ` Koen Kooi [this message]
2010-08-05 4:38 ` Khem Raj
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='i3cun3$aoh$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox