mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Giorgio <giorgio.nicole@arcor.de>
Cc: barebox@lists.infradead.org
Subject: Re: imx7d dual core boot
Date: Mon, 6 Apr 2020 08:16:44 +0200	[thread overview]
Message-ID: <f075fcf2-5703-37ee-b197-84afe0585560@pengutronix.de> (raw)
In-Reply-To: <9bd7f507-8f59-98ee-18af-48be3dba9372@arcor.de>

Hello Giorgio,

On 4/3/20 3:47 PM, Giorgio wrote:
> Hi Ahmad,
> 
> thank you for the detailed explanations, I'll have a look
> at the armv7 ref. manual for more background.
> 
> I wanted just to note, the problem is specifically linked
> to enabling the MMU:
> 
> in arch/arm/cpu/cache-armv7.S:
> 
> 
> 		orrne	r0, r0, #1		@ MMU enabled
> ...
> 		mcr	p15, 0, r0, c1, c0, 0	@ load control register
> 
> without the 'orrne ...' the imx7 does not hang.

I can't reproduce this exact problem. My setup:

- i.MX7D sabresd board,
- imx_v7_defconfig
- check out of upstream/next, commit 5931fe40 ("Merge branch 'for-next/zii' into next")
- revert of commit 8b2104d ("driver: Call of_clk_set_defaults for each probed device")
- nv bootm.secure_state=nonsecure

With this, I didn't observe any barebox hangs[1] while preparing a Linux net boot.
What's your setup?

[1]: Linux still hangs due to what I assume to be a psci issue, kernel log says
     "unsupported enable-method property: psci" before getting stuck durcing SDHCI probe

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2020-04-06  6:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 10:21 Giorgio
2020-03-27  5:56 ` Ahmad Fatoum
2020-03-27  8:27   ` Giorgio
2020-03-27 10:01     ` Ahmad Fatoum
2020-03-30 14:33       ` Giorgio
2020-04-03 13:01         ` Ahmad Fatoum
2020-04-03 13:47           ` Giorgio
2020-04-06  6:16             ` Ahmad Fatoum [this message]
2020-04-06  6:29               ` Ahmad Fatoum
2020-04-06 15:15               ` Giorgio
2020-04-06 18:44                 ` Ahmad Fatoum
2020-04-07  7:46                   ` Giorgio
2020-04-07  8:23                     ` Ahmad Fatoum
2020-04-07 12:28                       ` Giorgio
2020-04-07 13:43                         ` Ahmad Fatoum
2020-04-13 22:30                           ` Giorgio
2020-04-14  7:59                             ` Sascha Hauer
2020-04-14 13:05                               ` Giorgio

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=f075fcf2-5703-37ee-b197-84afe0585560@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=giorgio.nicole@arcor.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