From: rbernd@gmail.com (Bernd)
To: linux-arm-kernel@lists.infradead.org
Subject: Your kernel patches for the Marvell Mirabox
Date: Tue, 11 Dec 2012 22:15:06 +0100 [thread overview]
Message-ID: <50C7A25A.2090602@gmail.com> (raw)
In-Reply-To: <20121211161557.6819daa9@skate>
Hi Thomas,
Thanks, that did the trick! Now the kernel boots OK until it can't find
the root filesystem (I know the reason for that).
It appears that there is a bug in
$ make ARCH=arm CROSS_COMPILE=../arm-2012.09/bin/arm-none-eabi- uImage
The command it uses to create the uImage is (got it from
arch/arm/boot/.uImage.cmd):
/bin/sh /home/bernd/mirabox-dev/marvell-boards/scripts/mkuboot.sh -A arm
-O linux -C none -T kernel -a -e -n 'Linux-3.7.0-rc7-00250-g0c0029c'
-d arch/arm/boot/zImage arch/arm/boot/uImage
So no value given for parameters -a and -e.
Best regards,
Bernd
On 2012-12-11 16:15, Thomas Petazzoni wrote:
> Dear Bernd,
>
> On Tue, 11 Dec 2012 01:43:28 +0100, Bernd wrote:
>
>> Data Size: 1885555 Bytes = 1841.36 kB = 1.80 MB
>> Load Address: fffffff2
>> Entry Point: fffffff2
>
> Those Load address and Entry Point are incorrect.
>
> I think this is due to the fact that mach-mvebu is now part of the
> ARCH_MULTIPLATFORM thing and therefore no longer defines its own
> zreladdr-y, but I'm not sure. In any case, what I'm doing here is:
>
> ./scripts/mkuboot.sh -A arm -O linux -T kernel -C none -a 0x00008000 -e
> 0x00008000 -n 'Linux-marvell' -d myzImage-with-dtb-appended myuImage.
>
> Best regards,
>
> Thomas
>
next prev parent reply other threads:[~2012-12-11 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50C4AC68.7090709@gmail.com>
2012-12-10 14:02 ` Your kernel patches for the Marvell Mirabox Jason Cooper
2012-12-10 15:27 ` Thomas Petazzoni
2012-12-10 16:42 ` Jason Cooper
2012-12-11 0:43 ` Bernd
2012-12-11 15:15 ` Thomas Petazzoni
2012-12-11 21:15 ` Bernd [this message]
2012-12-12 8:31 ` Thomas Petazzoni
2012-12-12 20:01 ` Bernd
2012-12-12 20:43 ` Thomas Petazzoni
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=50C7A25A.2090602@gmail.com \
--to=rbernd@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).