From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Lluís Batlle i Rossell" <viriketo@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: block2mtd and ubi
Date: Mon, 22 Nov 2010 12:21:23 +0200 [thread overview]
Message-ID: <1290421283.2289.32.camel@localhost> (raw)
In-Reply-To: <20101122100008.GL9645@vicerveza.homeunix.net>
On Mon, 2010-11-22 at 11:00 +0100, Lluís Batlle i Rossell wrote:
> On Mon, Nov 22, 2010 at 11:32:45AM +0200, Artem Bityutskiy wrote:
> > On Mon, 2010-11-22 at 10:09 +0100, Lluís Batlle i Rossell wrote:
> > > On Mon, Nov 22, 2010 at 10:12:42AM +0200, Artem Bityutskiy wrote:
> > > > On Sun, 2010-11-21 at 01:01 +0100, Lluís Batlle i Rossell wrote:
> > > > > On Sat, Nov 20, 2010 at 06:58:56PM +0100, Lluís Batlle i Rossell wrote:
> > > > > It's a pity that the same 'ubinize' cannot do that job automatically, and give
> > > > > an image filling all the memory blocks. That would easy down a lot the job for
> > > > > block2mtd.
> > > >
> > > > Use ubiformat - it should get it right:
> > > >
> > > > http://www.linux-mtd.infradead.org/faq/ubi.html#L_flash_img
> > >
> > > I know, but I cannot do that on a block2mtd, if the block2mtd device I use is
> > > the rootfs of the system. All I have is a kernel, qemu, and a rootfs in a
> > > 'ubinize' ubi image.
> >
> > Why you can dd buy cannot ubiformat? What is the fundamental difference?
> ubiformat works on a mtd character device, while dd works on a block device.
But you can turn a block device into mtd device using block2mtd, so I do
not still see the fundamental difference.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-11-22 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-20 17:58 block2mtd and ubi Lluís Batlle i Rossell
2010-11-21 0:01 ` Lluís Batlle i Rossell
2010-11-22 8:12 ` Artem Bityutskiy
2010-11-22 9:09 ` Lluís Batlle i Rossell
2010-11-22 9:32 ` Artem Bityutskiy
2010-11-22 10:00 ` Lluís Batlle i Rossell
2010-11-22 10:21 ` Artem Bityutskiy [this message]
2010-11-22 10:37 ` Lluís Batlle i Rossell
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=1290421283.2289.32.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=viriketo@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