[OE-core] [PATCH] siteinfo: Add mechanism to extend siteinfo information from BSP layer

[Khem Raj]

> On Jul 22, 2016, at 8:55 AM, Richard Purdie <richard.purdie at linuxfoundation.org> wrote:
> 
> On Fri, 2016-07-22 at 08:47 -0700, Khem Raj wrote:
>> Whats the motivation here. This looks like a backdoor for bsps. To
>> user it will make inconsistent behaviour. Even now its quite hard to
>> root cause errors due to siteinfo
> 
> Right now if you have some new target, your only option is to either
> patch OE-Core, or copy the class into your new BSP.

May be we can make an exception and accept patches for these changes into release branches
via master ofcourse

> This is
> particularly problematic if you're working on hardware that isn't
> supported by core OE or that is in active development.
> 
> Having hooks to allow you to write a new BSP without having to make
> changes to the core would seem to be a good thing.

This seems to be fair, however, they will surely keep these fragments
and supply their BSP to users. who will now have to chase different
places for finding siteinfo details.

> 
> I'm not expecting users to regularly use this, just those writing more
> exotic BSPs or doing baremetal work for example.
> 
> I can sympathise with the problem as I've run into it several times now
> myself. We can't really demand that every time this happens, people
> send a patch for OE-Core (although if something is commonly used we'd
> obviously then encourage it).

This could also mean that I can override a definition e.g. size of off_t
for arm in my BSP layer and inject it into a MultiBSP setups where others will
get it too ?

> 
> Cheers,
> 
> Richard
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160722/cca6f35c/attachment-0002.sig>