linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* UBI+UBIFS on Read-Only NAND
@ 2013-12-05 12:53 Thomas Herrmann
  2013-12-06  8:24 ` Richard Genoud
  0 siblings, 1 reply; 3+ messages in thread
From: Thomas Herrmann @ 2013-12-05 12:53 UTC (permalink / raw)
  To: linux-mtd

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: UBI+UBIFS on Read-Only NAND
  2013-12-05 12:53 UBI+UBIFS on Read-Only NAND Thomas Herrmann
@ 2013-12-06  8:24 ` Richard Genoud
  2013-12-06 11:33   ` Matthieu CASTET
  0 siblings, 1 reply; 3+ messages in thread
From: Richard Genoud @ 2013-12-06  8:24 UTC (permalink / raw)
  To: Thomas Herrmann; +Cc: linux-mtd

2013/12/5 Thomas Herrmann <THerrmann@adwin.de>:
> 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...

AFAIK, UBI is not design to be used on a write protected NAND.
As it is basically a wear-leveling / bad block handling layer, it
wouldn't make much sense without a write capability.
The closest use case I can imagine would be to mount the UBIFS volume
RO by default and remount it RW when a gpio button is pushed.
But with a dip switch directly on the NAND WP pin, I don't think
there's an UBI based solution.

Richard.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: UBI+UBIFS on Read-Only NAND
  2013-12-06  8:24 ` Richard Genoud
@ 2013-12-06 11:33   ` Matthieu CASTET
  0 siblings, 0 replies; 3+ messages in thread
From: Matthieu CASTET @ 2013-12-06 11:33 UTC (permalink / raw)
  To: Richard Genoud; +Cc: linux-mtd, Thomas Herrmann

Le Fri, 6 Dec 2013 09:24:40 +0100,
Richard Genoud <richard.genoud@gmail.com> a écrit :

> 2013/12/5 Thomas Herrmann <THerrmann@adwin.de>:
> > 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...
> 
> AFAIK, UBI is not design to be used on a write protected NAND.
> As it is basically a wear-leveling / bad block handling layer, it
> wouldn't make much sense without a write capability.
> The closest use case I can imagine would be to mount the UBIFS volume
> RO by default and remount it RW when a gpio button is pushed.
> But with a dip switch directly on the NAND WP pin, I don't think
> there's an UBI based solution.
> 
When you open a UBI volume you can choose the mode (UBI_READONLY,
UBI_READWRITE, UBI_EXCLUSIVE).
But ubifs always open it in UBI_READWRITE mode (in ubifs_fill_super),
even if we are in ro mode.

If it wasn't the case you can implement a software write protect at ubi
level.


Matthieu

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-12-06 11:33 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-05 12:53 UBI+UBIFS on Read-Only NAND Thomas Herrmann
2013-12-06  8:24 ` Richard Genoud
2013-12-06 11:33   ` Matthieu CASTET

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).