From: Carlos Hernandez <ceh@ti.com>
To: "Cooper Jr., Franklin" <fcooper@ti.com>,
"Dmytriyenko, Denys" <denys@ti.com>,
"meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [PATCH 7/7][RFC] packagegroup-*-tisdk-addons: enable compiler and build essentials on omap-a15
Date: Tue, 17 Mar 2015 15:19:07 -0400 [thread overview]
Message-ID: <55087E2B.108@ti.com> (raw)
In-Reply-To: <8F29D6B095ED194EA1980491A5E029710C84948A@DFLE08.ent.ti.com>
On 03/17/2015 03:03 PM, Cooper Jr., Franklin wrote:
>> I marked this as RFC to solicit feedback. As explained in the 0/7 cover letter
>> >for the series, there are several methods to pull in gcc and build tools to the
>> >rootfs. This patch uses the least invasive one and enables minimal set of dev
>> >tools and only for omap-a15 SOC platforms (need to repeat it for keystone
>> >SOC). That covers Cortex-A15, but I know in the future we'd need target gcc
>> >also on am3/4 platforms - would you have any preferences to enable this?
> [Franklin] My understanding was the only reason this was needed is to enable developers to be able to compile
> dsp code and opencl code on the target for some reason especially since those are very powerful processors with a lot of memory.
>
> Unless something change this wasn't something we cared to enabled on 335x and 437x. No big deal doing it as long as the file system is bloated but I have no idea who really was going to use this/test this for those platforms.
Some Linaro tests does use make in the target. e.g.
https://git.linaro.org/?p=tools/pm-qa.git;a=summary
next prev parent reply other threads:[~2015-03-17 19:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 22:51 [PATCH 0/7] Enable target gcc compilation Denys Dmytriyenko
2015-03-16 22:51 ` [PATCH 1/7] toolchain-gcc: update versions for internal toolchain build Denys Dmytriyenko
2015-03-16 22:51 ` [PATCH 2/7] toolchain-linaro: prefer prebuilt Linaro runtime Denys Dmytriyenko
2015-03-16 22:51 ` [PATCH 3/7] gcc: overlay old 4.7 versions of core and linaro gcc recipes Denys Dmytriyenko
2015-03-16 22:51 ` [PATCH 4/7] gcc: handle different TARGET_SYS of OE vs. Linaro via symlinks Denys Dmytriyenko
2015-03-16 22:52 ` [PATCH 5/7] external-linaro-toolchain: package libgcc-dev stubs and libs for compilation Denys Dmytriyenko
2015-03-16 22:52 ` [PATCH 6/7] arago-prefs: set up preferences for target gcc Denys Dmytriyenko
2015-03-16 22:52 ` [PATCH 7/7][RFC] packagegroup-*-tisdk-addons: enable compiler and build essentials on omap-a15 Denys Dmytriyenko
2015-03-17 18:48 ` Denys Dmytriyenko
2015-03-17 19:03 ` Cooper Jr., Franklin
2015-03-17 19:19 ` Carlos Hernandez [this message]
2015-03-17 19:32 ` Cooper Jr., Franklin
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=55087E2B.108@ti.com \
--to=ceh@ti.com \
--cc=denys@ti.com \
--cc=fcooper@ti.com \
--cc=meta-arago@arago-project.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.