From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: How to cope with locked flash
Date: Thu, 15 Sep 2005 16:13:33 +0200 [thread overview]
Message-ID: <87ek7qpgfm.wl%kletschke@synertronixx.de> (raw)
How do you people cope with flash devices that power up locked?
I have intel K3 devices which are unlocked by flash_unlocke in the /etc/inittab
while booting the system.
However, if the fs was never mounted before the jffs2 hangs with this
in an endless loop:
jffs2_write_dirent in garbage_collect_dirent failed: -30
Write of 43 bytes at 0x00363928 failed. returned -30, retlen 0
Not marking the space at 0x00363928 as dirty because the flash driver returned retlen zero
Is there any help to avoid this situation?
Konsti
PS.: sorry, I missed the subject in my mail before so it looks like
spam :( I am still trying to get used to my new MUA :-/
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
next reply other threads:[~2005-09-15 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 14:13 Konstantin Kletschke [this message]
2005-09-15 16:38 ` How to cope with locked flash Todd Poynor
2005-09-15 18:08 ` Jörn Engel
2005-09-16 1:37 ` Todd Poynor
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=87ek7qpgfm.wl%kletschke@synertronixx.de \
--to=lists@ku-gbr.de \
--cc=linux-mtd@lists.infradead.org \
/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