From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Bad block skipping for command nboot
Date: Tue, 3 Jul 2007 16:55:13 +0200 [thread overview]
Message-ID: <200707031655.13160.sr@denx.de> (raw)
In-Reply-To: <468A60D8.9060704@siemens.com>
Hi Thomas,
On Tuesday 03 July 2007, Thomas Knobloch wrote:
> > And that's why I have to ask: Do we really need this command extension?
> > Why not just use a combination of commands (e.g. "nand read.jffs2
> > ...;bootm ...)?
>
> Using "nand read.jffs2 ...;bootm ..." has one disadvantage compared to the
> new "nboot.jffs2 ...". For the first command sequence u-boot has to read a
> fixed number of bytes from the NAND. You have to make big enough to support
> the largest possible image for your application. If the image is smaller
> u-boot will still have to read this fixed number of bytes.
> For "nboot" resp. "nboot.jffs2" u-boot will read only as much data from
> NAND as necessary. This might give some performance improvement.
Understood.
> BTW: when
> you ask for the need of the command "nboot.jffs2" you probably should
> question the pure "nboot" as well. It can be replaced by "nand read
> ...;bootm ..." as well.
Yep, correct. That's what was asking myself. I never used it so far.
Please resend the patch and I'll commit it to the NAND repository.
Thanks.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2007-07-03 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 10:57 [U-Boot-Users] [PATCH] Bad block skipping for command nboot Thomas Knobloch
2007-07-03 12:27 ` Stefan Roese
2007-07-03 14:44 ` Thomas Knobloch
2007-07-03 14:55 ` Stefan Roese [this message]
2007-07-03 15:32 ` Thomas Knobloch
2007-07-06 12:59 ` Stefan Roese
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=200707031655.13160.sr@denx.de \
--to=sr@denx.de \
--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