public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Chris AtLee <catlee@canada.com>
To: linux-mtd@lists.infradead.org
Subject: Re: A few questions (cramfs as root, flash permissions and JFFS2 on 2.2.18)
Date: 03 May 2002 16:17:42 -0400	[thread overview]
Message-ID: <1020457063.12077.52.camel@geb> (raw)
In-Reply-To: <1020452092.878.45.camel@geb>

[-- Attachment #1: Type: text/plain, Size: 885 bytes --]

> My second question has to do with protection on the flash chip itself. 
> Whenever I try to mount a jffs image I get lots of errors saying that
> Erasing failed horribly.  So I tried the erase and eraseall utilities
> and get the message that I'm trying to erase a Read-Only filesystem.  My
> bootloader allows me to peek and poke memory manually, so I played
> around with locking / unlocking sections of flash and it seems that I
> can lock and unlock blocks of flash just fine, it's just that they
> aren't reported correctly by the Read Configuration command...Is this
> what is meant by "Legacy lock/unlock" in the MTD debug output?  MTD
> detects this at unsupported on my unit.

Ok, I fixed this problem by adding a command to mtd->unlock for the
addresses corresponding to the partition I want to be read/write.  Is
this the correct solution?

Cheers,
Chris

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

      reply	other threads:[~2002-05-03 20:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03 18:54 A few questions (cramfs as root, flash permissions and JFFS2 on 2.2.18) Chris AtLee
2002-05-03 20:17 ` Chris AtLee [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=1020457063.12077.52.camel@geb \
    --to=catlee@canada.com \
    --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