linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Failure to boot...
Date: Thu, 31 Jan 2013 09:20:24 +0000	[thread overview]
Message-ID: <20130131092024.GN2637@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.02.1301302312030.6300@xanadu.home>

On Wed, Jan 30, 2013 at 11:19:40PM -0500, Nicolas Pitre wrote:
> Better yet (IMHO): just enable the zboot command in U-Boot to let you 
> boot a zImage binary directly.

I wish it were that easy but it isn't.  I've no idea where to get a
version of uboot for my boards which supports that; TI have always
supplied updates to uboot for me, and with the current state of TI
being afaict in chaos.

TI have always supplied a replacement X-Loader with each uboot update.
I've no idea what X-Loader is or why both get updated together, but...

Moreover, I doubt that the 3430LDP, of which there are multiple versions,
will ever see a uboot update.  It already suffers from a lack of correct
kernel support due to random wiring changes between these versions (the
keypad doesn't work correctly) and I've yet to indentify which version
it is despite downloading the circuits.  So trying to locate the right
uboot will be impossible there.

So, I'm _stuck_ with uImages for these platforms.

  reply	other threads:[~2013-01-31  9:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31  1:49 Failure to boot Russell King - ARM Linux
2013-01-31  3:02 ` Olof Johansson
2013-01-31  4:19   ` Nicolas Pitre
2013-01-31  9:20     ` Russell King - ARM Linux [this message]
2013-01-31 10:40       ` Russell King - ARM Linux
2013-01-31 12:49         ` Santosh Shilimkar
2013-01-31 13:04           ` Russell King - ARM Linux
2013-01-31 14:00             ` Santosh Shilimkar
2013-01-31 14:10               ` Santosh Shilimkar
2013-01-31 14:13               ` Russell King - ARM Linux
2013-01-31 14:16                 ` Russell King - ARM Linux
2013-01-31 14:20                   ` Santosh Shilimkar
2013-01-31 14:27                     ` Russell King - ARM Linux
2013-01-31 14:43                       ` Santosh Shilimkar
2013-01-31 16:00                         ` Tony Lindgren
2013-01-31 16:19                           ` Russell King - ARM Linux
2013-01-31 16:01                       ` Fabio Estevam
2013-01-31 16:18                         ` Russell King - ARM Linux
2013-01-31 16:27                           ` Arnd Bergmann
2013-01-31 17:51                             ` [PATCH, RFC] default machine descriptor for multiplatform Arnd Bergmann
2013-01-31 18:52                               ` Stephen Warren
2013-01-31 20:57                                 ` Arnd Bergmann
2013-01-31 20:34                               ` Nicolas Pitre
2013-02-01 11:47                               ` Santosh Shilimkar
2013-02-01 12:34                                 ` Arnd Bergmann
2013-02-05 21:37                               ` Rob Herring
2013-02-05 22:23                                 ` Arnd Bergmann
2013-02-05 21:39                               ` Olof Johansson
2013-03-03 13:27                               ` Rob Herring

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=20130131092024.GN2637@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).