From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] 16-bit NAND support
Date: Wed, 03 Nov 2004 01:21:21 +0100 [thread overview]
Message-ID: <20041103002126.3142CC1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 02 Nov 2004 17:41:55 CST." <71555548814716479478431542AA5F8A01B1B39D@dlee2k04.ent.ti.com>
In message <71555548814716479478431542AA5F8A01B1B39D@dlee2k04.ent.ti.com> you wrote:
>
> Is there some bit which worries you? I didn't notice anything in a
> quick look, but perhaps you did.
I'm always worried when somebody claims "this will not hurt at all"
but I see some sharp instruments behind his back. [Read: if he claims
"no impact on any other system", but the first glance shows obvious
changes in the memory footprint]
I cannot say (yet) is the implementation is clean, or if the
additional memory is well spent. But this is a boot loader, and "1k
or 2k at worst" is 1 or 2 percent of the total. This is a bigger
change than I am willing to ignore without understanding what for
this is good, and why it cannot be avoided.
Best regards,
Wolfgang Denk
--
See us @ Embedded/Electronica Munich, Nov 09 - 12, Hall A.6 Booth 513
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The biggest difference between time and space is that you can't reuse
time. - Merrick Furst
next prev parent reply other threads:[~2004-11-03 0:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 23:41 [U-Boot-Users] [PATCH] 16-bit NAND support Woodruff, Richard
2004-11-03 0:21 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-02 23:12 Zhang, Jian
2004-11-02 23:20 ` Wolfgang Denk
2004-11-02 22:22 Zhang, Jian
2004-11-02 23:05 ` Wolfgang Denk
2004-12-13 8:13 ` Pankaj GOYAL
2004-12-13 9:11 ` Wolfgang Denk
2005-04-03 21:37 ` Wolfgang Denk
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=20041103002126.3142CC1430@atlas.denx.de \
--to=wd@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