Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: introducing a new architecture/machine; policy ? (and a question)
Date: Wed, 23 Jun 2010 11:24:40 +0200	[thread overview]
Message-ID: <hvsjso$8bh$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTikz8wGLZKz6Z-o4YpC8C62P-whW_znpSKlV8yEx@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 23-06-10 10:53, Frans Meulenbroeks wrote:
> 2010/6/20 Frans Meulenbroeks <fransmeulenbroeks@gmail.com>:
>> 2010/6/20 Koen Kooi <k.kooi@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.

NO! Machines *never* pin versions, that's what distros and to a lesser
extent recipes are for.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMIdLYMkyGM64RGpERAlPnAKCdByYCC57ozSFv9XUpFP+F7oujgwCbBVC3
yqZUWZMlMXNv5b9ZuQwu6sI=
=A9rs
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-06-23  9:29 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-20  9:58 introducing a new architecture/machine; policy ? (and a question) Frans Meulenbroeks
2010-06-20 10:10 ` Frans Meulenbroeks
2010-06-20 12:35 ` Koen Kooi
2010-06-20 15:38   ` Frans Meulenbroeks
2010-06-23  8:53     ` Frans Meulenbroeks
2010-06-23  9:24       ` Koen Kooi [this message]
2010-06-23  9:36         ` Graeme Gregory
2010-06-23  9:54           ` Frans Meulenbroeks
2010-06-23 10:03             ` Graeme Gregory
2010-06-23 10:07               ` Philip Balister
2010-06-23 10:32                 ` Koen Kooi
2010-06-23 11:16                   ` Frans Meulenbroeks
2010-06-23 17:19                     ` Khem Raj
2010-06-23 19:55                       ` Frans Meulenbroeks
2010-06-23 22:20                         ` Khem Raj
2010-06-23 17:15             ` Khem Raj
2010-06-23 17:18               ` Tom Rini
2010-06-23 10:09         ` Frans Meulenbroeks
2010-06-23 10:30           ` Koen Kooi
2010-06-23 17:23           ` Khem Raj
2010-06-23 20:04             ` Frans Meulenbroeks
2010-06-23 21:55               ` Adrian Alonso
2010-06-23 22:16                 ` Khem Raj
2010-06-23 22:26               ` Khem Raj
2010-06-24  9:27               ` Koen Kooi
2010-06-24 11:23                 ` Frans Meulenbroeks
2010-06-24 15:10                   ` Khem Raj
2010-06-20 22:59 ` 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='hvsjso$8bh$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