From: Ron Madrid <ron_madrid@sbcglobal.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] mpc83xx: New board support SIMPC8313
Date: Fri, 21 Nov 2008 16:44:18 -0800 (PST) [thread overview]
Message-ID: <472077.6475.qm@web83505.mail.sp1.yahoo.com> (raw)
In response to my own email:
> I did not see this when I built before submitting my patch. It seems to build
> fine using ELDK version 4.1. I just tried building with 4.2 and am
> seeing the errors that you described. For some reason, the 4.2 build has
> about 48 extra bytes to it, and is once again putting me over the 4K
> bootstrap limit. I'm going to look into getting the size down, but that's a
> decent number of bytes to try to optimize out.
I've been trying to trim down my nand_spl bootstrap so that it
will be below the 4K limit allowed by the processor. However
this is proving to be very challenging. I have noticed that there
is a little over 100 (decimal) bytes that are being unused at the
beginning of the resulting binary (after the HRCW and version
string). Would it be possible to move some functions in start.S
(mpc83xx) in front of this (see below) part of the code?
. = EXC_OFF_SYS_RESET
.globl _start
This would allow for more board specific nand_spl boot code.
Would something like this be allowed or am I barking up the
wrong tree?
Ron
next reply other threads:[~2008-11-22 0:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 0:44 Ron Madrid [this message]
2008-11-25 0:37 ` [U-Boot] [PATCH v3] mpc83xx: New board support SIMPC8313 Kim Phillips
2008-11-25 17:02 ` Scott Wood
2008-11-25 19:11 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2008-11-20 22:33 Ron Madrid
2008-11-15 1:13 Ron Madrid
2008-11-20 0:15 ` Kim Phillips
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=472077.6475.qm@web83505.mail.sp1.yahoo.com \
--to=ron_madrid@sbcglobal.net \
--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 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.