public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC/PATCH] jffs2/mtdparts: Fix problem with usage from JFFS2 and MTDPARTS together
Date: Wed, 20 May 2009 12:01:50 +0200	[thread overview]
Message-ID: <200905201201.50810.sr@denx.de> (raw)
In-Reply-To: <20090517135428.0B53D832E416@gemini.denx.de>

Hi Wolfgang,

On Sunday 17 May 2009 15:54:28 Wolfgang Denk wrote:
> My tests are not succesful wither. I tested on TQM8548; when booting
> Linux I see this:
>
> ...
> NAND device: Manufacturer ID: 0x2c, Chip ID: 0xdc (Micron NAND 512MiB
> 3,3V 8-bit)
> Scanning device for bad blocks
> Bad eraseblock 628 at 0x000004e80000
> Bad eraseblock 995 at 0x000007c60000
> Bad eraseblock 2051 at 0x000010060000
> Bad eraseblock 3608 at 0x00001c300000
> Bad eraseblock 3992 at 0x00001f300000

<snip>

> => fsinfo
> ### filesystem type is JFFS2
> Scanning JFFS2 FS:   read_nand_cached: error reading nand off 0xabfe00 size
> 8192 bytes read_nand_cached: error reading nand off 0xadfe00 size 8192
> bytes
> read_nand_cached: error reading nand off 0xac0000 size 8192 bytes
> read_nand_cached: error reading nand off 0xaffe00 size 8192 bytes

<snip>

> The addresses where the read errors occur don't seem to be related to
> the bad blocks reported by Linux.

No. What does a "normal" "nand read" return when reading this complete 
partition into RAM? On PPC4xx it returned -117 here. I fixed it with the 
already posted patches for the 4xx NDFC ECC byte ordering. Perhaps the TQM8548 
has similar incompatibility issues with the Linux kernel here too?

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
=====================================================================

  reply	other threads:[~2009-05-20 10:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-16 10:04 [U-Boot] [RFC/PATCH] jffs2/mtdparts: Fix problem with usage from JFFS2 and MTDPARTS together Stefan Roese
2009-05-17 13:54 ` Wolfgang Denk
2009-05-20 10:01   ` Stefan Roese [this message]
2009-05-24 21:10     ` Wolfgang Denk
2009-05-26 19:48       ` Scott Wood
2009-05-17 14:52 ` Wolfgang Denk
2009-05-17 17:25   ` Wolfgang Denk
2009-05-20  9:54     ` Stefan Roese
2009-05-28 19:27 ` Wolfgang Denk
2009-06-01  8:59   ` Renaud barbier
2009-06-02  3:58     ` 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=200905201201.50810.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