public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot Graphics Library?
Date: Fri, 18 Jan 2013 01:50:56 +0100	[thread overview]
Message-ID: <50F89C70.7030003@ahsoftware.de> (raw)
In-Reply-To: <20130116194630.A2656203ACF@gemini.denx.de>

Am 16.01.2013 20:46, schrieb Wolfgang Denk:
> Dear Simon Glass,
>
> In message <CAPnjgZ12psS6sOnsuMU-VrrXWxS04Zb+grqqGUKNw2DTzBupag@mail.gmail.com> you wrote:
>>
>> We are currently using a very rudimentary graphics features attached
>> to U-Boot. It can only display bitmap images. We use this in Chromium
>> to composite a display for the various screens we need to display in
>> U-Boot. Unfortunately the graphics screens get quite large when using
>> multiple languages since they are pre-rendered.
>>
>> Is there any interest in a simply graphics library in U-Boot, that can
>> display things on the screen? We already have bitmap support, but
>> could perhaps add outline font support (e.g. freetype) as well. This
>> might allow display of simple boot menus or booting information. A
>> board could create a structure containing a list of things to display
>> (text, bitmaps) and pass it to the graphics library for rendering
>> using existing functions and the new font support.
>
> 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?

Yes. Sounds nice at first, but there will be no end of features people 
would want afterwards. Next will be video tutorials and fancy sound. ;)

And I think too that all this can be handled by adding a kernel (e.g. 
with integrated minimal initramfs) to u-boot. At least that is how I 
have handled such in the past.

Regards,

Alexander

  parent reply	other threads:[~2013-01-18  0:50 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
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 [this message]
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=50F89C70.7030003@ahsoftware.de \
    --to=holler@ahsoftware.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