All of lore.kernel.org
 help / color / mirror / Atom feed
From: James <jamessteward@optusnet.com.au>
To: michael <trimarchi@gandalf.sssup.it>
Cc: Richard Genoud <richard.genoud@gmail.com>,
	linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Help needed with MTD on AT91SAM9263-EK please.
Date: Fri, 23 May 2008 17:02:22 +1000	[thread overview]
Message-ID: <1211526142.6203.24.camel@torchwood> (raw)
In-Reply-To: <483668B6.3080507@gandalf.sssup.it>

Hi Michael,

On Fri, 2008-05-23 at 08:48 +0200, michael wrote:
> How do you create the jffs2 image. Which parameters use with the
> mtd-utils?

I was using the one supplied from
ftp://www.linux4sam.org/pub/oe/deploy/glibc/images/at91sam9263ek/Angstrom-x11-image-demo-glibc.rootfs.jffs2

I built the Angstrom minimal system and tried the resulting jffs2 file
system from that too.  Same problem.

I did try mkfs.jffs2 on the root file system produced in the Angstrom
minimal system build, but the result was the same.  I don't recall the
precise command line args I used now.

> Did you try to start from a ramdisk, erase all, and mount it?

At the moment I've got a USB stick as root, with an ext3 fs on it, and
noatime/nodiratime options.  At one stage I did erase the whole thing
and mount -tjffs2 /dev/mtdblock0 /mnt, writing and reading files died
there soon too.

> I'm using an at91san9260 board without any problems.

What kernel, patches and tool chain are you using?

Regards,
James.

  reply	other threads:[~2008-05-23  7:02 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
2008-05-23  6:48     ` michael
2008-05-23  7:02       ` James [this message]
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=1211526142.6203.24.camel@torchwood \
    --to=jamessteward@optusnet.com.au \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.genoud@gmail.com \
    --cc=trimarchi@gandalf.sssup.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.