From: James <jamessteward@optusnet.com.au>
To: Richard Genoud <richard.genoud@gmail.com>
Cc: Alessandro Rubini <rubini-list@gnudd.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
michael <trimarchi@gandalf.sssup.it>
Subject: Re: Help needed with MTD on AT91SAM9263-EK please.
Date: Fri, 23 May 2008 17:32:52 +1000 [thread overview]
Message-ID: <1211527972.6203.44.camel@torchwood> (raw)
In-Reply-To: <80b317760805230027n7cbf6ccbpc8289b4b3ad80714@mail.gmail.com>
On Fri, 2008-05-23 at 09:27 +0200, Richard Genoud wrote:
> I agree with Alessandro, don't rely to much on sam-ba for nand writing.
> That's why I asked you to do the test from linux (erase/mount/write/read)
Ok. Thanks. I'll try again on Monday, method as you suggest. Although
this doesn't explain why the tests
(flasherase/nandtest/flasherase/nandwrite/nanddump) failed. I'm not
very sure of the test applications use though.
Regards,
James.
next prev parent reply other threads:[~2008-05-23 7:33 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
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 [this message]
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=1211527972.6203.44.camel@torchwood \
--to=jamessteward@optusnet.com.au \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.genoud@gmail.com \
--cc=rubini-list@gnudd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox