From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] at91bootstrap.inc: Mark COMPATIBLE_MACHINEs.
Date: Wed, 22 Sep 2010 11:26:23 -0700 [thread overview]
Message-ID: <4C9A4A4F.7060401@mentor.com> (raw)
In-Reply-To: <AANLkTik62awMj=AX3ndn_QbEQDnSDVuqrKKmza7P0haC@mail.gmail.com>
Graham Gower wrote:
> On 22 September 2010 17:31, Marco Cavallini <koansoftware@gmail.com> wrote:
>> Graham Gower ha scritto, Il 22/09/2010 09:36:
>>> On 22 September 2010 16:43, Marcin Juszkiewicz
>>> <marcin@juszkiewicz.com.pl> wrote:
>>>> Dnia środa, 22 września 2010 o 02:41:52 Graham Gower napisał(a):
>>>>
>>>>> --- a/recipes/at91bootstrap/at91bootstrap.inc
>>>>> +++ b/recipes/at91bootstrap/at91bootstrap.inc
>>>>> +COMPATIBLE_MACHINE =
>>>>> "(afeb9260|at91cap9adk|at91sam9g20ek|at91sam9rlek|at91sam9263ek|at91sam926
>>>>> 0ek|at91sam9xeek|at91sam9261ek)"
>>>> mk355 is also atmel at91sam9263 so at91bootstrap is used on it probably.
>>>>
>>> The compatible machines here are those that have a defconfig in the
>>> the files/ directory.
>>>
>> Yes please
>> mh55 is also atmel at91sam9263 so at91bootstrap is used on it too.
>> It also have its defconfig in the recipes/linux/linux-2.6.28/mh355/
>> directory.
>>
>>
>
> Ok, well the defconfigs are duplicated into this recipe dir (probably
> a bad thing). To support mh55, you would have to copy the defconfig in
> and add it to COMPATIBLE_MACHINE.
It sounds like, and trying not to open a different can of worms, but the
at91 stuff should perhaps be using one of those hooks for grouping a set
of machines together?
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-09-22 18:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 0:41 [PATCH] at91bootstrap.inc: Mark COMPATIBLE_MACHINEs Graham Gower
2010-09-22 7:13 ` Marcin Juszkiewicz
2010-09-22 7:36 ` Graham Gower
2010-09-22 8:01 ` Marco Cavallini
2010-09-22 10:36 ` Graham Gower
2010-09-22 18:26 ` Tom Rini [this message]
2010-09-22 18:59 ` Koen Kooi
2010-09-22 19:10 ` Koen Kooi
2010-09-22 21:47 ` Tom Rini
2010-10-16 13:26 ` Ulf Samuelsson
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=4C9A4A4F.7060401@mentor.com \
--to=tom_rini@mentor.com \
--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