From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] QE firmware/microcode handling
Date: Thu, 20 Sep 2012 16:28:01 -0500 [thread overview]
Message-ID: <505B8A61.2040903@freescale.com> (raw)
In-Reply-To: <1348165467.8195.3@snotra>
Scott Wood wrote:
> The 512K limit is arbitrary and can be changed. It exists just to
> provide a stable start address on something that grows from the end of
> flash.
True, but we haven't actually done changed it. Instead of allowing for a
larger u-boot.bin, we have ALWAYS disabled features or rewritten code to
make it smaller. If making U-boot larger were so simple, it would have
been done by now, I think.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-09-20 21:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 9:49 [U-Boot] QE firmware/microcode handling Gerlando Falauto
2012-09-20 15:16 ` Wolfgang Denk
2012-09-20 15:22 ` Timur Tabi
2012-09-20 18:24 ` Scott Wood
2012-09-20 21:28 ` Timur Tabi [this message]
2012-09-21 1:55 ` McClintock Matthew-B29882
2012-09-21 8:32 ` [U-Boot] [PATCH] SBx81CFC960: embed Fman microcode in the bootloader judge.packham at gmail.com
2012-09-21 11:32 ` Tabi Timur-B04825
2012-09-21 15:58 ` Wolfgang Denk
2012-09-21 16:30 ` Timur Tabi
2012-09-22 9:44 ` Chris Packham
2012-09-24 14:25 ` Timur Tabi
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=505B8A61.2040903@freescale.com \
--to=timur@freescale.com \
--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