public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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 19:01:19 -0400	[thread overview]
Message-ID: <200904061901.23152.vapier@gentoo.org> (raw)
In-Reply-To: <20090406194943.667D0832E416@gemini.denx.de>

On Monday 06 April 2009 15:49:43 Wolfgang Denk wrote:
> In message Scott Wood wrote:
> > > 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?
> >
> > The same could be said about u-boot requiring its own image format (ELF
> > and raw binary images can't be passed a device tree or bd_t, AFAICT).
>
> When the U-Boot (or rather PPCBoot at that time) development was
> starte, there was a very important reason for not using ELF: wasting
> a full 64 kB for the standard ELF file header was unthinkable on most
> embedded devices of that time.
>
> Now, on fat systems with ample resource on one side, and on the other
> side with the infrastructure more or less in place to compose a bootm
> command from small,  separate  building  blocks,  it  should  be  not
> difficult to add such a feature, too.
>
> On the other hand, ELF images are missing a few key points  available
> in  U-Boot  images  so  I would not recommend using plain ELF for any
> system where reliability or just ease of use are important (which was
> the other part of the rationale that led to that format).

which are the same reasons processors do not implement support for ELF as a 
booting source ...

lets say i was to design a brand new part today with an on-chip rom that 
supports booting from a variety of sources (UART, SPI/I2C/NAND flashes, 
directly addressable NOR flashes, as a slave device to SPI/I2C, etc...), what 
format would you recommend that could satisfy all of these requirements ?  i'm 
not aware of any which is why the Blackfin processor has its own stripped down 
LDR format.
-mike

  reply	other threads:[~2009-04-06 23:01 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
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 [this message]
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=200904061901.23152.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