From: Richard Weinberger <richard@nod.at>
To: Shibin George <george.shibin1993@gmail.com>,
linux-mtd@lists.infradead.org
Subject: Re: gluebi vs. ubi-volume mapping
Date: Fri, 11 Jan 2019 13:44:12 +0100 [thread overview]
Message-ID: <1835331.mx3o4XuZP5@blindfold> (raw)
In-Reply-To: <CAGu8XfQ_iVh-5zb_h5FAi=wHifC+Drf1CPZbdiAzCXtjOoQmXg@mail.gmail.com>
Am Freitag, 11. Januar 2019, 13:42:11 CET schrieb Shibin George:
> > BTW: Why are you using glubi+mtdblock at all? To support squashfs we
> > have ubiblock.
> > That way you can use read-only block-based filesystems directly on top
> > of UBI without glubi
> > and mtdblock.
> ubiblock, being read-only, didn't satisfy my requirement.
> The device I am working on needs to have block-level software upgrade
> capability.
> So gluebi was the best solution that I could find that can run block-based
> filesystem.
Usually you don't want such a deep stacking on an embedded system.
But you are aware of ubiupdatevol?
Thanks,
//richard
next prev parent reply other threads:[~2019-01-11 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 6:35 gluebi vs. ubi-volume mapping Shibin George
2019-01-11 9:53 ` Richard Weinberger
2019-01-11 12:42 ` Shibin George
2019-01-11 12:44 ` Richard Weinberger [this message]
2019-01-11 12:54 ` Shibin George
2019-01-11 12:59 ` Richard Weinberger
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=1835331.mx3o4XuZP5@blindfold \
--to=richard@nod.at \
--cc=george.shibin1993@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox