Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jussi Kukkonen <jussi.kukkonen@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] xserver-xorg upgrade
Date: Wed, 20 May 2015 22:09:22 +0300	[thread overview]
Message-ID: <cover.1432147061.git.jussi.kukkonen@intel.com> (raw)

The last commit does three things:
 * removes xf86-video-modesetting recipe
 * upgrades xserver-xorg (which now includes modesetting driver)
 * updates OELAYOUT_ABI (to avoid sanity check freaking out from the
   previous two)
The combination seems logically atomic to me but let me know if I should
divide it into separate commits instead.

Also, I'm not totally familiar with the tmp/sysroots/ layout so would
appreciate advice on the sanity.bbclass changes.

First commit fixes a sanity.bbclass bug that would be triggered by the
actual patch.

I've tested the ABI upgrade to the best of my ability (including wiping
tmp/, building an image from master, then building this branch). 

The following changes since commit 16caaabfcc678b03a0cd88aaeac15f9b8d1c3dad:

  bitbake: bitbake-user-manual-customization.xsl: Pointing to mirrors for XSL files. (2015-05-19 22:09:36 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib jku/xorg
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=jku/xorg

Jussi Kukkonen (2):
  sanity.bbclass: import subprocess in correct function
  xserver-xorg: Upgrade 1.16.3 -> 1.17.1 (OELAYOUT_ABI change)

 meta-yocto/conf/distro/poky.conf                   |   2 +-
 meta/classes/sanity.bbclass                        |  10 +-
 meta/conf/abi_version.conf                         |   2 +-
 .../xorg-driver/xf86-video-modesetting_0.9.0.bb    |   8 --
 .../recipes-graphics/xorg-xserver/xserver-xorg.inc |   9 +-
 ...Check-strings-length-against-request-size.patch | 145 ---------------------
 ...wap-XkbSetGeometry-data-in-the-input-buff.patch | 109 ----------------
 .../Fix-subwindow-in-Xi-emulated-events.patch      |  41 ------
 .../xserver-xorg/xshmfence-option.patch            |  57 --------
 ...erver-xorg_1.16.3.bb => xserver-xorg_1.17.1.bb} |   8 +-
 10 files changed, 19 insertions(+), 372 deletions(-)
 delete mode 100644 meta/recipes-graphics/xorg-driver/xf86-video-modesetting_0.9.0.bb
 delete mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/0001-xkb-Check-strings-length-against-request-size.patch
 delete mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/0001-xkb-Don-t-swap-XkbSetGeometry-data-in-the-input-buff.patch
 delete mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/Fix-subwindow-in-Xi-emulated-events.patch
 delete mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/xshmfence-option.patch
 rename meta/recipes-graphics/xorg-xserver/{xserver-xorg_1.16.3.bb => xserver-xorg_1.17.1.bb} (74%)

-- 
2.1.4



             reply	other threads:[~2015-05-20 19:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 19:09 Jussi Kukkonen [this message]
2015-05-20 19:11 ` [PATCH 1/2] sanity.bbclass: import subprocess in correct function Jussi Kukkonen
2015-05-20 19:11 ` [PATCH 2/2] xserver-xorg: Upgrade 1.16.3 -> 1.17.1 (OELAYOUT_ABI change) Jussi Kukkonen
2015-05-20 19:23   ` Burton, Ross

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=cover.1432147061.git.jussi.kukkonen@intel.com \
    --to=jussi.kukkonen@intel.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox