[oe] introducing a new architecture/machine; policy ? (and a question)

[Frans Meulenbroeks]

2010/6/20 Frans Meulenbroeks <fransmeulenbroeks at gmail.com>:
> 2010/6/20 Koen Kooi <k.kooi at student.utwente.nl>:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 20-06-10 11:58, Frans Meulenbroeks wrote:
>>> Hi,
>>>
>>> I'm about to complete bringing a new architecture (nios2 with mmu) and
>>> machine (cyclone III FPGA starter kit, and maybe also the Nios2
>>> Embeddeded Evaluation Kit (aka neek)) to oe.
>>> Is there a policy on on the process how to do this.
>>
>> Have a look at the nios2 patches Leon sent last december, they were
>> reviewed on this list, but not committed.
>
> Koen, thanks for reminding me the look at the review comments.
>
> I'm well aware of the work of Leon and Walter (and they are well aware
> of my work).
> Note that what Leon posted was for a non-mmu nios2 core, whereas the
> changes I have is for an mmu core.
>
> Triggered by Koens reminder I revisited the review comments. Actually
> none but one are applicable for me.
> The one that is applicable is the one about pinning versions in
> machine descriptions.
> I have also done that, as there are simply no other versions of
> binutils and gcc that can be used by this hardware.
> Also I don't feel empowered to make changes in distribution specific files.
>
> The only alternative way that I can think of is doing something like:
> DEFAULT_PREFERENCE_nios2 = "1" in the recipes I need.
> No idea if that overrules the distro settings or not, but I can give
> it a try later today.

Well, tried it and apparently a distro pin has priority over a
DEFAULT_PREFERENCE_nios2 in the recipe.
Guess I'll have to do the pinning the the machine description as
described above.

Frans.