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 00:20:40 +0100 [thread overview]
Message-ID: <20041102232045.0F23FC1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 02 Nov 2004 17:12:57 CST." <BA2832125C3C994384FCC051CDFC7369B8A351@dlee2k05.ent.ti.com>
In message <BA2832125C3C994384FCC051CDFC7369B8A351@dlee2k05.ent.ti.com> you wrote:
> Yes, it would change the code size as 16-bit nand code is added. But the
> path that an 8-bit chip follows remains the same. I don't expect it
> breaks any existing boards. Can someone run a test on 8-bit chip boards?
Even if you disable the 16 bit NAND code the code size will change as
you added new fields to some structures and tables.
So please do not claim that it does not affect existing boards. It
does!
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
There are some things worth dying for.
-- Kirk, "Errand of Mercy", stardate 3201.7
next prev parent reply other threads:[~2004-11-02 23:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 23:12 [U-Boot-Users] [PATCH] 16-bit NAND support Zhang, Jian
2004-11-02 23:20 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-02 23:41 Woodruff, Richard
2004-11-03 0:21 ` 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=20041102232045.0F23FC1430@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