All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] having trouble booting a simple kernel on a TQM860 board
Date: Mon, 05 Dec 2011 13:58:58 +0100	[thread overview]
Message-ID: <20111205125858.581321408765@gemini.denx.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1112050701340.21244@oneiric>

Dear Robert,

In message <alpine.DEB.2.02.1112050701340.21244@oneiric> you wrote:
>
> > No.  Now you don't need a cuImage nay more.  Just use the DT as I
> > showed you in the builkd and boot log I sent before.
> 
>   for the sake of clarification, you write that i don't *need*
> cuImages anymore, but that's not the same as saying that i *must* move
> to using device trees.  in fact, a cuImage file still works just fine

True, you don't have to use the DT.  You don't have to use the most
straightforward way that has been well tested for a ton of
combinations of recent U-Boot releases against recent kernel releases.

You are free to chose any untested, unsupported way you like.

It's perfectly fine to ignore all good advice you get here. But
eventually you should then also stop asking further questions here.

> for my lite5200 boards, so obviously the version of u-boot that i've
> flashed to my TQM boards can still handle that format.

Of course U-Boot can handle this.

>   so while it's probably a good idea to move to the device tree
> recipe, that still doesn't explain why i can't use a cuImage file for
> my tqm boards.  so i'll test the device tree process later today, but
> i'm still curious as to why a cuImage format file still fails in this
> case when it works just fine for the other boards.

Because this code has never been adapted for nor tested with any
TQM8xx boards?  But frankly, who cares?  This code simply is not
needed for these boards.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
grep me no patterns and I'll tell you no lines.

  reply	other threads:[~2011-12-05 12:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02 23:19 [U-Boot] having trouble booting a simple kernel on a TQM860 board Robert P. J. Day
2011-12-02 23:29 ` Scott Wood
2011-12-02 23:41   ` Robert P. J. Day
2011-12-02 23:49     ` Scott Wood
2011-12-03  0:03       ` Robert P. J. Day
2011-12-03  0:17     ` Wolfgang Denk
2011-12-05  2:14   ` Robert P. J. Day
2011-12-05 10:09     ` Wolfgang Denk
2011-12-05 10:37       ` Robert P. J. Day
2011-12-05 12:05       ` Robert P. J. Day
2011-12-05 12:58         ` Wolfgang Denk [this message]
2011-12-05 17:48           ` Robert P. J. Day
2011-12-05 20:02             ` Wolfgang Denk
2011-12-03  0:16 ` Wolfgang Denk
2011-12-03  0:23   ` Robert P. J. Day
2011-12-03  0:26     ` Wolfgang Denk

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=20111205125858.581321408765@gemini.denx.de \
    --to=wd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.