From: Richard Weinberger <richard@nod.at>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Artem Bityutskiy" <dedekind1@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Boris Brezillon" <boris.brezillon@free-electrons.com>,
"Brian Norris" <computersforpeace@gmail.com>
Subject: Re: [PATCH RFC 2/2] ubi: add support for UBI_EC_FLAG_ERASE_FROM_HERE
Date: Sat, 31 Dec 2016 11:03:18 +0100 [thread overview]
Message-ID: <415ea536-5c38-1dae-bc6e-ed8d453dc196@nod.at> (raw)
In-Reply-To: <CACna6ryjVENPpT-oQeKVVULXUGKNzht9SEnBXS+FXy00G30czg@mail.gmail.com>
Rafał,
On 30.12.2016 22:44, Rafał Miłecki wrote:
> Some of them do, but that requires serial access to the device. Most
> users use button-triggered tftp server/client or just minimal
> bootloader web interface for flashing an image. In these cases you
> don't have any control over what bootloader does.
So the use case is the initial installation of OpenWRT.
What about using an installer?
i.e. create Kernel with an in-kernel initramfs. This "installer kernel"
will get flashed using that button-triggered mechanism.
All the pre-installed bootloader has to do is flashing and booting the kernel.
This kernel will then boot and provide a fancy webinterface to the user
where she can install the OpenWRT rootfs. That way you can use all the Linux
tools for partitioning, flashing, verification(!), etc.
The installer kernel will be used only once can be get removed after the
installation on OpenWRT.
Thanks,
//richard
next prev parent reply other threads:[~2016-12-31 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 17:11 [PATCH RFC 1/2] ubi: add flags1 field to the EC header Rafał Miłecki
2016-12-30 17:11 ` [PATCH RFC 2/2] ubi: add support for UBI_EC_FLAG_ERASE_FROM_HERE Rafał Miłecki
2016-12-30 20:47 ` Richard Weinberger
2016-12-30 21:44 ` Rafał Miłecki
2016-12-31 10:03 ` Richard Weinberger [this message]
2016-12-31 9:37 ` Boris Brezillon
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=415ea536-5c38-1dae-bc6e-ed8d453dc196@nod.at \
--to=richard@nod.at \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=rafal@milecki.pl \
--cc=zajec5@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