From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: SoCFPGA with CONFIG_THUMB2_KERNEL boot error
Date: Wed, 20 Apr 2016 11:55:41 +0200 [thread overview]
Message-ID: <20160420095541.GG31470@pengutronix.de> (raw)
In-Reply-To: <CAKv+Gu9rzxtw2i1QJAU0C-y4Lmh6KDWH0p+TYNHsndr-6c11zw@mail.gmail.com>
On Wed, Apr 20, 2016 at 11:43:30AM +0200, Ard Biesheuvel wrote:
> (replying to self)
>
> On 20 April 2016 at 11:39, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> > (+ Arnd)
> >
> > On 20 April 2016 at 11:25, Dave Martin <Dave.Martin@arm.com> wrote:
> >> On Tue, Apr 19, 2016 at 04:02:20PM +0200, Steffen Trumtrar wrote:
> >>> Hi!
> >>>
> >>> According to kernelci.org (and validating on my own hardware), the current
> >>> socfpga mainline kernel has an issue with CONFIG_THUMB2_KERNEL enabled.
> >>>
> >>> https://storage.kernelci.org/mainline/v4.6-rc4-11-g12566cc35d0e/arm-multi_v7_defconfig/lab-khilman/boot-socfpga_cyclone5_de0_sockit.html
> >>>
> >>> vs
> >>>
> >>> https://storage.kernelci.org/mainline/v4.6-rc4-11-g12566cc35d0e/arm-multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/lab-khilman/boot-socfpga_cyclone5_de0_sockit.html
> >>>
> >>> Both boot successfully, but notice that the board fails to bring up CPU1 if
> >>> thumb2 support is enabled.
> >>>
> >>> Any ideas why this might be happening?
> >>
>
> Actually, this looks like a problem with the secondary entry point to
> me. Could you try this?
Been there, done that. Unfortunately this does not solve the problem.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2016-04-20 9:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 14:02 SoCFPGA with CONFIG_THUMB2_KERNEL boot error Steffen Trumtrar
2016-04-20 9:25 ` Dave Martin
2016-04-20 9:39 ` Ard Biesheuvel
2016-04-20 9:43 ` Ard Biesheuvel
2016-04-20 9:55 ` Sascha Hauer [this message]
2016-04-20 10:26 ` Ard Biesheuvel
2016-04-20 11:00 ` Sascha Hauer
2016-04-20 11:06 ` Ard Biesheuvel
2016-04-20 23:51 ` Russell King - ARM Linux
2016-04-21 6:24 ` Ard Biesheuvel
2016-04-21 7:52 ` Ard Biesheuvel
2016-04-20 11:06 ` Sascha Hauer
2016-04-20 15:55 ` Dinh Nguyen
2016-04-21 6:54 ` Sascha Hauer
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=20160420095541.GG31470@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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.