public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 08/12] 83xx, kmeter: QE_ENET10 errata for Silicon Revision 2.1
Date: Tue, 17 Feb 2009 09:54:51 +0100	[thread overview]
Message-ID: <499A7B5B.4030709@denx.de> (raw)
In-Reply-To: <499A621C.5080503@denx.de>

Hello Kim,

Heiko Schocher wrote:
> Kim Phillips wrote:
>> On Wed, 11 Feb 2009 19:26:22 +0100
>> Heiko Schocher <hs@denx.de> wrote:
>>
>>> +	switch (svid) {
>>> +		case 0x0020:
>> 'case' should be aligned directly under 'switch'.
>>
>>> +++ b/cpu/mpc83xx/start.S
>>> @@ -137,6 +137,11 @@ get_pvr:
>>>  	mfspr	r3, PVR
>>>  	blr
>>>
>>> +	.globl get_svr
>>> +get_svr:
>>> +	mfspr	r3, SVR
>>> +	blr
>>> +
>> on a ./MAKEALL SIMPC8313_LP, I'm getting:
>>
>> powerpc-linux-gnu-ld: NAND bootstrap too big
>> powerpc-linux-gnu-ld: NAND bootstrap too big
>> make[1]: *** [/home/r1aaha/git/u-boot/nand_spl/u-boot-spl] Error 1
>> make: *** [nand_spl] Error 2
>> make: *** Waiting for unfinished jobs....
>> powerpc-linux-gnu-size: './u-boot': No such file
> 
> Hmm.. with actual u-boot I get for this board (without my patches):
> 
> [hs at pollux u-boot]$ ./MAKEALL SIMPC8313_LP
> ...Large Page NAND...Configuring for SIMPC8313 board...
> In file included from /home/hs/U-Boot-Patches/u-boot/include/config.h:5,
>                  from include/common.h:35:
> /home/hs/U-Boot-Patches/u-boot/include/configs/SIMPC8313.h:81:1: warning: "CONFIG_MAX_MEM_MAPPED" redefined
> In file included from /home/hs/U-Boot-Patches/u-boot/include/config.h:4,
>                  from include/common.h:35:
> /home/hs/U-Boot-Patches/u-boot/include/asm/config.h:28:1: warning: this is the location of the previous definition
> In file included from /home/hs/U-Boot-Patches/u-boot/include/config.h:5,
>                  from start.S:30:
> [...]

I was to fast, i get the error (I just have to wait for the end of
the above warnings):

[hs at pollux u-boot]$ ./MAKEALL SIMPC8313_LP
...Large Page NAND...Configuring for SIMPC8313 board...
In file included from /home/hs/U-Boot-Patches/u-boot/include/config.h:5,
                 from include/common.h:35:
[..]
/home/hs/U-Boot-Patches/u-boot/include/asm/config.h:28:1: warning: this is the location of the previous definition
ppc_82xx-ld: NAND bootstrap too big
ppc_82xx-ld: NAND bootstrap too big
make[1]: *** [/home/hs/U-Boot-Patches/u-boot/nand_spl/u-boot-spl] Fehler 1
make: *** [nand_spl] Fehler 2
make: *** Warte auf noch nicht beendete Prozesse...
ppc_82xx-size: './u-boot': No such file
[hs at pollux u-boot]$

I get this error just with actual u-boot.

bye
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2009-02-17  8:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11 18:26 [U-Boot] [PATCH 08/12] 83xx, kmeter: QE_ENET10 errata for Silicon Revision 2.1 Heiko Schocher
2009-02-17  1:37 ` Kim Phillips
2009-02-17  7:07   ` Heiko Schocher
2009-02-17  8:54     ` Heiko Schocher [this message]
2009-02-18  1:25       ` Kim Phillips
2009-02-18  2:29         ` Kumar Gala
2009-02-18  3:30           ` Kumar Gala
2009-02-18 17:20         ` Scott Wood
2009-02-18 18:25           ` Kim Phillips
2009-02-17 17:51   ` Scott Wood

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=499A7B5B.4030709@denx.de \
    --to=hs@denx.de \
    --cc=u-boot@lists.denx.de \
    /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