public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Revert "fdt: Fix fdtdec_get_addr_size() for 64-bit"
Date: Wed, 2 Sep 2015 13:04:33 -0700	[thread overview]
Message-ID: <55E75651.3040509@nvidia.com> (raw)
In-Reply-To: <f17d10691d434af6a63556e1a5077eb3@HQMAIL103.nvidia.com>

On 09/02/2015 09:52 AM, Tom Warren wrote:
> Simon, et al,
> 
>> Simon Glass wrote at Friday, August 14, 2015 3:05 AM:
>> I plan to apply this revert to u-boot-x86 (where SPI is currently
>> broken) and (once it has a bit more testing) also this patch which I think makes
>> the change in a safer way:
>>
>> https://patchwork.ozlabs.org/patch/504918/
>>
>> At present that patch breaks at least one x86 board and I have not dug into it
>> yet.
>>
>> The revert should not break tegra, according to Stephen.
> 
> Unfortunately, my testing on P2571 with TOT u-boot-tegra (rebased against TOT u-boot/master this morning) shows that that is not true.
> 
> The revert of the disputed 'fdtdec_get_addr_size' patch _does_ break Tegra 64-bit (P2571, at least). Nyan-big is OK.  With Simon's revert in place, my board just loops on SPL signon, so I assume it's faulting, etc. in CPU init.  Note that this is the current state of TOT u-boot/master.

I'm a bit confused. So far, we don't support SPL on T210 since we assume
some other bootloader runs on the boot CPU and starts just the main
U-Boot on the main CPU. It sounds like you're testing some local-only
SPL support?

  parent reply	other threads:[~2015-09-02 20:04 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03  0:13 [U-Boot] [PATCH] Revert "fdt: Fix fdtdec_get_addr_size() for 64-bit" Simon Glass
2015-08-03 15:12 ` Stephen Warren
2015-08-03 15:52   ` Simon Glass
2015-08-03 17:25     ` Tom Rini
2015-08-03 17:27       ` Simon Glass
2015-08-03 18:20     ` Stephen Warren
2015-08-05  4:08       ` Simon Glass
2015-08-05 18:22         ` Stephen Warren
2015-08-05 23:45           ` Simon Glass
2015-08-06  7:09             ` Michal Suchanek
2015-08-06 18:43               ` Stephen Warren
2015-08-06 19:03             ` Stephen Warren
2015-08-09 15:08               ` Simon Glass
2015-08-14  8:10                 ` Bin Meng
2015-08-14  8:32                   ` Thierry Reding
2015-08-14  8:44                     ` Bin Meng
2015-08-14 14:06                       ` Thierry Reding
2015-08-14 14:29                         ` Bin Meng
2015-08-14  9:01                   ` Michal Suchanek
2015-08-14  9:08                     ` Bin Meng
2015-08-14 10:04                       ` Simon Glass
2015-09-02 16:52                         ` Tom Warren
2015-09-02 16:58                           ` Simon Glass
2015-09-02 20:04                           ` Stephen Warren [this message]
2015-09-02 20:39                             ` Tom Warren
2015-09-02 20:54                               ` Stephen Warren
2015-09-02 23:43                                 ` Stephen Warren
2015-09-03  2:02                                   ` Tom Warren
2015-09-16 21:46                                   ` Tom Warren
2015-09-17  1:10                                     ` Simon Glass
2015-09-17  1:58                                       ` Tom Warren
2015-08-14 16:50               ` Simon Glass
2015-08-03 15:40 ` Bin Meng
2015-08-04 15:27 ` Thierry Reding

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=55E75651.3040509@nvidia.com \
    --to=swarren@nvidia.com \
    --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