public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Linux mtd <linux-mtd@lists.infradead.org>,
	Shmulik Ladkani <shmulik.ladkani@gmail.com>
Subject: Re: Userspace write to UBI partitions
Date: Wed, 08 Feb 2012 14:00:34 +0200	[thread overview]
Message-ID: <1328702434.22240.50.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1202080834220.17234@lnxricardw.se.axis.com>

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

On Wed, 2012-02-08 at 08:35 +0100, Ricard Wanderlof wrote:
> On Tue, 7 Feb 2012, Shmulik Ladkani wrote:
> 
> >> I'll try this out. In the meantime, there doesn't seem to be an ioctl for
> >> erasing blocks?
> >>
> > Well, another option would be using Gluebi - (CONFIG_MTD_UBI_GLUEBI).
> > It exposes a "regular" mtd for every existing volume.
> >
> > You'd be able to work using standard mtd interfaces on it (mtdchar
> > ioctls, e.g. MEMERASE, or even the mtdblock abstraction).
> 
> For other reasons, gluebi is not a viable alternative for us. Mainly 
> because it puts an mtd device on _every_ ubi volume, meaning that volumes 
> can't be removed or resized while gluebi is enabled.

I do not recommend to use gluebi in general - it is just a hack, but the
limitation you brought up is fixable if you really need to :-)

-- 
Best Regards,
Artem Bityutskiy

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

  reply	other threads:[~2012-02-08 11:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 15:20 Userspace write to UBI partitions Ricard Wanderlof
2012-02-07 16:29 ` Shmulik Ladkani
2012-02-07 16:36   ` Ricard Wanderlof
2012-02-07 17:09     ` Shmulik Ladkani
2012-02-08  7:35       ` Ricard Wanderlof
2012-02-08 12:00         ` Artem Bityutskiy [this message]
2012-02-08 12:20           ` Ricard Wanderlof
2012-02-08 11:59     ` Artem Bityutskiy
2012-02-08 12:18       ` Ricard Wanderlof
2012-02-08 13:49         ` Atlant Schmidt
2012-02-08 13:58           ` Artem Bityutskiy

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=1328702434.22240.50.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=ricard.wanderlof@axis.com \
    --cc=shmulik.ladkani@gmail.com \
    /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