From: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
To: <meta-ti@yoctoproject.org>
Subject: linux-omap-psp and security code
Date: Thu, 19 Jul 2012 13:31:26 +0300 [thread overview]
Message-ID: <5007E1FE.3070208@mentor.com> (raw)
Hello,
I have a question about linux-omap-psp-2.6.32 kernel and boards, which
uses this kernel, in particular about
0038-ARM-Expose-some-CPU-control-registers-via-sysfs.patch. The recent
toolchains based on binutils-2.21 or later imply more accurate handling
with `smc #0' instructions, which are found in the aforementioned patch.
The compilation of the linux-omap-psp kernel with such toolchains leads
to "selected processor does not support ARM mode `smc #0'" errors. The
patch itself adds /sys/devices/system/cpu/cpuN/ nodes providing access
to control register, auxiliary control register, and L2 cache auxiliary
control register.
I see several possible solutions of the problem, and I'd be glad to find
out the best one. First of all it might have sense to remove the patch
completely, because its functionality is purely optional, presumably it
is not used by any userspace programs and therefore can be omitted. As a
soft alternative CONFIG_CPU_V7_SYSFS kernel option for a list of boards
could be disabled in default kernel config files, but I personally don't
like this variant, because it merely veils a problem, better to remove
the patch itself.
One more option is to fix the patch, either remove store feature of
/sys/devices/system/cpu/cpuN/(l2_)?aux_control files or provide
-march=armv7-a+sec AFLAGS in Makefile.
Any suggestions and comments are appreciated.
With best wishes,
Vladimir
next reply other threads:[~2012-07-19 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 10:31 Vladimir Zapolskiy [this message]
2012-07-31 20:16 ` linux-omap-psp and security code Denys Dmytriyenko
2012-07-31 20:59 ` Vladimir Zapolskiy
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=5007E1FE.3070208@mentor.com \
--to=vladimir_zapolskiy@mentor.com \
--cc=meta-ti@yoctoproject.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.