All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert P. J. Day <rpjday@crashcourse.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] having trouble booting a simple kernel on a TQM860 board
Date: Mon, 5 Dec 2011 12:48:39 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1112051242090.4383@oneiric> (raw)
In-Reply-To: <20111205125858.581321408765@gemini.denx.de>

On Mon, 5 Dec 2011, Wolfgang Denk wrote:

> 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.

  please stop being so defensive, wolfgang, it doesn't become you.  i
have no doubt that using a separate device tree is a better idea.  but
i also like to be very careful with my terminology.

  if someone says using a device tree is better, i'm fine with that.
but an earlier claim of yours seemed to suggest that one *needed* to
use a DT, and if that's the case, i just want to know that. i simply
like to know what my options are in case Plan A doesn't work, i can
try Plan B.

  also, i was *given* material to work with, and i'm making an effort
to change as little of it as possible if i don't have to, at the
request of the person who gave it to me.  and sometimes, political
reasons might trump technical reasons, as much as we don't want them
to.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

  reply	other threads:[~2011-12-05 17:48 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
2011-12-05 17:48           ` Robert P. J. Day [this message]
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=alpine.DEB.2.02.1112051242090.4383@oneiric \
    --to=rpjday@crashcourse.ca \
    --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.