From: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
To: Denys Dmytriyenko <denys@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: linux-omap-psp and security code
Date: Tue, 31 Jul 2012 23:59:17 +0300 [thread overview]
Message-ID: <50184725.80703@mentor.com> (raw)
In-Reply-To: <20120731201625.GC21245@edge>
Hi Denys,
On 31.07.2012 23:16, Denys Dmytriyenko wrote:
> This one got stuck in the moderation queue with all the spam... Just wanted to
> comment on the third option, though.
>
> On Thu, Jul 19, 2012 at 01:31:26PM +0300, Vladimir Zapolskiy wrote:
>> 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.
>
> FWIW, I previously made a similar fix for this type of issue:
>
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/commit/?id=051482e3b03ba7e2d6cecc0d8f85cc3be22dc8b2
Eventually I verified this alternative and found that it won't work
as expected in this particular case. Here assembly instructions are
ingrained in C code, and after compilation there will be ".arch armv7"
directive in the generated assembly sources, which has precedence
over -march assembler flag. So, the only remaining option is to fix C
code.
But asflags method shall work fine with pure assembly sources like
in your fix.
> But either way it's better to update to a more recent 2.6.37 kernel for AM37x
> anyway, which I'll work on next.
Indeed. Excluding two problematic (and IMO useless and potentially
destructive) patches may be a good immediate measure to restore the
builds, but it's up to you to disable them or not. Having support
of the boards in 2.6.37 is the best option for sure.
With best wishes,
Vladimir
prev parent reply other threads:[~2012-07-31 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 10:31 linux-omap-psp and security code Vladimir Zapolskiy
2012-07-31 20:16 ` Denys Dmytriyenko
2012-07-31 20:59 ` Vladimir Zapolskiy [this message]
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=50184725.80703@mentor.com \
--to=vladimir_zapolskiy@mentor.com \
--cc=denys@ti.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.