From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot Graphics Library?
Date: Fri, 18 Jan 2013 10:18:43 +0100 [thread overview]
Message-ID: <50F91373.5070903@denx.de> (raw)
In-Reply-To: <CAPnjgZ3rNhvL98JEOPV=90u-Wr3iEqs8QgqYaz=bOohRFRJeEA@mail.gmail.com>
On 16/01/2013 22:46, Simon Glass wrote:
> Hi Wolfgang,
>
Hi Simon,
>>
>> This sounds like a nice feature. Initially. Then I start wondering
>> if this really belongs into a boot loader. Instead of doing fancy
>> graphics stuff, we should IMO rather focus on booting the OS of your
>> choice really fast, and let this do the fancy GUIs. Or?
>>
>
> The problem is that a major purpose of the GUIs is to allow installing
> an OS from a USB stick/SD card, since the OS may have become corrupted
> and unbootable. We have looked at keeping around a separate OS image
> for this (e.g. in an available disk partition), but so far that hasn't
> proved practical since that itself can be fairly easily overwritten
> and we then have a doorstop.
>
Well, if a separate OS image can be overwritten, U-Boot image can be
overwritten too, and then the board does not boot at all.
I provided for a customer a solution with a separate OS and a small
rootfs as initramfs, and even if it is theoretically possible to destroy
this image, it has the same probability that U-Boot has to disappear. It
still seems to me a good solution, with the drawback to use much more
resorces (Flash) that a U-Boot solution can use. Anyway, with the
current size of NAND flash, even this drawback is not very important in
many projects.
Maybe more as a GUI-guided recovery, the customer needs a way to rescue
the system when everything goes wrong. Providing a booting SD or USB
card, that can complete restore the system, seems to be a good way, or
at least it was in my case.
Implementing it in U-Boot seems to me overkilling, but is only my 2
cents ;-).
Best regards,
Stefano
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2013-01-18 9:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 15:17 [U-Boot] U-Boot Graphics Library? Simon Glass
2013-01-16 19:46 ` Wolfgang Denk
2013-01-16 21:46 ` Simon Glass
2013-01-16 22:40 ` Wolfgang Denk
2013-01-16 22:54 ` Simon Glass
2013-01-17 7:05 ` Dirk Behme
2013-01-17 7:53 ` James W.
2013-01-17 12:56 ` Wolfgang Denk
2013-01-17 12:48 ` Wolfgang Denk
2013-01-18 9:18 ` Stefano Babic [this message]
2013-01-18 13:23 ` Simon Glass
[not found] ` <CAGrmWbzMM33kvQjvDEn66e_XO+GrV+UYb9uVxqUv0iHAnKm3Vg@mail.gmail.com>
2013-01-18 20:57 ` Simon Glass
2013-01-21 1:29 ` Alexander Holler
2013-01-22 11:29 ` Alexander Holler
2013-01-18 0:50 ` Alexander Holler
2013-01-18 1:22 ` [U-Boot] cc-list modified? Alexander Holler
2013-01-18 3:17 ` Scott Wood
2013-01-18 16:32 ` Alexander Holler
2013-01-21 2:53 ` Alexander Holler
2013-01-21 18:19 ` Scott Wood
2013-01-21 18:32 ` Alexander Holler
2013-01-18 8:49 ` [U-Boot] U-Boot Graphics Library? Albert ARIBAUD
2013-01-16 22:42 ` Andre Renaud
2013-01-16 22:57 ` Simon Glass
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=50F91373.5070903@denx.de \
--to=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
/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