From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] SPI flash writing
Date: Tue, 13 Mar 2012 22:16:35 -0400 [thread overview]
Message-ID: <201203132216.36783.vapier@gentoo.org> (raw)
In-Reply-To: <D839955AA28B9A42A61B9181506E27C40311BB41@SRVCHBER1212.ch.keymile.net>
On Tuesday 13 March 2012 17:31:02 Falauto, Gerlando wrote:
> From: Mike Frysinger [mailto:vapier at gentoo.org]
> >On Tuesday 13 March 2012 16:17:52 Jason Cooper wrote:
> >> On Tue, Mar 13, 2012 at 04:11:29PM -0400, Mike Frysinger wrote:
> >> > On Tuesday 13 March 2012 14:25:07 Gerlando Falauto wrote:
> >> > > 2) an out-of-boundary-check againts the flash size so at least a
> >> > > warning is issued when you use too big a size value
> >> >
> >> > i'm not sure about this. if you want to do size checking, then enable
> >> > the hush shell and do it in a script.
> >>
> >> Is there a programatic way to get the size of the flash at runtime from
> >> the hush script?
> >
> >no. question is, do you really need that ? sounds like you know ahead of
> >time how big the space is for u-boot, so the size of the flash doesn't
> >matter.
>
> Can't the same command also be used for burning something *other than*
> u-boot (e.g. a kernel, config section, or something like that)? So the
> size of the flash *does matter*, doesn't it?
you have to show how it actually does matter. when you deploy a board and
programming the flash directly, you don't let the regions grow arbitrarily.
you know how big the space for u-boot, or the kernel, or dedicated config
space, or anything else is going to be. if you want to arbitrarily append
things, then you're going to use a filesystem.
-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/20120313/af5199cd/attachment.pgp>
next prev parent reply other threads:[~2012-03-14 2:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 18:25 [U-Boot] SPI flash writing Gerlando Falauto
2012-03-13 20:11 ` Mike Frysinger
2012-03-13 20:17 ` Jason Cooper
2012-03-13 20:35 ` Mike Frysinger
2012-03-13 21:31 ` Falauto, Gerlando
2012-03-14 2:16 ` Mike Frysinger [this message]
2012-03-14 6:44 ` Gerlando Falauto
2012-03-15 0:50 ` Mike Frysinger
2012-03-15 0:02 ` Tom Rini
2012-03-15 0:51 ` Mike Frysinger
2012-03-14 2:18 ` Simon Glass
2012-03-14 6:58 ` Gerlando Falauto
2012-04-03 14:34 ` [U-Boot] [PATCH] cmd_sf: add size checking to spi flash commands Gerlando Falauto
2012-04-03 19:31 ` Mike Frysinger
2012-07-21 17:29 ` [U-Boot] [PATCH v2] " Mike Frysinger
2012-04-03 15:14 ` [U-Boot] [PATCH 0/2] SPI flash update command Gerlando Falauto
2012-04-04 6:40 ` Valentin Longchamp
2012-04-03 15:14 ` [U-Boot] [PATCH 1/2] cmd_sf: let "sf update" erase last sector as a whole Gerlando Falauto
2012-04-04 0:28 ` Simon Glass
2012-04-03 15:14 ` [U-Boot] [PATCH 2/2] cmd_sf: "sf update" preserve the final part of the last sector Gerlando Falauto
2012-04-04 0:33 ` Simon Glass
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=201203132216.36783.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