All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John Willis" <John.Willis@Distant-earth.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [RFC] Add ubi volume image support, fix ubifs
Date: Wed, 11 Feb 2009 16:18:02 -0000	[thread overview]
Message-ID: <000c01c98c64$51bfc3b0$f53f4b10$@Willis@Distant-earth.com> (raw)
In-Reply-To: <20090211002752.GJ11815@smtp.west.cox.net>

Hi,

Thanks for these patches. Looking good IMHO.

> >> Really?  iirc from the mounting commandline stuff that means you
> have to
> >> pass in machine-rootfs rather than just rootfs, ie
> >> root=ubi0:machine-rootfs not root=ubi0:rootfs
> >
> > You'll have to update your bootloaders anyway, so cutting down on
> > 'flashed wrong machine' errors is a big win :)
> 
> The PoV we have is of starting things from scratch, so that's not
> something we worry about.  How about this so distros can take care of
> it?

Yep, I can't really see many normal OE users will have converted existing
images over to UBI so it seems like the right way to start is as we mean to
go on.

I'll test these patches on the Pandora NAND image later (they are along the
same lines as the patches I have been working on for UBI/UBIFS support but
have the extra bonus feature of actually looking like they work). 
It will make a nice change from post processing a TAR ;).
 
Regards,

John Willis






  parent reply	other threads:[~2009-02-11 16:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10 20:48 [RFC] Add ubi volume image support, fix ubifs Tom Rini
2009-02-10 22:43 ` Koen Kooi
2009-02-10 22:59   ` Tom Rini
2009-02-10 23:42     ` Koen Kooi
2009-02-11  0:27       ` Tom Rini
2009-02-11  8:09         ` Koen Kooi
2009-02-11 16:18         ` John Willis [this message]
2009-02-12 22:45 ` Koen Kooi

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='000c01c98c64$51bfc3b0$f53f4b10$@Willis@Distant-earth.com' \
    --to=john.willis@distant-earth.com \
    --cc=openembedded-devel@lists.openembedded.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.