All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] UBI: Do not try to autoresize in readonly mode
Date: Fri, 24 Aug 2012 17:48:18 +0200	[thread overview]
Message-ID: <6233716.oXLBM8tzrg@pali> (raw)
In-Reply-To: <1345822171.2848.325.camel@sauron.fi.intel.com>

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

On Friday 24 August 2012 18:29:31 Artem Bityutskiy wrote:
> On Sat, 2012-08-18 at 14:11 +0200, Pali Rohár wrote:
> > I'm sending small patch which skip autoresizing ubi in
> > readonly mode. I think it is really not good idea to try
> > resize in ro mode.
> 
> Hi, I've just pushed a similar patch to linux-ubi.git, is this
> fine with you? I've also CCed -stable.
> 

Hi, patch is OK. I tested it and working for me fine.

> > BTW, is there userspace tool for unpacking data from ubifs
> > image without need to simulate nand device in kernel?
> 
> Unfortunately no.

Ok. I have patch for block2mtd.ko which allows me to mount ubifs 
image in way: losetup --> block2mtd --> ubiattach --> mount 
without nandsim. I needed to patch block2mtd, because ubi code 
needs correct erase size, write size nand subpage shift and full 
image size. So I added params for these properties in block2mtd 
code - and it working. But I do not know if this is correct way, 
but I can send my patch.

-- 
Pali Rohár
pali.rohar@gmail.com

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

  reply	other threads:[~2012-08-24 15:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-18 12:11 [PATCH] UBI: Do not try to autoresize in readonly mode Pali Rohár
2012-08-24 15:29 ` Artem Bityutskiy
2012-08-24 15:48   ` Pali Rohár [this message]
2012-08-24 15:57     ` Artem Bityutskiy
2012-08-24 15:59       ` Pali Rohár
2012-08-24 16:09         ` Artem Bityutskiy
2017-06-02 15:39           ` Pali Rohár

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=6233716.oXLBM8tzrg@pali \
    --to=pali.rohar@gmail.com \
    --cc=dedekind1@gmail.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 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.