From: Denys Dmytriyenko <denis@denix.org>
To: arago-devel@gforge.ti.com
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [arago-devel] dm365 and OE
Date: Wed, 19 May 2010 23:11:42 -0400 [thread overview]
Message-ID: <20100520031142.GD25484@denix.org> (raw)
In-Reply-To: <t2gade1bdc1005052310je365713at72a3997b449e46a1@mail.gmail.com>
On Thu, May 06, 2010 at 08:10:42AM +0200, Raffaele Recalcati wrote:
> 2010/4/27 Denys Dmytriyenko <denis@denix.org>
>
> >
> > 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.
> >
>
> The ping is going on?
>
> I have unzipped the dvsdk and tried to associate it to arago/OE recipes, but
> what is the corrispondence?
>
> Doing an 'ls -1' in my dvsdk dir I obtain:
> bin
> bios_5_41_00_06
> biosutils_1_02_02
> codec_engine_2_25_01_06
> dm365_codecs_01_00_06
> dm365mm_01_00_03
> dmai_2_10_00_06
> docs
> dsplink_linux_1_64
> DVSDK_3_10_00_12_release_notes.html
> dvsdk_demos_3_10_00_10
> dvtb_4_20_02
> edma3_lld_01_11_00_03
> examples
> framework_components_2_25_01_05
> linux_dvsdk_3_10_beta_manifest.pdf
> linuxutils_2_25_01_06
> Makefile
> mapdmaq
> mapdmaq-hd
> Rules.make
> uninstall
> xdais_6_25_01_08
> xdctools_3_16_01_27
>
> I guess that each directory has to become a tgz in this dir and from
> localhost I need to reach it (using a link from /var/www to this dir):
>
> But:
>
> arago/recipes/ti/ti-codecs-dm365_3.10.00.02.bb
> uses
>
> PV = "03_10_00_02"
> BASE_SRC_URI = "http://install.source.dir.local"
> SRC_URI = "${BASE_SRC_URI}/dm365_codecs_${PV}.tar.gz;name=dm365codecs \
> file://mapdmaq"
>
> but in my dvsdk I have
> dm365_codecs_01_00_06
> and so ${PV} seems wrong.
>
> ${PV} is similar, but not equal, to dvsdk version, 3_10_00_02 versus
> 3_10_00_12.
>
> ----------------
> ti-dmai points to svn, instead in dvsdk I have dmai_2_10_00_06 .
> -----------------
>
> I could rebuild from dvsdk 3_10_00_12 sources using arago or not, but,
> first, I'd like some check if it is the good starting point.
Sorry for the mess - this is still not resolved the way we had hoped. While
the combined DVSDK is now available in beta, some of the individual
components, like codecs, are still not available for download separately.
Looks like we may need to write a recipe to extract necessary pieces from
DVSDK release... Please be patient, hopefully we'll have the solution soon.
--
Denys
next prev parent reply other threads:[~2010-05-20 3:16 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
2010-05-06 6:10 ` Raffaele Recalcati
2010-05-20 3:11 ` Denys Dmytriyenko [this message]
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=20100520031142.GD25484@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.