From: Pantelis Antoniou <panto@intracom.gr>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] New NAND code draft
Date: Fri, 30 Apr 2004 15:05:20 +0300 [thread overview]
Message-ID: <40924100.9000800@intracom.gr> (raw)
Hi there
In the attached patch you can see the progress of my work
in the NAND rewrite.
This is not suitable for inclusion yet.
Things that work now:
1. Correct handling of bad blocks.
2. NAND boot works
3. Updated to latest MTD snapshot.
4. Direct to NAND tftp/nfs support.
Things that are probably borked:
1. Multiple chip support (I don't have such hardware available
and the previous code was kinda of unclear.
2. Since there is DOC support in u-boot that utilizes the old
code and definitions I left the linux/mtd/nand.h header in
place, and created a new mtd_nand.h header for the new stuff.
3. JFFS2 support although there is probably b0rken.
4. The read.xxx/write.xxx support is just not there yet.
I would appreciate it if you could take a look and report
back to me.
Regards
Pantelis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nand-new.diff.bz2
Type: application/x-bzip2
Size: 19019 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20040430/2caf7fd7/attachment.bin
next reply other threads:[~2004-04-30 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 12:05 Pantelis Antoniou [this message]
2004-06-06 23:24 ` [U-Boot-Users] New NAND code draft 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=40924100.9000800@intracom.gr \
--to=panto@intracom.gr \
--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