From: "Måns Rullgård" <mans@mansr.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Data Abort with gcc 7.1
Date: Thu, 13 Jul 2017 13:34:52 +0100 [thread overview]
Message-ID: <yw1xy3rssefn.fsf@mansr.com> (raw)
In-Reply-To: <20170713123209.qmeuv7jej2cpvvrk@flea> (Maxime Ripard's message of "Thu, 13 Jul 2017 14:32:09 +0200")
Maxime Ripard <maxime.ripard@free-electrons.com> writes:
> On Thu, Jul 13, 2017 at 11:20:34AM +0100, Peter Robinson wrote:
>> >>> What hardware did this happen on? If it was on ARMv5, adding the packed
>> >>> attribute is probably the correct fix. If it was ARMv6 or later,
>> >>> something else is broken as well.
>> >>
>> >> It does not matter if this was ARMv6+ hardware or not. The current
>> >> U-Boot code is wrong and we need to fix it.
>> >
>> > The question is how many errors there are. That's why I asked about the
>> > hardware.
>>
>> I've seen it on a number of devices but they were all ARMv7+
>> (AllWinner, Rockchips etc)
>
> It was on an Allwinner SoCs with a Cortex-A7 CPU, so armv7. However,
> as far as I know, the unaligned accesses are disable in u-boot.
Yes, so it seems, although I can't fathom why.
--
Måns Rullgård
next prev parent reply other threads:[~2017-07-13 12:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 16:54 [U-Boot] Data Abort with gcc 7.1 Maxime Ripard
2017-07-11 16:59 ` Tom Rini
2017-07-11 17:59 ` Dr. Philipp Tomsich
2017-07-12 14:20 ` Maxime Ripard
2017-07-12 14:34 ` Tom Rini
2017-07-12 14:41 ` Dr. Philipp Tomsich
2017-07-12 15:30 ` Thomas Petazzoni
2017-07-12 17:37 ` Tom Rini
2017-07-12 15:48 ` Dr. Philipp Tomsich
2017-07-12 17:49 ` Tom Rini
2017-07-12 17:49 ` Dr. Philipp Tomsich
2017-07-12 18:07 ` Siarhei Siamashka
2017-07-12 18:26 ` Dr. Philipp Tomsich
2017-07-12 20:42 ` Mark Kettenis
2017-07-12 17:55 ` Siarhei Siamashka
2017-07-13 0:43 ` Måns Rullgård
2017-07-13 3:52 ` Siarhei Siamashka
2017-07-13 10:11 ` Måns Rullgård
2017-07-13 10:20 ` Peter Robinson
2017-07-13 12:32 ` Maxime Ripard
2017-07-13 12:34 ` Måns Rullgård [this message]
2017-07-23 10:55 ` Jörg Krause
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=yw1xy3rssefn.fsf@mansr.com \
--to=mans@mansr.com \
--cc=u-boot@lists.denx.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