All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: arago-devel@gforge.ti.com
Subject: Re: [arago-devel] dm365 and OE
Date: Mon, 26 Apr 2010 22:57:03 -0400	[thread overview]
Message-ID: <20100427025702.GC10320@denix.org> (raw)
In-Reply-To: <x2rade1bdc1004261848k1f9cfc01yc64057689a22fbb1@mail.gmail.com>

On Tue, Apr 27, 2010 at 03:48:17AM +0200, Raffaele Recalcati wrote:
> I'll try to go on with both for some weeks.
> But, first of all, I need a dvsdk running on dm365 with Arago.
> By now, I can't build any ti recipe for dm365 in Arago (arago-next).
> I could build dvsdk externally following the readme, but I think it is
> better to re-use you work.
> Which are the recipes that I can build for dm365?

arago-next was merged back to the master branch recently, but it shouldn't 
matter, as DVSDK was buildable before the merge. If you are referring to the 
fact that some components are not fetchable and need to be downloaded 
manually, it's still the case for a few of them, as explained in the README.
AFAIK, codecs for some platforms were not public at the time, I believe dm365 
being one of them. I'll ping some people internally and see if/when this will 
be fixed.

> In case of problem I, and my team, will contribute to the work.

Thanks. Please keep us posted.

-- 
Denys



  reply	other threads:[~2010-04-27  4:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 10:40 dm365 and OE Raffaele Recalcati
2010-04-26 11:22 ` Koen Kooi
2010-04-26 17:44 ` Denys Dmytriyenko
2010-04-27  1:48   ` [arago-devel] " Raffaele Recalcati
2010-04-27  2:57     ` Denys Dmytriyenko [this message]
2010-05-06  6:10       ` Raffaele Recalcati
2010-05-20  3:11         ` Denys Dmytriyenko
2010-05-20 18:55           ` Raffaele Recalcati
2010-04-27  6:42     ` Koen Kooi

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=20100427025702.GC10320@denix.org \
    --to=denis@denix.org \
    --cc=arago-devel@gforge.ti.com \
    --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.