From: Denys Dmytriyenko <denis@denix.org>
To: "Monk, Roger" <r-monk@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>,
"Dmytriyenko, Denys" <denys@ti.com>
Subject: Re: [PATCH] omapfbplay: import from OE classic
Date: Mon, 21 May 2012 16:47:17 -0400 [thread overview]
Message-ID: <20120521204717.GA13482@denix.org> (raw)
In-Reply-To: <4C82F39BABFE6A429733A300DEBF52240B75598B@DNCE05.ent.ti.com>
On Thu, May 10, 2012 at 02:23:35PM +0000, Monk, Roger wrote:
> On Thu, May 10, 2012 at 15:20:31, Koen Kooi wrote:
> > Subject: Re: [meta-ti] [PATCH] omapfbplay: import from OE classic
> >
> >
> > Op 10 mei 2012, om 16:13 heeft Monk, Roger het volgende geschreven:
> >
> > > On Thu, May 10, 2012 at 15:09:36, Koen Kooi wrote:
> > >> Subject: Re: [meta-ti] [PATCH] omapfbplay: import from OE classic
> > >>
> > >>
> > >> Op 10 mei 2012, om 15:42 heeft Monk, Roger het volgende geschreven:
> > >>
> > >>> Hi Koen,
> > >>>
> > >>> Think we've still got some API incompatibility here. I needed to
> > >> roll
> > >>> back to an earlier omapfbplay commit
> > >>> (34293052c5a2ae328eac6903512e6b4ce19b5639) and patch CODEC_TYPE :-
> > >>>
> > >>> - if (afc->streams[i]->codec->codec_type == CODEC_TYPE_VIDEO
> > >> && !st)
> > >>> + if (afc->streams[i]->codec->codec_type ==
> > >>> + AVMEDIA_TYPE_VIDEO && !st)
> > >>>
> > >>> to get this working on beagleboard-xm, so I suspect there may have
> > >> been an API change after Aug11, or
> > >> d03f042ecac0a231bedeadc7a6c67f0102d5505a was rebased against 0.8
> > >> branch? I guess we should ask Mans...
> > >>
> > >> We still use libav 0.7.4 in meta-oe, I suspect Mans updated to
> > >> 0.8.x or even newer. I only build tested it, so I'm open for fixes
> > >> that make it run :) Upgrading libav might be an option as well, but
> > >> I'm not sure of that will get accepted for the meta-oe release branch.
> > >
> > > See attached for now - probably ok as reasonable known working
> > baseline before we upgrade other bits?
> >
> > The patch looks good to me. Once the beaglebone a6 release it out I'll
> > have time to look at libav. I'll need it for a customer project in
> > that timeframe as well. Thanks for updating the patch!
>
> Np! - you gave me great head-start! - I'll re-send via git send-email.
BTW, do we want to have PROVIDES and PREFERRED_PROVIDER for all those
different variants of omapfbplay?
--
Denys
prev parent reply other threads:[~2012-05-21 20:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 12:04 [PATCH] omapfbplay: import from OE classic Koen Kooi
2012-05-10 13:42 ` Monk, Roger
2012-05-10 14:09 ` Koen Kooi
2012-05-10 14:13 ` Monk, Roger
2012-05-10 14:20 ` Koen Kooi
2012-05-10 14:23 ` Monk, Roger
2012-05-21 20:47 ` 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=20120521204717.GA13482@denix.org \
--to=denis@denix.org \
--cc=denys@ti.com \
--cc=meta-ti@yoctoproject.org \
--cc=r-monk@ti.com \
/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.