mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Stefan Reinauer <stefan.reinauer@coresystems.de>
To: barebox@lists.infradead.org
Subject: Re: BIOS like screen for uboot
Date: Fri, 05 Nov 2010 19:25:14 -0700	[thread overview]
Message-ID: <4CD4BC8A.7060502@coresystems.de> (raw)
In-Reply-To: <AANLkTi=OBTyCqTLhLjzp04714cVzF+GEm0pALiu50Z8S@mail.gmail.com>

On 11/1/10 4:36 AM, Kallol Biswas wrote:
> Hi,
>      We have a customer request that we need to create a BIOS like
> screens for uboot.
>
> For this we have cross compiled curses library under uboot but have
> been getting error in
> linking phase we have expected.
>
> The major effort is to get termcap database into uboot.
Hm.. I hate patronizing people, but are you sure you (or your customers)
want that? BIOS screens are by far the most useless user interface around.

However, I think you have several options.

One, for sure, is the menu command as Robert suggested.

If you really want to go for a curses style interface I suggest that you
look at "libpayload" which is a library containing slimmed down
functions for a lot of things, including a pretty small curses
implementation that works on framebuffers, text consoles and serial
consoles. It's released under a BSD style license.

Check out http://www.coreboot.org/Libpayload

The last option might be to boot a Linux kernel and use real userland
ncurses, if you really need to (i.e. if you want i18n stuff, too). It is
also the most bloated option.

HTH
Stefan


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      parent reply	other threads:[~2010-11-06  2:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01 11:36 Kallol Biswas
2010-11-05  9:58 ` Robert Schwebel
2010-11-06  2:25 ` Stefan Reinauer [this message]

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=4CD4BC8A.7060502@coresystems.de \
    --to=stefan.reinauer@coresystems.de \
    --cc=barebox@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