From: Indrek Kruusa <indrek.kruusa@artecdesign.ee>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: cat file > /dev/mtd0 works but after position 512
Date: Wed, 14 Jun 2006 13:02:44 +0300 [thread overview]
Message-ID: <448FDEC4.8020606@artecdesign.ee> (raw)
In-Reply-To: <1150210422.5257.333.camel@localhost.localdomain>
Thomas Gleixner wrote:
> On Tue, 2006-06-13 at 17:02 +0300, Indrek Kruusa wrote:
>> Hi!
>>
>> I have Samsung 64 MB NAND behind cs553x flash controller - therefore
>> cs553x_nand driver.
>> cat file > /dev/mtd0 works reportedly (with page aligned file). But
>> after board reboots the flash is empty.
>>
>> dd ... bs=512 seek=1 of=/dev/mtd0 works and content stays in flash
>> after reboot too (it works I mean :) )
>>
>> I am debugging my own changes in cs553x_nand driver so it is up to me of
>> course. But can this behavior be explained in other way than nand driver
>> bug? Broken BIOS/board?
>
> http://www.linux-mtd.infradead.org/faq/nand.html
>
> tglx
Thanks for the pointer - there are definitely still things I am not
aware of. Currently it came out though that our BIOS contains support
for NAND media with specific format. And if there isn't needed format in
place - it creates one immediately at boot :)
Without that "feature" it seems to be OK. Annoying thing is that
initializing says 'ECC error while reading bad block table'. I am not
sure at moment how to handle this fact. But it is possible to
flash_eraseall, nandwrite my_jffs2.img, mount and read it.
thanks,
Indrek
prev parent reply other threads:[~2006-06-14 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 14:02 cat file > /dev/mtd0 works but after position 512 Indrek Kruusa
2006-06-13 14:53 ` Thomas Gleixner
2006-06-14 10:02 ` Indrek Kruusa [this message]
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=448FDEC4.8020606@artecdesign.ee \
--to=indrek.kruusa@artecdesign.ee \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.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