public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Bas Mevissen <abuse@basmevissen.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] denx/master is not building for OMAP3 platforms except Beagle
Date: Tue, 05 Oct 2010 14:34:28 +0200	[thread overview]
Message-ID: <dc274b9a5e5be6a8dab026cdd07c82fb@localhost> (raw)
In-Reply-To: <4CA976E4.4020104@dawes.za.net>

On Mon, 04 Oct 2010 08:40:36 +0200, Rogan Dawes <rogan@dawes.za.net>
wrote:

> For what it is worth, would it be possible to have a more verbose error
> message that actually provides a reference to what needs to be done,
> rather than simply failing with an obscure message about DRAM configuration?
> 

Maybe something like a file called e.g. CommonErrors containing common
build and runtime errors and an explanation what might be the problem. A
simple grep in this file for a few keywords shown in the build or run
failure might provide helpful info then.

Regards,

-- 
Bas

      parent reply	other threads:[~2010-10-05 12:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-03 10:50 [U-Boot] denx/master is not building for OMAP3 platforms except Beagle Hiremath, Vaibhav
2010-10-03 11:06 ` Albert ARIBAUD
2010-10-03 13:46   ` Hiremath, Vaibhav
2010-10-03 18:37     ` Wolfgang Denk
2010-10-04  5:08       ` Hiremath, Vaibhav
2010-10-04  6:00 ` Heiko Schocher
2010-10-04  6:40   ` Rogan Dawes
2010-10-04  8:06     ` Heiko Schocher
2010-10-04 12:43       ` Detlev Zundel
2010-10-04 12:50         ` Wolfgang Denk
2010-10-04 12:56         ` Heiko Schocher
2010-10-05 11:46           ` Detlev Zundel
2010-10-05 12:34     ` Bas Mevissen [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=dc274b9a5e5be6a8dab026cdd07c82fb@localhost \
    --to=abuse@basmevissen.nl \
    --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