All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Stevens <darren@stevens-zone.net>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, Pat Wall <pjwall@mac.com>,
	rtd@a-eon.com, aperez@alexperez.com,
	Christian Zigotzky <chzigotzky@xenosoft.de>
Subject: Re: powerpc/pasemi/nemo: Fix low memory values for boot.
Date: Mon, 23 Jan 2017 19:15:25 +0000 (GMT)	[thread overview]
Message-ID: <497a17344e3.4cea1c9d@auth.smtp.1and1.co.uk> (raw)
In-Reply-To: <87h94qb8u2.fsf@concordia.ellerman.id.au>

Hello Michael

On 23/01/2017, Michael Ellerman wrote:
>> Clearing the long long at addr 8 has been shown to fix this, so
>> add an initalisation to head_64.S so the system will boot.
>
> I'd really prefer it if someone could tell me why we need to clear it.
> But I assume no one knows?

The problem was found by Christian, and the fix comes courtesy of Olof
Johansson, I've not looked into it before.

> I don't want to pollute this code with NEMO workarounds if we can avoid
> it.

To be honest, so would I.

> You said the hang happens after printing the initial memory map, I'm not
> quite sure where you mean, but it sounds like that will be late enough
> that we can do the clear in pasemi platform code?

During prom_init. Where it says 'Memory layout at Init'

I took a long look today and traced the problem the 'prom_find_boot_cpu' and a
much better patch will follow.

Regards
Darren

  reply	other threads:[~2017-01-23 19:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-20 17:46 [PATCH] powerpc/pasemi/nemo: Fix low memory values for boot Darren Stevens
2017-01-20 20:22 ` Segher Boessenkool
2017-01-23  6:15 ` Michael Ellerman
2017-01-23 19:15   ` Darren Stevens [this message]
2017-01-24  4:46     ` Michael Ellerman

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=497a17344e3.4cea1c9d@auth.smtp.1and1.co.uk \
    --to=darren@stevens-zone.net \
    --cc=aperez@alexperez.com \
    --cc=chzigotzky@xenosoft.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=pjwall@mac.com \
    --cc=rtd@a-eon.com \
    /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.