From: Thomas Senyk <thomas.senyk@pelagicore.com>
To: "Ahsan, Noor" <Noor_Ahsan@mentor.com>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
"Potnis, Abhijit" <Abhijit_Potnis@mentor.com>
Subject: Re: wayland enabled gpu-viv
Date: Wed, 10 Jul 2013 12:38:33 +0200 [thread overview]
Message-ID: <4227229.FU8GTJhYOQ@rudolf> (raw)
In-Reply-To: <365E1805BC95084CBE82381A0B869994DE4D4969@EU-MBX-01.mgc.mentorg.com>
On Wednesday, 10 July, 2013 9:28:06 Ahsan, Noor wrote:
> So you have modified same gpu-viv recipe that is available in meta-fal-arm
> or created the new one. I am interested to know couple of things here.
> First is why gpu-viv recipe is removing wayland specific things. See
> following
>
> # FIXME: Remove Wayland contents
> rm -r ${D}${includedir}/wayland-viv
> find ${D}${libdir} -name '*-wl.so' -exec rm '{}' ';'
> rm ${D}${libdir}/*wayland*.so*
>
> so it looks that we can't add wayland stuff in the same recipe or I am
> interpreting something wrong here. Can't we add wayland stuff in the same
> recipe just like we have other stuff for x11 and directfb.
I agree, we should have everything in one recipe.
My best guess why someone removes it: He didn't know what else to do with it,
and then it's good practice to remove 'unless stufff' within recipes.
So solving the 'FIXME' would mean: remove all the 'rm' and move them
accordingly (remove them only if wayland is not in DISTRO_FEATURES and deploy
them otherwise)
> Secondly I see
> gpu-viv-bin-mx6q-3.0.035-4.0.0.bin and gpu-viv-wl-bin-mx6q-3.0.35-4.0.0.bin
> at http://download.ossystems.com.br/bsp/freescale/source/. I compared both
> bin file contents are same so why we have separated it out.
No clue. Anyone from freescale a comment?
>
> Noor
>
> -----Original Message-----
> From: Thomas Senyk [mailto:thomas.senyk@pelagicore.com]
> Sent: Wednesday, July 10, 2013 2:15 PM
> To: meta-freescale@yoctoproject.org
> Cc: Ahsan, Noor; Potnis, Abhijit
> Subject: Re: [meta-freescale] wayland enabled gpu-viv
>
> On Wednesday, 10 July, 2013 7:16:29 Ahsan, Noor wrote:
> > Hello,
> >
> > We are working on wayland support on saberlite. I saw that
> > meta-fsl-arm layer does not have wayland enabled gpu-viv recipes. May
> > I know what is the plan regarding that?
>
> I'm currently overloaded with my imx6-vpu work, but in general I would be
> interested in this as well.
>
> What's already there:
> - The drivers releases already include the wayland part
> - If one enables wayland as DISTRO_FEATURE and/or installs it, the protocol
> part is also done.
>
> What's missing:
> - within the gpu recipe:
> the same code existing for x, fb and dfb needs to be added for wayland.
> - this will include:
> pkgconfig files: wayland-egl.pc (which is likely to be a copy of egl.pc)
> ... most likely more then that but I can't recall what else is missing.
>
>
> So far I've only done this 'manually' by fiddling around with the sysroot
> and rootfs ... I hadn't had the time to test a proper recipe way of
> creating everything. Anyway If you need help, let me know.
>
> > Noor
> >
> > Noor Ahsan | Engineering Manager Mentor Embedded Linux Mentor
> > Embedded<http://www.mentor.com/embedded>(tm) |5-6-7-8th floors 105
> > B2 Gulberg III, Ali Tower MM Alam Road, Lahore P +92 42 36099196 | M
> > +92 300 4448444
> > Nucleus<http://www.mentor.com/embedded-software/nucleus/>(r) |
> > Linux<http://www.mentor.com/embedded-software/linux/>(r) |
> > Android<http://www.mentor.com/embedded-software/android/>(tm) |
> > Services<http://www.mentor.com/embedded-software/services/> |
> > UI<http://www.mentor.com/embedded-software/inflexion/> |
> > Multi-OS<http://www.mentor.com/embedded-software/multicore-multi-os>
> >
> > Android is a trademark of Google Inc. Use of this trademark is subject
> > to Google Permissions. Linux is the registered trademark of Linus
> > Torvalds in the U.S. and other countries.
prev parent reply other threads:[~2013-07-10 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 7:16 wayland enabled gpu-viv Ahsan, Noor
2013-07-10 9:14 ` Thomas Senyk
2013-07-10 9:28 ` Ahsan, Noor
2013-07-10 10:38 ` Thomas Senyk [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=4227229.FU8GTJhYOQ@rudolf \
--to=thomas.senyk@pelagicore.com \
--cc=Abhijit_Potnis@mentor.com \
--cc=Noor_Ahsan@mentor.com \
--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.