All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Dragan Marinkovic <marinkovic.dragan@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: squashfs on top of ubi
Date: Tue, 04 Nov 2014 10:18:17 -0300	[thread overview]
Message-ID: <5458D219.4010406@free-electrons.com> (raw)
In-Reply-To: <CAKNKmJS-vKgzjfU4A9t188HHrTqKBwW_i2D7rm4Jxw2rFUUYZA@mail.gmail.com>

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

On 11/04/2014 01:12 AM, Dragan Marinkovic wrote:
[..] I was able to back port the changes ​to​ Linux 3.4 and managed
> to get ubiblkvol userlan​d​ tool up and running. So far, so good.
> 

Great! :)

> I have a few questions though​:
> * What is the mechanics of actually adding squashfs image on top of UBI and
> mount it from userland? I have monolithic kernel.
> 

Well, once you have an ubiblock0_0 device it's just like any other block
device. The raw UBI volume and the block device are 1:1 so you can write
an image to the ubi0_0 volume and you'll be able to mount through the
block device:

mount -o,ro /dev/ubiblock0_0 /mnt

I have some notes with a sort of howto here waiting to be published, let
me see if I can get it in shape.

> * The current version of the driver is RO. I found some of your work from
> 2012 which introduces read-write ubiblock driver (
> http://lists.infradead.org/pipermail/linux-mtd/2012-December/045274.html).
> Is this something that could be potentially used? There is also
> http://webcache.googleusercontent.com/search?q=cache:http://patchwork.ozlabs.org/patch/323628/
> which seems to indicate that there are two separate versions of ubi block
> driver. With the exception of th​at​ post, I can't find any other reference to RW ubiblock driver.
> Could you shed some light on this?
> 

You can find the history and evolution of this driver in this cover letter:

http://lists.infradead.org/pipermail/linux-mtd/2014-February/052228.html

As you can see at some point we decided to remove write support.

-- 
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

           reply	other threads:[~2014-11-04 13:20 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAKNKmJS-vKgzjfU4A9t188HHrTqKBwW_i2D7rm4Jxw2rFUUYZA@mail.gmail.com>]

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=5458D219.4010406@free-electrons.com \
    --to=ezequiel.garcia@free-electrons.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marinkovic.dragan@gmail.com \
    --cc=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.