From: "Eric Bénard" <eric@eukrea.com>
To: pgsellmann@portner-elektronik.at
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] linux_2.6.38: update support for PcontrolG20 HW rev 2
Date: Mon, 16 May 2011 12:29:32 +0200 [thread overview]
Message-ID: <4DD0FC8C.4040104@eukrea.com> (raw)
In-Reply-To: <201105161155.05490.pgsellmann@portner-elektronik.at>
Hi Peter,
On 16/05/2011 11:55, Peter Gsellmann wrote:
> Am Samstag 14 Mai 2011, 19:06:24 schrieb Eric Bénard:
>> On 29/04/2011 11:45, Peter Gsellmann wrote:
>>> All prototypes hardware rev 1 are drawn back
>>> so default should be rev 2
>>>
>>> Signed-off-by: Peter Gsellmann<pgsellmann@portner-elektronik.at>
>>> ---
>>> recipes/linux/linux-2.6.38/pcontrolg20/defconfig | 1761 ++++++++++++++++++++
>>> .../pcontrolg20/pcontrolg20_2.6.38.patch | 235 +++
>>> recipes/linux/linux_2.6.38.bb | 2 +
>>> 3 files changed, 1998 insertions(+), 0 deletions(-)
>>> create mode 100644 recipes/linux/linux-2.6.38/pcontrolg20/defconfig
>>> create mode 100644 recipes/linux/linux-2.6.38/pcontrolg20/pcontrolg20_2.6.38.patch
>>>
>> I applied this patch and tried to build the kernel but it seems there is no
>> machine definition for pcontrolg20 : can you please resend a patch serie to
>> add the kernel support and the machine conf file.
> the machine configuration for pcontrolg20 is still not in a stable state:
> At least the kernel patch is stable, but for the at91bootstrap i have made changes for lowlevel initialization and memory detection which i have to bring in sync with mainline; right now my at91bootstrap patch looks ugly and would be rejected deservedly.
> Same is for U-boot. I patched a specific git-revision with a number of additional commands i need for factory testing.
> Even worse, the perpetual discussions about kernel relocation/decompression convinced me to evaluate alternatives like barebox.
>
good choice ;-)
> So my ToDo-list is:
> (*) commit kernel.patch
> * commit at91bootstrap.patch
> * commit U-boot or Barebox patches
> * commit conf/machine/pcontrolg20.conf
> * commit recipes/pcontrolg20-image.bb
>
> If its ok for you this would be the first commit.
>
> I could commit the pcontrolg20.conf also, but the entries for at91boosttrap and u-boot would be commented out.
yes a kernel recipe without the machine conf file can't be tested : please
send the 2 patches (kernel + conf file), then you will be able to add entries
for at91bootstrap & u-boot to the conf file later when you add the support for
you board in their respective recipes.
thanks
Eric
next prev parent reply other threads:[~2011-05-16 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 9:45 [PATCH] linux_2.6.38: update support for PcontrolG20 HW rev 2 Peter Gsellmann
2011-05-14 17:06 ` Eric Bénard
2011-05-16 9:55 ` Peter Gsellmann
2011-05-16 10:29 ` Eric Bénard [this message]
2011-05-16 13:47 ` Peter Gsellmann
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=4DD0FC8C.4040104@eukrea.com \
--to=eric@eukrea.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=pgsellmann@portner-elektronik.at \
/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