[oe] [PATCH] base.bbclass: add support for SOC_FAMILY in COMPATIBLE_MACHINES

[Khem Raj]

On Wed, Aug 4, 2010 at 1:24 PM, Maupin, Chase <chase.maupin at ti.com> wrote:
>> -----Original Message-----
>> From: openembedded-devel-bounces at lists.openembedded.org
>> [mailto:openembedded-devel-bounces at lists.openembedded.org] On Behalf Of
>> Khem Raj
>> Sent: Wednesday, August 04, 2010 2:49 PM
>> To: openembedded-devel at 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 at 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

>
> beagleboard
> omap3evm
> nokia900
> dm37x-evm
> archos5
> bug20
>
> and many many more.  These machines are defined by a variety of companies, some from TI, some community, Nokia, Archos, etc.  I don't think it is likely that we will get agreement on the naming between all the groups.  I know that just within TI the naming is driven by marketing names for the devices.
>
>>
>> I don't have a strong
>> > objection to this patch but, conceptually, it seems a bit ugly.
>>
>>
>>
>> >
>> > p.
>> >
>> >
>> >
>> > _______________________________________________
>> > Openembedded-devel mailing list
>> > Openembedded-devel at lists.openembedded.org
>> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>> >
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel at lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>