public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot limitation if any.
Date: Mon, 9 Jun 2014 19:31:53 +0200	[thread overview]
Message-ID: <E1Wu3QJ-0007zj-5X@janus> (raw)
In-Reply-To: <1402332031005-181821.post@n7.nabble.com>

Hi mazen.e,

On Mon, 9 Jun 2014 09:40:31 -0700 (PDT), "mazen.e"
<mazen.ezzeddine@gmail.com> wrote:

> Undoubtedly u-boot is very powerful and feature-rich bootloader. However,
> does it have any limitation? In other words what features if included to
> u-boot current functionality would result in a better efficiency in terms of
> performance, power,security,portability, boot-time,  or any other criteria.
> 
> I actually was writing a small research report about u-boot but could not
> identify any limitation to include :).

A few shortcomings off the top of my head:

- doesn't do windows;

- doesn't brew coffee;

- doesn't automatically detect sarcasm (so much for the US Secret
  Service).

Seriously, though: as long as you don't set some kind of expectations,
there is no way you can tell whether something meets them or not. So
what are your expectations -- what do you expect U-Boot to do?

If you don't know what to expect, but your research is about more than
one bootloader, then at least you can gather all the features of all
bootloaders, then for each feature, check which bootloader supports
it. That will give you at least relative limitations.

> Many thanks.

Amicalement,
-- 
Albert.

      reply	other threads:[~2014-06-09 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 16:40 [U-Boot] u-boot limitation if any mazen.e
2014-06-09 17:31 ` Albert ARIBAUD [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=E1Wu3QJ-0007zj-5X@janus \
    --to=albert.u.boot@aribaud.net \
    --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