From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] bin_dep.sh Support
Date: Mon, 6 Apr 2009 05:03:17 -0400 [thread overview]
Message-ID: <200904060503.18864.vapier@gentoo.org> (raw)
In-Reply-To: <20090406082439.BFF42832E416@gemini.denx.de>
On Monday 06 April 2009 04:24:39 Wolfgang Denk wrote:
> In message Ronen Shitrit wrote:
> > I'm not sure we are on the same page here, the Kirkwood has an
> > internal bootROM which can only boot an image if this image is
> > wrapped by a specific header.
>
> What a stupid (read: broken) hardware design.
>
> There are tons of standards for image formats, and even more commonly
> used formats I would not dare to call standard; but this processor
> has to invent yet another one?
true there are plenty of formats out there, but there arent really ones geared
towards booting a processor. the ELF format is way too bloated/complex (and
yet still not flexible enough) to be usable, and that's about the closest
applicable format i'm familiar with. beyond the simple "processor will start
execution at address XXXX", there isnt any standardization here.
the Blackfin processor too has a custom format (LDR) for booting code. it's
akin to the PHDRs in ELF, plus some additional flag bits to control behavior.
but in our world, i wrote external utilities to manage ELF->LDR conversion and
so i didnt need a dedicated script in u-boot to do that ugly conversion mojo,
just a new Makefile target (u-boot.ldr).
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090406/0819dade/attachment.pgp
next prev parent reply other threads:[~2009-04-06 9:03 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 11:49 [U-Boot] [PATCH] debug_print macros support Prafulla Wadaskar
2009-04-03 11:49 ` [U-Boot] [PATCH] bin_dep.sh Support Prafulla Wadaskar
2009-04-03 11:49 ` [U-Boot] [PATCH] Macronix MX25xx MTD SPI flash driver Prafulla Wadaskar
2009-04-03 14:14 ` Mike Frysinger
2009-04-06 7:23 ` Prafulla Wadaskar
2009-04-06 7:39 ` Mike Frysinger
2009-04-06 8:27 ` Prafulla Wadaskar
2009-04-06 8:49 ` Mike Frysinger
2009-04-03 17:54 ` [U-Boot] [PATCH] bin_dep.sh Support Wolfgang Denk
2009-04-06 7:34 ` Prafulla Wadaskar
2009-04-06 8:05 ` Wolfgang Denk
2009-04-06 8:13 ` Ronen Shitrit
2009-04-06 8:24 ` Wolfgang Denk
2009-04-06 8:36 ` Ronen Shitrit
2009-04-06 9:11 ` Wolfgang Denk
2009-04-06 9:03 ` Mike Frysinger [this message]
2009-04-06 9:16 ` Wolfgang Denk
2009-04-06 9:33 ` Mike Frysinger
2009-04-06 10:28 ` Wolfgang Denk
2009-04-06 10:49 ` Mike Frysinger
2009-04-06 9:38 ` Prafulla Wadaskar
2009-04-06 10:16 ` Mike Frysinger
2009-04-06 11:00 ` Wolfgang Denk
2009-05-26 9:08 ` Stefan Roese
2009-04-06 19:30 ` Scott Wood
2009-04-06 19:49 ` Wolfgang Denk
2009-04-06 23:01 ` Mike Frysinger
2009-04-06 9:39 ` Detlev Zundel
2009-04-06 9:43 ` Prafulla Wadaskar
2009-04-03 17:53 ` [U-Boot] [PATCH] debug_print macros support Wolfgang Denk
2009-04-06 5:32 ` Prafulla Wadaskar
2009-04-06 6:31 ` Mike Frysinger
2009-04-06 6:43 ` Prafulla Wadaskar
2009-04-06 7:56 ` Wolfgang Denk
2009-04-06 8:05 ` Mike Frysinger
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=200904060503.18864.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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