All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Missing OMAP35x_Graphics_SDK_setuplinux_3_00_00_08.bin	during libgles-omap3_3.00.00.08.bb
Date: Tue, 11 Aug 2009 05:19:25 -0400	[thread overview]
Message-ID: <20090811091925.GA11120@denix.org> (raw)
In-Reply-To: <fce2a370908110100m2347b6fag409721b7f024b847@mail.gmail.com>

On Tue, Aug 11, 2009 at 11:00:47AM +0300, Ihar Hrachyshka wrote:
> On Tue, Aug 11, 2009 at 10:34 AM, Khem Raj<raj.khem@gmail.com> wrote:
> > On Mon, Aug 10, 2009 at 6:43 PM, Denys Dmytriyenko<denis@denix.org> wrote:
> >> On Mon, Aug 10, 2009 at 02:55:55PM -0700, John Faith wrote:
> >>> Khem Raj wrote:
> >>>> ...
> >>>> It seems like this file
> >>>> /home/kraj/work/oe/openembedded/recipes/powervr-drivers/libgles-omap3/OMAP35x_Graphics_SDK_setuplinux_3_00_00_08.bin
> >>>> is missing in my case.
> >>>>
> >>>> Where should it come from
> >>>
> >>> The Graphics SDK installer must be downloaded from Ti and manually put in
> >>> place before building libgles:
> >>> http://code.google.com/p/beagleboard/wiki/HowtoUseSGXunderAngstrom
> >>
> >> By the way, should it be done the same way as DVSDK - i.e. expect the
> >> installer in the downloads/ instead of the recipes/? Which way is better?
> >
> > FWIW I would prefer if it downloads the file for me somehow
> 
> Texas Instruments doesn't allow it.

For now, but it is being addressed and should be better in the future...

Denys



      reply	other threads:[~2009-08-11  9:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 20:51 Missing OMAP35x_Graphics_SDK_setuplinux_3_00_00_08.bin during libgles-omap3_3.00.00.08.bb Khem Raj
2009-08-10 21:55 ` John Faith
2009-08-11  1:43   ` Denys Dmytriyenko
2009-08-11  7:34     ` Khem Raj
2009-08-11  8:00       ` Ihar Hrachyshka
2009-08-11  9:19         ` Denys Dmytriyenko [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=20090811091925.GA11120@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-devel@lists.openembedded.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.