From: Denys Dmytriyenko <denys@ti.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: meta-ti@yoctoproject.org, Tom Rini <trini@konsulko.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: Re: [PATCH] beaglebone.conf: temporarily use generic am335x_evm_config for U-boot
Date: Wed, 17 Oct 2018 15:37:16 -0400 [thread overview]
Message-ID: <20181017193716.GH4031@beryl> (raw)
In-Reply-To: <CAMKF1sqMCEGkNyOK_WgN6KfKs+_30tq-_868SrkSmxAjbRhGAA@mail.gmail.com>
On Wed, Oct 17, 2018 at 12:27:19PM -0700, Khem Raj wrote:
> On Wed, Oct 17, 2018 at 12:25 PM Denys Dmytriyenko <denys@ti.com> wrote:
> > > > > Yeah I saw that but this patch is not their in 2018.01 release that TI
> > > > fork
> > > > > is based on regardless I backported this patch to this version it did not
> > > > > bring the size below mark
> > > > > I think it’s because we are using hardened toolchain and that enalbles
> > > > > extra options to enable pie and ssp since these options get added to CC
> > > > > they get passed into uboot straight
> > > > >
> > > > > I think we should just disable security flags for u boot in OE and may be
> > > > > uboot make system should append fno-pie fno-stack-protector to nullify
> > > > > these options
> > > >
> > > > OK, do you want to submit a patch for that or should I do one and just
> > > > Suggested-by you? Thanks!
> > >
> > >
> > > This would not be acceptable change since it changes how we build gcc
> > > itself secondly it does not happen for master uboot
> > >
> > > However if this works then we need to understand why it increas e the size
> >
> > Even if this change is not acceptable upstream, I would prefer it locally in
> > meta-ti recipe, instead of disabling more features to free up 5-6KB in SPL.
>
> this is a distro level change. meta-ti is not appropriate place to decide that
Are we talking about passing fno-pie and fno-stack-protector to U-boot build
that you suggested above? That is what I'm referring here. It can be BBB
specific patch. That is until we figure out why it grows code so much...
--
Denys
next prev parent reply other threads:[~2018-10-17 19:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 2:50 [PATCH] beaglebone.conf: temporarily use generic am335x_evm_config for U-boot Denys Dmytriyenko
2018-10-13 8:17 ` Khem Raj
2018-10-14 19:24 ` Denys Dmytriyenko
2018-10-15 5:07 ` Khem Raj
2018-10-16 7:50 ` Khem Raj
2018-10-16 16:42 ` Tom Rini
2018-10-16 18:11 ` Khem Raj
2018-10-16 18:29 ` Denys Dmytriyenko
2018-10-16 18:38 ` Denys Dmytriyenko
2018-10-16 18:59 ` Tom Rini
[not found] ` <9e7016817d464dd8bfb1210b8e9e6cf5@SOC-EX01V.e01.socionext.com>
2018-10-17 2:55 ` Tom Rini
2018-10-17 4:06 ` Khem Raj
2018-10-17 4:37 ` Denys Dmytriyenko
2018-10-17 6:55 ` Khem Raj
2018-10-17 17:50 ` Denys Dmytriyenko
2018-10-17 11:26 ` Tom Rini
2018-10-17 15:00 ` Khem Raj
2018-10-17 19:25 ` Denys Dmytriyenko
2018-10-17 19:27 ` Khem Raj
2018-10-17 19:37 ` Denys Dmytriyenko [this message]
2018-10-17 19:46 ` Khem Raj
2018-10-16 18:50 ` Khem Raj
2018-10-16 19:00 ` Denys Dmytriyenko
2018-10-16 19:20 ` Khem Raj
2018-10-16 21:19 ` Khem Raj
2018-10-17 0:26 ` Denys Dmytriyenko
2018-10-17 0:37 ` Denys Dmytriyenko
2018-10-17 1:42 ` Khem Raj
2018-10-17 1:58 ` Denys Dmytriyenko
2018-10-17 2:26 ` Denys Dmytriyenko
2018-10-16 18:52 ` Tom Rini
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=20181017193716.GH4031@beryl \
--to=denys@ti.com \
--cc=meta-ti@yoctoproject.org \
--cc=raj.khem@gmail.com \
--cc=trini@konsulko.com \
--cc=yamada.masahiro@socionext.com \
/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.