From: "Jose Mª Ferreiro" <jose.ferreiro@horus.es>
To: meta-freescale@yoctoproject.org
Subject: Re: Gstreamer problem with mfw_isink
Date: Fri, 27 Sep 2013 19:40:07 +0200 [thread overview]
Message-ID: <5245C2F7.5000206@horus.es> (raw)
In-Reply-To: <2BC32295742BF14CA5950C3659567EB6779986@039-SN1MPN1-003.039d.mgd.msft.net>
Hello Lauren
I will never know. At noon we decided to do a ./repo sync (three weeks
from last). Now the isink.imx is included.
When I try to look at autoconfigure work, I find references to
linux/mxcfb.h and the sink compiled.
Thanks any way,
Jose
PD: a full family of pinguins is also included into the update
El 27/09/2013 17:22, Post Lauren-RAA013 escribió:
> Gst plugin for Isink needs access to mxc_fb.h. If gstreamer during autoconfigure state does not find this which has resided in the kernel/include/linux directory than it will auto configure it out of the build. Need to add includes in gst-fsl-plugin to the path where mxc_fb.h resides.
>
> -----Original Message-----
> From: meta-freescale-bounces@yoctoproject.org [mailto:meta-freescale-bounces@yoctoproject.org] On Behalf Of Jose Mª Ferreiro
> Sent: Friday, September 27, 2013 9:46 AM
> To: meta-freescale@yoctoproject.org
> Subject: Re: [meta-freescale] Gstreamer problem with mfw_isink
>
>
>
> El 27/09/2013 14:30, Daiane Angolini escribió:
>> On 09/27/2013 06:28 AM, diego wrote:
>>> El 27/09/2013 9:16, diego escribió:
>>>> Hello,
>>>>
>>>> Yesterday I just wrote here:
>>>> https://community.freescale.com/docs/DOC-93788, explaining this:
>>>> ....
>>>> WARNING: erroneous pipeline: no element "mfw_isink"
>>>>
>>>> So if I inspect (gst-inspect | grep "isink"), you'll see this
>>>> element is not installed:
>>>>
>>>> ...
>>>> How can I add it ?
>>>> **
>>>> Regards,
>>>>
>>>> Diego González
>>> Hello everybody,
>>>
>>> I didn't specified my branch and hardware in the last e-mail, but
>>> we're usingdylan branch for iMX6Q SabreLite board.
>>>
>>> We discovered that gst-fsl-plugin is not including the sink in the
>>> next directory :
>>> ~/build/tmp/work/imx6qsabrelite-poky-linux-gnueabi/gst-fsl-plugin/3.0
>>> .5-r9.3/gst-fsl-plugins-3.0.5/src/misc/
>>>
>>>
>>> The v4lsink folder is compiled , however isink folderis not compiled.
>>>
>>> Any clues how to add it?
>>
>> I almost remember that this is a known issue and the fix was not
>> backported to dylan.
>>
>> In other words, it's already fixed on master, but was not backported
>> to dylan
>>
>> Would you mind to test using master?
>>
>>
>>
> Hello Daiane
>
> No problem at all. We already were testing master for another reason but we were not yet able to compile it with linux-fslc (we post another message before). We will try with linux-boundary and I will test this there.
>
> Just now we were testing if dylan+linux-fslc change something but the result is terrible. We lost our hdmi video output and network does not start neither. Trying menuconfig at linux-fslc I can see that Graphics support options are very different from linux-boundary graph options. We were starting to fear that linux.fslc has no very good support for our iMX6Q Sabre Lite. Can it be possible? Or it is more possible we have a problem with our yocto configuration?
>
> Thank you very much,
> Jose
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
>
next prev parent reply other threads:[~2013-09-27 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 7:16 Gstreamer problem with mfw_isink diego
2013-09-27 9:28 ` diego
2013-09-27 12:30 ` Daiane Angolini
2013-09-27 14:46 ` Jose Mª Ferreiro
2013-09-27 15:22 ` Post Lauren-RAA013
2013-09-27 17:40 ` Jose Mª Ferreiro [this message]
2013-09-27 15:39 ` Daiane Angolini
2013-09-27 17:39 ` Jose Mª Ferreiro
-- strict thread matches above, loose matches on Subject: below --
2013-09-27 7:13 diego
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=5245C2F7.5000206@horus.es \
--to=jose.ferreiro@horus.es \
--cc=meta-freescale@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.