From: Thomas Gleixner <tglx@linutronix.de>
To: Gavin Lambert <gavinl@compacsort.com>
Cc: linux-mtd@lists.infradead.org
Subject: RE: Why is PEB not erased before writing???
Date: Tue, 20 Feb 2007 23:29:21 +0100 [thread overview]
Message-ID: <1172010561.25076.11.camel@localhost.localdomain> (raw)
In-Reply-To: <037a01c75538$eb2a3590$0502a8c0@gavinlpc>
On Wed, 2007-02-21 at 10:48 +1300, Gavin Lambert wrote:
> Quoth Thomas Gleixner [tglx@linutronix.de]:
> > On Tue, 2007-02-20 at 16:41 +0530, Brijesh Singh wrote:
> >> Yes I did enable this CONFIG_MTD_UBI_USERSPACE_IO option.We can't
> >> write the device if this flag is not enabled.UBI treats the device as
> >> readonly. This is the usual way to write UBI device,I guess.
> >
> > No. It is not. It is a _DEBUG_ option. UBI has an update mechanism.
> > See documentation.
>
> Perhaps it needs to be named better then :)
1. It is only available, when you enable CONFIG_MTD_UBI_DEBUG
2. From the help text of CONFIG_MTD_UBI_USERSPACE_IO:
"By default, users cannot directly write and erase individual
eraseblocks of dynamic volumes (the update operation must be used
instead). This option enables this capability - this is often useful for
debugging."
Better names are not really preventing PEBKAC scenarios.
tglx
prev parent reply other threads:[~2007-02-20 22:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 6:37 Why is PEB not erased before writing??? Brijesh Singh
2007-02-20 9:34 ` Thomas Gleixner
2007-02-20 9:49 ` brijesh.singh
2007-02-20 10:44 ` Thomas Gleixner
2007-02-20 11:08 ` Brijesh Singh
2007-02-20 11:11 ` Brijesh Singh
2007-02-20 11:17 ` Thomas Gleixner
2007-02-20 21:48 ` Gavin Lambert
2007-02-20 22:29 ` Thomas Gleixner [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=1172010561.25076.11.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=gavinl@compacsort.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