linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Herrmann <THerrmann@ADwin.de>
To: linux-mtd@lists.infradead.org
Subject: UBI+UBIFS on Read-Only NAND
Date: Thu, 05 Dec 2013 13:53:47 +0100	[thread overview]
Message-ID: <52A0775B.3080005@ADwin.de> (raw)

We had an old JFFS based system that had a dip switch connected to the
write-enable pin of the flash device, and it worked as expected. Users
were able to configure and use the system in r/w mode and then "lock"
the configuration.

I tried the same with our newer hardware, and UBI/UBIFS. I did not use
static volumes, since write support is essential for initial setup.
However, the system will not boot if the flash is write-protected in
hardware, because UBI assumes that it is R/W.

What is the suggested solution for such a setup? I could not find
anything in the FAQ or in the archive, but I may have been searching for
the wrong keywords...

Regards
Thomas Herrmann

             reply	other threads:[~2013-12-05 12:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 12:53 Thomas Herrmann [this message]
2013-12-06  8:24 ` UBI+UBIFS on Read-Only NAND Richard Genoud
2013-12-06 11:33   ` Matthieu CASTET

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=52A0775B.3080005@ADwin.de \
    --to=therrmann@adwin.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;
as well as URLs for NNTP newsgroup(s).