From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] NAND driver updates
Date: Tue, 15 Jan 2008 09:49:03 +0100 [thread overview]
Message-ID: <200801150949.04305.sr@denx.de> (raw)
In-Reply-To: <200801051715.04327.sr@denx.de>
Hi All,
On Saturday 05 January 2008, Stefan Roese wrote:
> I just updated the master branch of the NAND custodian repository with the
> patches from William Juul:
>
> http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-nand-flash.git;a=shor
>tlog;h=master
>
> This patchset brings the U-Boot NAND subsystem in sync again with the Linux
> 2.6.22.1 NAND code. Thanks go to William Juul and his colleagues for the
> hard
As it seems the current status of the new NAND subsystem provided by William
Juul and his colleges, has still some problems. As far as I see it right now
here a list (please let me know if I missed something):
- DOC support broken and removed for now
- needs to be ported and tested on HW with DOC
- 'nand read.jffs2/.i' not implemented at all
- 'nand write.jffs2/.i' not implemented correctly
- Doesn't skip bad blocks
- From my quick first look, it doesn't write the OOB correctly
- Extensive testing on other platforms needed
So with all these flaws, it doesn't make sense from my point of view, to pull
these changes into the official U-Boot repository in this merge window. I
think we should delay this merge for 1 or 2 U-Boot versions, until the
problems mentioned above are resolved.
Any thoughts/comments on this?
If we agree on this merge delay, then I suggest that I move this mtd update
into a different branch (it's currently in the master branch :-() of the
u-boot-nand-flash repository and base the master branch on the master branch
of Wolfgang's official repository. This way updates and fixes to the "old"
NAND subsystem can be handled better.
Again, any comments?
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:[~2008-01-15 8:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 15:54 [U-Boot-Users] [PATCH] NAND: Change nand_wait_ready() to not call nand_wait() Stefan Roese
2008-01-05 16:15 ` [U-Boot-Users] NAND driver updates Stefan Roese
2008-01-08 10:05 ` Matthias Fuchs
2008-01-08 22:06 ` ksi at koi8.net
2008-01-13 7:24 ` Dirk Behme
2008-01-13 8:14 ` ksi at koi8.net
2008-01-09 23:03 ` Matthias Fuchs
2008-01-10 5:45 ` Stefan Roese
2008-01-10 17:46 ` Stefan Roese
2008-01-15 8:49 ` Stefan Roese [this message]
2008-01-15 12:34 ` Matthias Fuchs
2008-01-15 12:48 ` Stig A. Olsen
2008-01-15 17:56 ` ksi at koi8.net
2008-01-16 13:45 ` 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=200801150949.04305.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