From: Ladislav Michl <ladis@linux-mips.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] New NAND code
Date: Tue, 7 Jun 2005 17:10:31 +0200 [thread overview]
Message-ID: <20050607151031.GA8694@orphique> (raw)
In-Reply-To: <20040801224522.C75C3C109F@atlas.denx.de>
On Mon, Aug 02, 2004 at 12:45:17AM +0200, Wolfgang Denk wrote:
> Did anybody actually test this rewrite extensively? I don't remember
> any feedback?
Wolfgang,
today I downloaded Pantelis' patch from GMANE archive (thanks to Andrew
Dyer for noticing and also excuse by blindness when reading U-Boot
homepage). Patch was forward ported to current U-Boot code base and
extended to support large page devices. I tested it with Samsung
K91G16U0M and K91G08U0M NAND chips.
Unfortunately patch will be extremely hard to merge, because it is
complete rewrite based on recent Linux MTD code. Therefore it is nearly
imposible to sent chain of incremental patches. My prosal is to make
compile time tests for all boards in U-Boot tree which has NAND support
enabled and report results including code size changes. Than I'll send
patch to mailing list (and posibly cc board maintainers) with request
for testing. In case anyone has better idea, let me know.
Best regards,
ladis
next prev parent reply other threads:[~2005-06-07 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 17:25 [U-Boot-Users] New NAND code Stefan Roese
2004-08-01 22:45 ` Wolfgang Denk
2004-08-02 8:17 ` Stefan Roese
2004-08-02 8:27 ` Pantelis Antoniou
2004-08-10 10:13 ` Andy Hawkins
2004-08-02 8:50 ` Wolfgang Denk
2005-06-07 15:10 ` Ladislav Michl [this message]
2005-06-07 20:22 ` Wolfgang Denk
2006-08-10 6:22 ` rahul
-- strict thread matches above, loose matches on Subject: below --
2004-08-03 13:33 Dave Ellis
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=20050607151031.GA8694@orphique \
--to=ladis@linux-mips.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