Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Laurentiu Palcu <laurentiu.palcu@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 12/12] xf86-video-omapfb: upgrade to 0.4.2
Date: Wed, 14 Nov 2012 10:44:57 +0100	[thread overview]
Message-ID: <20121114094457.GJ3928@jama.jama.net> (raw)
In-Reply-To: <5467b530a59b1d698e8171b4a7c77104593dde40.1352884713.git.laurentiu.palcu@intel.com>

[-- Attachment #1: Type: text/plain, Size: 3312 bytes --]

On Wed, Nov 14, 2012 at 11:28:09AM +0200, Laurentiu Palcu wrote:
> Other changes:
>  * changed the recipe's SRC_URI to track the new (maintained) repo;
>  * removed all old patches as the latest driver's structure has changed
>    drastically;
>  * license file changed quite a bit: MIT -> GPLv2 (needs to be reviewed
>    by somebody with a better understanding of these things though);
>  * xf86-video-omapfb changed its name to xf86-video-omap: change the
>    recipe name acordingly;
>  * add dependency of libdrm-omap;
> 
> Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
> ---
>  ...-video-omapfb_git.bb => xf86-video-omap_git.bb} |   27 ++++++++++----------
>  1 file changed, 13 insertions(+), 14 deletions(-)
>  rename meta/recipes-graphics/xorg-driver/{xf86-video-omapfb_git.bb => xf86-video-omap_git.bb} (43%)
> 
> diff --git a/meta/recipes-graphics/xorg-driver/xf86-video-omapfb_git.bb b/meta/recipes-graphics/xorg-driver/xf86-video-omap_git.bb
> similarity index 43%
> rename from meta/recipes-graphics/xorg-driver/xf86-video-omapfb_git.bb
> rename to meta/recipes-graphics/xorg-driver/xf86-video-omap_git.bb
> index f16441e..fec3365 100644
> --- a/meta/recipes-graphics/xorg-driver/xf86-video-omapfb_git.bb
> +++ b/meta/recipes-graphics/xorg-driver/xf86-video-omap_git.bb
> @@ -6,19 +6,18 @@ DESCRIPTION = "omapfb driver supports the basic Texas Instruments OMAP \
>  framebuffer."
>  
>  LICENSE = "MIT-X & GPLv2+"
> -LIC_FILES_CHKSUM = "file://COPYING;md5=63e2cbac53863f60e2f43343fb34367f"
> -DEPENDS += "virtual/libx11"
> -
> -SRCREV = "28c006c94e57ea71df11ec4fff79d7ffcfc4860f"
> -PR = "${INC_PR}.6"
> -PV = "0.1.1+gitr${SRCPV}"
> -
> -SRC_URI = "git://git.pingu.fi/xf86-video-omapfb;protocol=http \
> -            file://omap-revert-set-CRTC-limit.patch \
> -            file://omap-revert-set-virtual-size.patch \
> -            file://omap-force-plain-mode.patch  \
> -            file://omap-blacklist-tv-out.patch  \
> -            file://0004-Attempt-to-fix-VRFB.patch \
> +LIC_FILES_CHKSUM = "file://COPYING;md5=10ce5de3b111315ea652a5f74ec0c602"
> +DEPENDS += "virtual/libx11 libdrm-omap"

Ah, now I see why you added them in libdrm PROVIDES, but why not use
libdrm in DEPENDS and libdrm-omap added to RDEPENDS by shlibs?

I also don't see GNUtoo comment resolved.

Cheers,

> +RPROVIDES = "xf86-video-omapfb"
> +RCONFLICTS = "xf86-video-omapfb"
> +RREPLACES = "xf86-video-omapfb"
> +
> +SRCREV = "ae0394e687f1a77e966cf72f895da91840dffb8f"
> +PR = "${INC_PR}.0"
> +PV = "0.4.2+gitr${SRCPV}"
> +
> +SRC_URI = "git://anongit.freedesktop.org/xorg/driver/xf86-video-omap;protocol=git \
>  "
>  
>  S = "${WORKDIR}/git"
> @@ -28,5 +27,5 @@ CFLAGS += " -I${STAGING_INCDIR}/xorg "
>  
>  # Use overlay 2 on omap3 to enable other apps to use overlay 1 (e.g. dmai or omapfbplay)
>  do_compile_prepend_armv7a () {
> -        sed -i -e s:fb1:fb2:g ${S}/src/omapfb-xv.c
> +        sed -i -e s:fb1:fb2:g ${S}/src/omap_xv.c
>  }
> -- 
> 1.7.9.5
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2012-11-14  9:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14  9:27 [PATCH v2 00/12] xorg upgrades Laurentiu Palcu
2012-11-14  9:27 ` [PATCH v2 01/12] xf86-video-vesa: upgrade to 2.3.2 Laurentiu Palcu
2012-11-14  9:27 ` [PATCH v2 02/12] xf86-video-intel: upgrade to 2.20.12 Laurentiu Palcu
2012-11-14  9:28 ` [PATCH v2 03/12] xf86-input-mouse: upgrade to 1.8.1 Laurentiu Palcu
2012-11-14  9:28 ` [PATCH v2 04/12] xkeyboard-config: upgrade to 2.7 Laurentiu Palcu
2012-11-14  9:28 ` [PATCH v2 05/12] xcb-proto: upgrade to 1.8 Laurentiu Palcu
2012-11-14  9:28 ` [PATCH v2 06/12] fontconfig: upgrade to 2.10.1 Laurentiu Palcu
2012-11-14  9:28 ` [PATCH v2 07/12] libdrm: upgrade to 2.4.40 Laurentiu Palcu
2012-11-14  9:39   ` Martin Jansa
2012-11-14  9:28 ` [PATCH v2 08/12] xserver-xorg: upgrade to 1.13.0 Laurentiu Palcu
2012-11-14 11:28   ` Otavio Salvador
2012-11-14 11:44     ` Burton, Ross
2012-11-14  9:28 ` [PATCH v2 09/12] mdadm: upgrade to 3.2.6 Laurentiu Palcu
2012-11-14  9:28 ` [PATCH v2 10/12] xf86-video-vmware: Add compat API Laurentiu Palcu
2012-11-14  9:28 ` [PATCH v2 11/12] xf86-input-synaptics: add mtdev dependency Laurentiu Palcu
2012-11-14  9:28 ` [PATCH v2 12/12] xf86-video-omapfb: upgrade to 0.4.2 Laurentiu Palcu
2012-11-14  9:44   ` Martin Jansa [this message]
2012-11-14 16:28   ` Saul Wold
2012-11-15  7:43     ` Laurentiu Palcu

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=20121114094457.GJ3928@jama.jama.net \
    --to=martin.jansa@gmail.com \
    --cc=laurentiu.palcu@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