From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: giorgio.nicole@arcor.de
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: imx7d enable second core
Date: Wed, 18 Jul 2018 09:54:34 -0700 [thread overview]
Message-ID: <CAHQ1cqFHRFYzKnjhD4-2+=-5dC8AGQNYKyuPZbwp8yWUauXAfw@mail.gmail.com> (raw)
In-Reply-To: <461871869.117927.1531898866247@mail.vodafone.de>
On Wed, Jul 18, 2018 at 12:28 AM Giorgio Dal Molin
<giorgio.nicole@arcor.de> wrote:
>
> Hi all,
>
> I'm currently working with the imx7d sabre board from NXP.
>
> I have now a running barebox bootloader and a booting kernel.
>
> My problem is now that, apparently, only one core is active:
>
> ...
> commandline: console=ttymxc0,115200n8 ip=11.0.0.4::11.0.0.2:255.0.0.0::eth0: root=/dev/mmcblk0p2 rootdelay=1
> Starting kernel in secure mode
AFAIK, this means that you are booting in secure mode and secure
monitor code, which also implements PSCI needed for SMP to work, will
_not_ be installed by Barebox. One way to fix this would be to set:
global.bootm.secure_state=nonsecure
before booting Linux. Doing that I get:
# lscpu -e
CPU SOCKET CORE ONLINE MAXMHZ MINMHZ
0 0 0 yes 996.0000 792.0000
1 0 1 yes 996.0000 792.0000
#
on my SabreSD board.
Thanks,
Andrey Smirnov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-07-18 16:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 7:27 Giorgio Dal Molin
2018-07-18 7:56 ` Oleksij Rempel
2018-07-18 16:54 ` Andrey Smirnov [this message]
2018-07-19 7:16 ` Giorgio Dal Molin
2018-07-19 16:02 ` Andrey Smirnov
2018-07-19 16:16 ` Giorgio Dal Molin
2018-07-19 15:52 ` Giorgio Dal Molin
2018-07-19 16:09 ` Andrey Smirnov
2018-07-19 16:18 ` Giorgio Dal Molin
2019-10-15 11:29 Giorgio Dal Molin
2019-10-15 11:37 ` Ahmad Fatoum
2019-10-15 11:51 ` Ahmad Fatoum
2019-10-15 12:11 ` Giorgio Dal Molin
2019-10-15 12:47 ` Ahmad Fatoum
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='CAHQ1cqFHRFYzKnjhD4-2+=-5dC8AGQNYKyuPZbwp8yWUauXAfw@mail.gmail.com' \
--to=andrew.smirnov@gmail.com \
--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