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 21:02:38 +0100	[thread overview]
Message-ID: <20111205200238.6818318E00D9@gemini.denx.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1112051242090.4383@oneiric>

Dear Robert,

In message <alpine.DEB.2.02.1112051242090.4383@oneiric> you wrote:
> 
> > 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.
...
>   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.

I was very careful, actually.

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

I told you, several times, and I repeat it here again, for the last
time, promised:

If you want to have an easy start, use a separate device tree. This is
what has been tested all the time, and what is known to be working.

If you go for cuImage, this is completely untested code on TQM8xx, and
you are on your own - this may work, but it is more likely that it
doesn't.

Your choice.

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

You already updated U-Boot successfully, so there is no need to
continue trying cuImages.  But it's your choice.


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
It is easier to change the specification to fit the program than vice
versa.

  reply	other threads:[~2011-12-05 20:02 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
2011-12-05 20:02             ` Wolfgang Denk [this message]
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=20111205200238.6818318E00D9@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.