Hi Robert,
El Sun, Feb 22, 2009 at 02:02:12PM -0500 Robert P. J. Day ha dit:
>
> i'm sure i could verify this by RTFS but i've had a long week and
> i'm feeling lazy so ... is it true that i can protect an MTD partition
> from accidental overwriting by defining it in the map file with the
> MAP_WRITEABLE flag?
i suppose you mean MTD_WRITEABLE
> and having done that, the only way to change that partition would be
> to use flash_unlock, write it, then flash_lock it again? as in,
> defining it with MAP_WRITEABLE is *exactly* equivalent to having
> locked it initially. or does that MAP_WRITEABLE mask flag mean
> something different? thanks.
i'd say it's not equivalent. afaik the flag MTD_WRITEABLE marks a
partition as writable at kernel level (eg by marking it as 'ro' on the
kernel command line), while flash_lock/unlock operate on lock bits of
the flash chip. the chip won't let you write the partition if it is
locked at chip level, even if the partition in the kernel has
MTD_WRITEABLE set.
--
Matthias Kaehlcke
Embedded Linux Engineer
Barcelona
The yellow ships hung in the air just like bricks dont do
(The Hitch-Hiker's Guide to the Galaxy)
.''`.
using free software / Debian GNU/Linux | http://debian.org : :' :
`. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4 `-
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
