From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 1/5] Use common files for AT91SAM9 configuration
Date: Mon, 18 Oct 2010 19:16:38 +0200 [thread overview]
Message-ID: <4CBC80F6.8020600@atmel.com> (raw)
In-Reply-To: <AANLkTim6ROYhLyn1e8=PT+Joby0hiJ7rCVgUD7ifJRYe@mail.gmail.com>
Frans Meulenbroeks skrev:
> 2010/10/18 Koen Kooi <k.kooi@student.utwente.nl>:
> On 18-10-10 15:38, Ulf Samuelsson wrote:
>>>> Marcin Juszkiewicz skrev:
>>>>> Dnia sobota, 16 pazdziernika 2010 o 14:50:02 ulf.samuelsson@atmel.com
>>>>> napisaB(a):
>>>>>
>>>>>> +++ b/conf/machine/include/at91-2.6.30.inc
>>>>>> +++ b/conf/machine/include/at91-2.6.32.inc
>>>>> Do you plan to duplicate that file with each kernel you will produce?
>>>>> Create include/at91-sam9.inc and put it there.
>>>>>
>>>>> Regards,
>>>> This is to allow different kernel versions for different AT91 chips.
>>>> This allows both a "stable" version, and a development kernel
>>>> to be easily handled.
>>>>
>>>> The file defines (amongst other things) the
>>>> * kernel version,
>>>> * u-boot version
>>>> * at91bootstrap version
>>>> so you need one file per version.
> NAK! Machines don't get to decide versions! Please revert that commit
> and come up with a better way, e.g. default_preference in the recipes or
> distro include files.
>
>> Well machines are probably better capable to decide what u-boot and
>> kernel version is best for them.
>> One alternative (which is probably by more yukky) is to create an
>> kernel-at91 recipe and define PREFERRED_PROVIDER_virtual/kernel
>> I don't feel that is a better scenario
>
The advantage of putting the kernel/u-boot/at91bootstrap in the
machine file, is that I can make a copy of a machine file to another
file, change the version of the include file and build.
I dont have to change any files, so nothing existing breaks.
Once everything is tested, I can just replace the old machine file
with the new file and check in.
>> Frans
>
>
>>
>>
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
BR
Ulf Samuelsson
next prev parent reply other threads:[~2010-10-18 17:37 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-16 12:50 [PATCH 1/5] Use common files for AT91SAM9 configuration ulf.samuelsson
2010-10-16 12:50 ` [PATCH 2/5] Add AT91SAM9 linux-2.6.30 from www.linux4sam.org ulf.samuelsson
2010-10-16 12:50 ` [PATCH 3/5] Add u-boot-2009.11 support for AT91SAM9 ulf.samuelsson
2010-10-16 12:50 ` [PATCH 4/5] Add X-Windows support for AT91 LCD controller ulf.samuelsson
2010-10-16 12:50 ` [PATCH 5/5] Add X11 images with more multimedia support (mplayer etc.) ulf.samuelsson
2010-10-18 13:18 ` Marcin Juszkiewicz
2010-10-18 13:46 ` Ulf Samuelsson
2010-10-18 13:20 ` [PATCH 1/5] Use common files for AT91SAM9 configuration Marcin Juszkiewicz
2010-10-18 13:38 ` Ulf Samuelsson
2010-10-18 15:36 ` Koen Kooi
2010-10-18 17:00 ` Frans Meulenbroeks
2010-10-18 17:16 ` Ulf Samuelsson [this message]
2010-10-18 17:10 ` Ulf Samuelsson
2010-10-18 19:05 ` Khem Raj
2010-10-18 23:10 ` Ulf Samuelsson
2010-10-18 23:33 ` Khem Raj
2010-10-20 23:57 ` Ulf Samuelsson
2010-10-21 6:00 ` Khem Raj
2010-10-25 15:38 ` Ulf Samuelsson
2010-10-25 17:56 ` Khem Raj
2010-10-25 19:32 ` Ulf Samuelsson
2010-10-25 19:39 ` Frans Meulenbroeks
2010-10-28 19:04 ` Ulf Samuelsson
2010-10-21 8:11 ` Koen Kooi
2010-10-21 8:43 ` Frans Meulenbroeks
2010-10-21 9:25 ` Koen Kooi
2010-10-21 9:53 ` Frans Meulenbroeks
2010-10-21 22:01 ` Ulf Samuelsson
2010-10-22 6:28 ` Frans Meulenbroeks
2010-10-25 15:35 ` Ulf Samuelsson
2010-10-19 2:30 ` Philip Balister
2010-10-19 7:24 ` Frans Meulenbroeks
2010-10-20 23:44 ` 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=4CBC80F6.8020600@atmel.com \
--to=ulf.samuelsson@atmel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.