From: Denys Dmytriyenko <denys@ti.com>
To: Ash Charles <ashcharles@gmail.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: DSP packages for OMAP3
Date: Tue, 10 Jun 2014 22:56:39 -0400 [thread overview]
Message-ID: <20140611025637.GK18034@edge> (raw)
In-Reply-To: <CAK8F28kqBnnWBgdk3TXHqBLVW25sVchmQ-eUVf5ujbh=6Dcwtw@mail.gmail.com>
On Tue, Jun 10, 2014 at 04:04:43PM -0700, Ash Charles wrote:
> Hi,
>
> I was stepping through the meta-ti layer to assess support for the DSP
> on OMAP3[57].
>
> Two questions:
> 1. It looks like there are more recent versions of the code
> generation tools [1] (either 7.6.0 or 7.4.8) than 7.2.7. Is there any
> reason not to use these newer version? (Apologies if this is a dumb
> question---I just don't know enough about the DSP ecosystem)
>
> 2. It seems like ti-dsplink and ti-linuxutils (among others I suspect)
> have hardcoded compiler paths and flags that supersede those provided
> by bitbake. This is causing me headaches when trying to build with a
> hardfp compiler (as recent SGX binaries are provided in hardfp mode).
> Is there a technical limitation to compiling DSP support code with a
> hard float compiler? I don't mind taking a stab at making the
> makefiles a little more flexible but if the code itself relies on
> non-hardfp, I'll need to rethink.
Unfortunately, DSP support in meta-ti is not maintained currently, as
explained in the corresponding README file.
--
Denys
next prev parent reply other threads:[~2014-06-11 2:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 23:04 DSP packages for OMAP3 Ash Charles
2014-06-11 2:56 ` Denys Dmytriyenko [this message]
2014-06-11 8:13 ` Ash Charles
2014-06-11 14:35 ` Enrico
2014-06-12 23:09 ` Ash Charles
2014-06-13 14:32 ` Enrico
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=20140611025637.GK18034@edge \
--to=denys@ti.com \
--cc=ashcharles@gmail.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.