From: Joachim Jaeger <jjaeger@fsforth.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] NAND READ.JFFS2S
Date: Thu, 10 Mar 2005 11:00:02 +0100 [thread overview]
Message-ID: <42301AA2.8040006@fsforth.de> (raw)
Hi list,
I just tried to use the NAND read command with skipping bad blocks (nand
read.jffs2s) on our S3C2410 based module with the original cmd_nand.c
file from 1.1.2, which is identical with the latest one from top of CVS.
It failed. It worked the same way as the nand read.jffs2 command.
The reason herefore is, that the order of recognizing the command in
function do_nand will never recognize the .jffs2s string. Because at
first the .jffs2 string is checked.
Following patch swaps the order of recognition and it works.
Ciao
Joachim
--
*********************************************************
For more information: http://www.fsforth.de
*********************************************************
Joachim Jaeger
FS FORTH-SYSTEME GmbH
Kueferstr. 8, D-79206 Breisach
Phone: +49 (7667) 908-146, FAX +49 (7667) 908-246
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cmd_nand.c.diff
Url: http://lists.denx.de/pipermail/u-boot/attachments/20050310/b75daf45/attachment.txt
reply other threads:[~2005-03-10 10:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42301AA2.8040006@fsforth.de \
--to=jjaeger@fsforth.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