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, 2 Jun 2017 17:39:59 +0200 [thread overview]
Message-ID: <201706021739.59748@pali> (raw)
In-Reply-To: <1345824556.2848.339.camel@sauron.fi.intel.com>
[-- Attachment #1: Type: Text/Plain, Size: 1072 bytes --]
On Friday 24 August 2012 18:09:16 Artem Bityutskiy wrote:
> On Fri, 2012-08-24 at 17:59 +0200, Pali Rohár wrote:
> > > Why do you need to use block2mtd? If you have an image for NOR
> > > flash, use mtdram, if it is for NAND - use nandsim. What
> > > prevents you from using mtdram or nandsim?
> >
> > I do not know why, but copying 256 MB image to nandsim takes more
> > time than losetup & block2mtd & mount...
>
> May be, how much more? Is that a show-stopper for you? If you copy
> with 'dd', try 'bs=2048' if you are simulating a device with a 2048
> bytes NAND page size.
>
> But I guess you can patch block2mtd, I do not have objections
> (although it'll report about itself as NOR flash?), but I never used
> it and I am not sure how many bugs there are.
Hi! Years ago I wrote patches for block2mtd to allow specify write size
and nand subpage shift. But I forgot to send them. I think they could be
useful for other people, so rebased them on mainline kernel I will send
them in few minutes.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2017-06-02 15:40 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
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 [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=201706021739.59748@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.