From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS and bcm2835_defconfig
Date: Tue, 11 Mar 2014 22:35:24 -0600 [thread overview]
Message-ID: <531FE40C.1060709@wwwdotorg.org> (raw)
In-Reply-To: <alpine.DEB.2.10.1403101717050.31525@vincent-weaver-1.um.maine.edu>
On 03/10/2014 03:21 PM, Vince Weaver wrote:
> Hello
>
> I buit the current
> git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-rpi.git
> kernel on a Raspberry Pi.
>
> I used
> make bcm2835_defconfig
> make zImage
> but the results zImage hung at boot.
>
> It turned out that for some reason
> CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
> and
> CONFIG_ARCH_USE_BUILTIN_BSWAP=y
Hmm. I thought that ARMv6 didn't have efficient unaligned accesses, but
I suppose it must; ARM selects HAVE_EFFICIENT_UNALIGNED_ACCESS for
v6/v6k/v7. BUILTIN_BSWAP seems innocuous. Can you verify which of those
two options actually causes problems for you?
I'm not sure why either of these options would cause any trouble.
Perhaps Will might have some suggestions, since he authored the code
that selects HAVE_EFFICIENT_UNALIGNED_ACCESS, or Kim since he authored
the code that selects ARCH_USE_BUILTIN_BSWAP. Perhaps there are
compiler-version-specific bugs, or the RPi's native toolchain has issues?
next parent reply other threads:[~2014-03-12 4:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.10.1403101717050.31525@vincent-weaver-1.um.maine.edu>
2014-03-12 4:35 ` Stephen Warren [this message]
2014-03-12 11:03 ` CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS and bcm2835_defconfig Russell King - ARM Linux
2014-03-12 15:44 ` Stephen Warren
2014-03-12 16:05 ` Russell King - ARM Linux
2014-03-12 16:29 ` Måns Rullgård
2014-03-12 11:33 ` Will Deacon
2014-03-12 11:41 ` Vince Weaver
2014-03-12 19:20 ` Vince Weaver
2014-03-17 21:16 ` Vince Weaver
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=531FE40C.1060709@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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.