All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <darren.hart@intel.com>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [PATCH 1/5] xf86-video-intel: Bring 2.20.0 version to match released graphics stack
Date: Tue, 09 Oct 2012 16:03:08 -0700	[thread overview]
Message-ID: <5074AD2C.4000007@intel.com> (raw)
In-Reply-To: <ADD6A3980E8C39419A432FF422031B4C15730EF4@ORSMSX106.amr.corp.intel.com>

CC'ing Ross, which of course I had meant to do in the first place...

On 10/09/2012 04:01 PM, Kamble, Nitin A wrote:
> 
>>> --- /dev/null
>>> +++ b/common/recipes-graphics/xorg-driver/xf86-video-intel_2.20.0.bb
>>> @@ -0,0 +1,26 @@
>>> +require xorg-driver-video.inc
>>> +
>>> +SUMMARY = "X.Org X server -- Intel integrated graphics chipsets driver"
>>> +
>>> +DESCRIPTION = "intel is an Xorg driver for Intel integrated graphics
>>> +\ chipsets. The driver supports depths 8, 15, 16 and 24. On some
>>> +chipsets, \ the driver supports hardware accelerated 3D via the
>>> +Direct Rendering \ Infrastructure (DRI)."
>>> +
>>> +LIC_FILES_CHKSUM =
>> "file://COPYING;md5=8730ad58d11c7bbad9a7066d69f7808e"
>>> +
>>> +PR = "${INC_PR}.0"
>>> +
>>> +DEPENDS += "virtual/libx11 drm xf86driproto glproto \
>>> +	    virtual/libgl xineramaproto xf86driproto libpciaccess"
>>> +
>>> +
>>> +EXTRA_OECONF += "--disable-xvmc"
>>
>> I think Ross's version enables xvmc. Any reason to disable it?
> 
> I basically took the recipe from oecore, and updated to the desired version. That way it is very close to what is in oecore, and all the testing of oecore is on our side.
> 
>>
>> Is the new method to use PACKAGECONF instead of EXTRA_OECONF now?
>> Again, this is what I saw in Ross's layer.
>>
> Not sure, I will see the differences with Ross's recipe, and test it out here.
> 
> Thanks,
> Nitin
> 
> 
>> --
>> Darren Hart
>> Intel Open Source Technology Center
>> Yocto Project - Linux Kernel
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
> 

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


  reply	other threads:[~2012-10-09 23:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09 22:10 [PATCH 0/5] Misc meta-intel commits nitin.a.kamble
2012-10-09 22:10 ` [PATCH 1/5] xf86-video-intel: Bring 2.20.0 version to match released graphics stack nitin.a.kamble
2012-10-09 22:40   ` Darren Hart
2012-10-09 23:01     ` Kamble, Nitin A
2012-10-09 23:03       ` Darren Hart [this message]
2012-10-09 22:10 ` [PATCH 2/5] crownbay.conf: specify the 8.0.4 version as preferred version of mesa-dri nitin.a.kamble
2012-10-09 22:41   ` Darren Hart
2012-10-10  9:24   ` Burton, Ross
2012-10-10 23:10     ` Kamble, Nitin A
2012-10-11 16:53       ` Burton, Ross
2012-10-11 23:39         ` Kamble, Nitin A
2012-10-12  3:55           ` Ross Burton
2012-10-09 22:10 ` [PATCH 3/5] emgd-driver_bin_1.10: drop it as all BSP using EMGD have switched to 1.14 version now nitin.a.kamble
2012-10-09 22:44   ` Darren Hart
2012-10-09 22:10 ` [PATCH 4/5] fishriver BSP retirement nitin.a.kamble
2012-10-09 22:45   ` Darren Hart
2012-10-09 22:10 ` [PATCH 5/5] update maintainers of various BSPs nitin.a.kamble

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=5074AD2C.4000007@intel.com \
    --to=darren.hart@intel.com \
    --cc=nitin.a.kamble@intel.com \
    --cc=yocto@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.