Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Contents of the "origin/ulf/linux-2.6.30.2" branch. Help with testing wanted.
Date: Wed, 12 Aug 2009 15:32:50 +0200	[thread overview]
Message-ID: <4A82C482.6060008@atmel.com> (raw)
In-Reply-To: <200908121433.31479.marcin@juszkiewicz.com.pl>

Marcin Juszkiewicz skrev:
> Dnia wtorek, 11 sierpnia 2009 o 20:55:00 Ulf Samuelsson napisał(a):
>> The goal of this branch is to update the AT91 support.
>>
>> 1) Fix AT91bootstrap, which is currently non-functional
>> 2) Update to the latest u-boot (2009.08-rc2)
>> 3) Update the kernel (2.6.30.2)
>>    with many AT91 patches not yet in mainstream kernel.
>>    MCI patches still lacking...
> 
> Cool! I will check your changes and then rebase and merge them into .dev 
> tree. I am also planning to push it later to stable/2009 branch.
> 
>> I have so far managed to build everything and load
>> on an AT91SAM9263EK which has a dataflash
>> containing at91bootstrap, u-boot and linux.
>>
>> 0x0     at91bootstrap
>> 0x8400  u-boot
>> 0x84000 linux
>>
>> The NAND flash is programmed with a root file system
>>
>> 0x400000 JFFS2 root file system.
> 
> Similar setup is used on at91sam9263-ek here so I will test your branch.
> 
>> AT91BOOTSTRAP
>> v2.10 was completely wrong due to bad linkaddr.
>> v2.12 and v2.13 boots properly from dataflash.
> 
> Can we just drop all older versions?

The guys responsible for afeb9260 might want to test.

> 
> I had to add patch to 2.12 to get rid of -fno-dwarf2-cfi-asm parametr 
> passed to GCC. Did not tested with 2.13-rc1 as at91.com is not 
> reachable.

Yes, fixed in 2.13-rc1
Will send you the source file.

> 
>> All boards compile, but only the SAM9263EK has been tested on H/W.
>> Only dataflashcard boot that is...
>> Boot from NAND flash not tested.
> 
> Thats what I will not test either - my board has Rev A cpu so only dfc 
> booting possible.
> 
>> The updated at91bootstrap changes the recipe
>> so that the normal way to configure is to do
>>
>> oe_runmake <board>_defconfig
>>
>> instead of copying a defconfig file to the toplevel .config
> 
> Thats good - especially as at91bootstrap configs in OE are basically the 
> same which are in sources.
> 
>> U-BOOT
>> Updated to 2009.08-rc2 with patches.
> 
> [..]
> 
>> The last time I bitbaked this, U-Boot did not build
>> for some reason.
>> When I bitbaked u-boot directly, it built.
>> Will rebuild again and see if problem repeats.
> 
> Will check it.

Someone found the same problem.

> 
>> LINUX
>> A kernel is generated, with the defconfig taken
>> from Marcin's 2.6.30, slightly updated.
>>
>> Added a lot of patches from the ARM mailing list,
>> but the MCI is missing.
>> Hope to get that later.
> 
> I will merge it with linux_2.6.30.bb recipe. Will add also latest 
> 2.6.30.x patch to this.
> 
> For future: do not use linux-2.6.30.2.tar.bz2 but linux-2.6.30.bz2 + 
> patch-2.6.30.2.bz2 - this will save download time for those who have 
> linux-2.6.30.tar.bz2 tarball already.

OK.

>> linux boots and you can communicate with the console,
>> but gpe is not started properly.
> 
> Interesting problem, will check but later as now I have other type of 
> image as default.
> 
>> I introduced the possibility to build linux using
>> make <board>_defconfig, instead of using a
>> defconfig in a board directory under linux.
>> LINUX26_DEFCONFIG needs to be defined.
> 
> Interesting, will check. I see a problem anyway because linux_*.bb 
> recipes by default use defconfig as part of SRC_URI. But we can use 
> empty file to satisfy it.

The fix will test if $(LINUX_DEFCONFIG) is defined,
and if so, it will copy $(LINUX_DEFCONFIG)
to defconfig to avoid problems with recipes

Had a bug, but I got it running today.
Will push soon.


> 
>> BOARD SUPPORT
>> Since there are plenty of AT91 chips with more coming,
>> I decided to make two include files.
>> conf/machine/include/AT91.inc
>> conf/machine/include/AT91-LCD.inc
> 
> Thanks a lot - I had that in todolist ;)
> 
>> I will spend some time testing this, but
>> I hope I will get some help from interested parties.
> 
> As always you can count on me when it comes to AT91 stuff.
> 
> Regards, 


-- 
Best Regards
Ulf Samuelsson




  reply	other threads:[~2009-08-12 13:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 18:55 Contents of the "origin/ulf/linux-2.6.30.2" branch. Help with testing wanted Ulf Samuelsson
2009-08-12 12:33 ` Marcin Juszkiewicz
2009-08-12 13:32   ` Ulf Samuelsson [this message]
2009-08-21 11:53     ` Marcin Juszkiewicz
2009-08-22  7:41       ` Ulf Samuelsson
2009-08-23 10:55         ` Marcin Juszkiewicz
2009-08-22 17:45       ` Ulf Samuelsson
2009-08-23 10:41         ` Marcin Juszkiewicz
2009-08-23 11:31           ` Ulf Samuelsson
2009-08-12 15:13   ` Koen Kooi
2009-08-12 15:56   ` Phil Blundell
2009-08-12 22:09     ` Ulf Samuelsson
2009-08-13  7:12       ` Koen Kooi
2009-08-13  7:10     ` Ulf Samuelsson
2009-08-13 17:34       ` Contents of the "origin/ulf/linux-2.6.30.2" branch. Status update 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=4A82C482.6060008@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox