public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: James <jamessteward@optusnet.com.au>
To: Richard Genoud <richard.genoud@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Help needed with MTD on AT91SAM9263-EK please.
Date: Fri, 23 May 2008 16:38:04 +1000	[thread overview]
Message-ID: <1211524684.6203.13.camel@torchwood> (raw)
In-Reply-To: <80b317760805222326j57e6bc11sfe0beef9ab68267b@mail.gmail.com>

Hi Richard,

On Fri, 2008-05-23 at 08:26 +0200, Richard Genoud wrote:
> I didn't have those kind of problems with the sam9263-ek
> have you tried to erase the device, mount it with jffs2 or yaffs2,
> write a file, unmount, mount and read back the file ?

Yup.  I have used the examples from linux4sam.org, which use a jffs2
file system.

The NAND flash was erased and root jffs2 image written using the SAM-BA
utility, then boot the kernel to use this as its rootfs.  It mounts ok
to begin with, then I get heaps of jffs2 warnings and finally a kernel
bug, I think at fs/jffs2/file.c:251 (I don't have the system here at
home.)

What version of kernel, patches and compiler are you using?

I did try briefly with yaffs2, but I don't think the problem is in the
file system, more the underlying access to the NAND flash.  Maybe in the
chip timing, or something.  I haven't yet investigated that properly.

Regards,
James.

  reply	other threads:[~2008-05-23  6:38 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22  6:20 Help needed with MTD on AT91SAM9263-EK please James
2008-05-23  6:26 ` Richard Genoud
2008-05-23  6:38   ` James [this message]
2008-05-23  6:48     ` michael
2008-05-23  7:02       ` James
2008-05-23  7:12         ` michael
2008-05-23  7:13         ` michael
2008-05-23  7:19         ` michael
2008-05-23  7:28           ` James
2008-05-23  6:52     ` Richard Genoud
2008-05-23  7:05       ` James
2008-05-23  7:27         ` Richard Genoud
2008-05-23  7:32           ` James
2008-05-23  7:41           ` michael
2008-05-25 22:50           ` James
2008-05-27  7:42             ` Richard Genoud
2008-05-27 21:46               ` James
2008-05-28  6:24                 ` Richard Genoud
2008-05-28 22:52                   ` James
2008-05-28 22:59                     ` James
2008-05-29  6:41                       ` Richard Genoud
2008-05-29  6:46                         ` James
2008-05-30  2:05                           ` James
2008-05-23  7:03     ` Alessandro Rubini
2008-05-23  7:08       ` James
2008-05-23  7:09       ` James
2008-05-23  7:39         ` Alessandro Rubini
2008-05-23  7:42           ` James

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=1211524684.6203.13.camel@torchwood \
    --to=jamessteward@optusnet.com.au \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.genoud@gmail.com \
    /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