All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daiane Angolini <daiane.angolini@freescale.com>
To: Prathamesh P Ghanekar <prathamesh.ghanekar@igate.com>,
	"meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>
Subject: Re: building vivante drivers(so's) compatible with xorg13.0 and above
Date: Wed, 12 Feb 2014 08:52:39 -0200	[thread overview]
Message-ID: <52FB5277.6060204@freescale.com> (raw)
In-Reply-To: <2BC3ECFBDE78594E858F96993713F3F90968ECAD@IGTEMUMMB11.igatecorp.com>

On 12-02-2014 04:32, Prathamesh P Ghanekar wrote:
> Hello everyone,
>
> I am working on freescale i.MX6 SABRE-AUTO board. I am trying to get
> familiar with the board, by making use of the BSP provided by Freescale.
>
> After reading few posts and forums, I came to know that, VIVANTE GPU
> drivers shipped with the BSP do not support Xorg13.0 and above, which I
> intend to use.
>
> Can you please provide any help regarding building the vivante
> drivers(user space) for armv7l using yocto project?
>
> How should I go about this activity?

Please, enter a SR asking what you need to Freescale.
Vivante GPU libraries/user space is released as binary only

>
> P.S. I am not interested in building the entire YOCTO image.

cool

>
> Thanks and regards,
> Prathamesh Ghanekar
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Disclaimer~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Information contained and transmitted by this e-mail is confidential and
> proprietary to iGATE and its affiliates and is intended for use only by
> the recipient. If you are not the intended recipient, you are hereby
> notified that any dissemination, distribution, copying or use of this
> e-mail is strictly prohibited and you are requested to delete this
> e-mail immediately and notify the originator or mailadmin@igate.com
> <mailto:mailadmin@igate.com>. iGATE does not enter into any agreement
> with any party by e-mail. Any views expressed by an individual do not
> necessarily reflect the view of iGATE. iGATE is not responsible for the
> consequences of any actions taken on the basis of information provided,
> through this email. The contents of an attachment to this e-mail may
> contain software viruses, which could damage your own computer system.
> While iGATE has taken every reasonable precaution to minimise this risk,
> we cannot accept liability for any damage which you sustain as a result
> of software viruses. You should carry out your own virus checks before
> opening an attachment. To know more about iGATE please visit
> www.igate.com <http://www.igate.com>.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Please, when sending email to a mailing list, do not include disclaimer. 
Now my reply is proprietary to iGATE :(

>
>
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>


-- 
Daiane



  reply	other threads:[~2014-02-12 10:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12  6:32 building vivante drivers(so's) compatible with xorg13.0 and above Prathamesh P Ghanekar
2014-02-12 10:52 ` Daiane Angolini [this message]
2014-02-12 11:05 ` Otavio Salvador

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=52FB5277.6060204@freescale.com \
    --to=daiane.angolini@freescale.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=prathamesh.ghanekar@igate.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.