public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Grant Erickson <gerickson@nuovations.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problems with root JFFS2 on NAND Flash
Date: Thu, 26 Jun 2008 10:55:03 -0700	[thread overview]
Message-ID: <C4892607.100BB%gerickson@nuovations.com> (raw)
In-Reply-To: <c13b1cfc0806261027q7bb406b5rbfe1f3d44fc43bc3@mail.gmail.com>

On 6/26/08 10:27 AM, Stuart Wood wrote:
> Tried what you said including patching mkfs.jffs2 and I'm now getting
> these errors
> 
> [ errors omitted ]
>
> This seems to imply that the kernel is looking for the clean markers.
> If they are not needed
> with NAND flash then why would it look for them? I did not see
> anything in the kernel configs
> for JFFS2 that would tell it to use use them.
> 
> As I said before this is kernel 2.6.18, an older version of build root
> using mtd_20050122
> 
> Any other thoughts?

Stuart:

Without knowing more about the specific origin and configuration of your
kernel, version and configuration of u-boot and model, revision and geometry
of NAND, it is difficult to speculate.

I am using:

    AMCC PowerPC 405EXr
    Samsung K9F1208U0B NAND
    U-boot 1.3.3
    Linux 2.6.25-rc3-DENX

Are you certain that u-boot and linux are in agreement about the NAND layout
and format? I had some initial problems in that area until I applied a patch
to u-boot (prior to 1.3.3) that addressed the issue and brought the two into
agreement.

Regards,

Grant

  reply	other threads:[~2008-06-26 17:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13 13:58 [U-Boot-Users] Problems with root JFFS2 on NAND Flash Stuart Wood
2008-06-13 14:45 ` Stuart Wood
2008-06-13 15:54   ` Grant Erickson
2008-06-26 17:27     ` Stuart Wood
2008-06-26 17:55       ` Grant Erickson [this message]
2008-06-26 18:16         ` Stuart Wood
2008-06-26 18:51           ` Kenneth Johansson
2008-06-30 21:02             ` Stuart Wood
2008-06-26 23:17           ` Andrejs Cainikovs

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=C4892607.100BB%gerickson@nuovations.com \
    --to=gerickson@nuovations.com \
    --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