LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Small <tim@seoss.co.uk>
To: Scott Wood <oss@buserror.net>, linuxppc-dev@lists.ozlabs.org
Subject: Re: NXP p1010se device trees only correct for P1010E/P1014E, not P1010/P1014 SoCs.
Date: Mon, 9 Jul 2018 09:38:59 +0100	[thread overview]
Message-ID: <0bec4690-992b-a6ef-3989-a1ce96da825d@seoss.co.uk> (raw)
In-Reply-To: <bdc2e385580cc08bcbf9d5b3595cbca5162314f8.camel@buserror.net>

On 06/07/18 19:41, Scott Wood wrote:
>> My openwrt patch
>> just does a:
>>
>> /delete-node/  crypto@30000;
>>
>> after the p1010si-post.dtsi include.
> U-Boot should already be removing the node on non-E chips -- see
> ft_cpu_setup() in arch/powerpc/cpu/mpc85xx/fdt.c


Hi Scott,

Thanks for your email.  The device in question ships an old uboot (a 
vendor fork of U-Boot 2010.12-svn15934).

I am right in saying that the right fix is to either:

Use a bootloader (such as current upstream uboot) which adjusts the 
device tree properly...

or:

In the case (such as OpenWRT) where the preferred installation method is 
to retain the vendor bootloader, then the distro kernel should handle 
the device tree fixup itself?

Regards,

Tim.

  reply	other threads:[~2018-07-09  8:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06 14:50 NXP p1010se device trees only correct for P1010E/P1014E, not P1010/P1014 SoCs Tim Small
2018-07-06 18:41 ` Scott Wood
2018-07-09  8:38   ` Tim Small [this message]
2018-07-09 22:21     ` Scott Wood
2018-07-20 14:32       ` TP Link WDR4900 (was NXP p1010se device trees only correct for P1010E/P1014E, not P1010/P1014 SoCs) Tim Small

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=0bec4690-992b-a6ef-3989-a1ce96da825d@seoss.co.uk \
    --to=tim@seoss.co.uk \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=oss@buserror.net \
    /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