From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe003.messaging.microsoft.com [213.199.154.206]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 9F519E0146D for ; Mon, 15 Apr 2013 09:42:47 -0700 (PDT) Received: from mail34-am1-R.bigfish.com (10.3.201.244) by AM1EHSOBE015.bigfish.com (10.3.207.137) with Microsoft SMTP Server id 14.1.225.23; Mon, 15 Apr 2013 16:42:46 +0000 Received: from mail34-am1 (localhost [127.0.0.1]) by mail34-am1-R.bigfish.com (Postfix) with ESMTP id 0288D602F5; Mon, 15 Apr 2013 16:42:46 +0000 (UTC) X-Forefront-Antispam-Report: CIP:70.37.183.190; KIP:(null); UIP:(null); IPV:NLI; H:mail.freescale.net; RD:none; EFVD:NLI X-SpamScore: -4 X-BigFish: VS-4(zzbb2dI98dI9371I1432Izz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz8275bhz2dh2a8h668h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h18e1h190ch1946h19b4h19c3h1ad9h1b0ah1155h) Received: from mail34-am1 (localhost.localdomain [127.0.0.1]) by mail34-am1 (MessageSwitch) id 1366044136140409_15555; Mon, 15 Apr 2013 16:42:16 +0000 (UTC) Received: from AM1EHSMHS014.bigfish.com (unknown [10.3.201.254]) by mail34-am1.bigfish.com (Postfix) with ESMTP id 2025D4605E2; Mon, 15 Apr 2013 16:42:16 +0000 (UTC) Received: from mail.freescale.net (70.37.183.190) by AM1EHSMHS014.bigfish.com (10.3.207.152) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 15 Apr 2013 16:42:11 +0000 Received: from az84smr01.freescale.net (10.64.34.197) by 039-SN1MMR1-002.039d.mgd.msft.net (10.84.1.15) with Microsoft SMTP Server (TLS) id 14.2.328.11; Mon, 15 Apr 2013 16:42:09 +0000 Received: from [10.29.244.97] ([10.29.244.97]) by az84smr01.freescale.net (8.14.3/8.14.0) with ESMTP id r3FGg8Sc012089; Mon, 15 Apr 2013 09:42:08 -0700 Message-ID: <516C2DB2.7050607@freescale.com> Date: Mon, 15 Apr 2013 13:41:22 -0300 From: Daiane Angolini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 MIME-Version: 1.0 To: Otavio Salvador References: <1366026722-31385-1-git-send-email-otavio@ossystems.com.br> <1366026722-31385-13-git-send-email-otavio@ossystems.com.br> <516C1D2C.8030005@freescale.com> In-Reply-To: X-OriginatorOrg: freescale.com Cc: meta-freescale Mailing List Subject: Re: [meta-fsl-arm PATCH v3 12/13] xf86-dri-vivante: Fix DRI module name X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Apr 2013 16:42:48 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 04/15/2013 01:15 PM, Otavio Salvador wrote: > On Mon, Apr 15, 2013 at 12:30 PM, Daiane Angolini > wrote: >> On 04/15/2013 08:52 AM, Otavio Salvador wrote: >>> >>> The Xorg Vivante driver has a hardcoded module name as 'vivante_dri' >>> so we need to rename it for full Xorg acceleration to work. >>> >>> Signed-off-by: Otavio Salvador >>> --- >>> Changes in v3: None >>> Changes in v2: None >>> >>> recipes-graphics/xorg-driver/xf86-dri-vivante_1.1.0.bb | 4 ++++ >>> 1 file changed, 4 insertions(+) >>> >>> diff --git a/recipes-graphics/xorg-driver/xf86-dri-vivante_1.1.0.bb >>> b/recipes-graphics/xorg-driver/xf86-dri-vivante_1.1.0.bb >>> index 975041d..6e8f8db 100644 >>> --- a/recipes-graphics/xorg-driver/xf86-dri-vivante_1.1.0.bb >>> +++ b/recipes-graphics/xorg-driver/xf86-dri-vivante_1.1.0.bb >>> @@ -30,6 +30,10 @@ do_install_append () { >>> >>> # FIXME: don't install libtool (*.la) file >>> rm ${D}${libdir}/xorg/modules/extensions/*.la >>> + >>> + # FIXME: The Xorg driver has a hardcoded library name >>> + mv ${D}${libdir}/xorg/modules/extensions/libdri.so \ >>> + ${D}${libdir}/xorg/modules/extensions/libvivante_dri.so >> >> >> I think you can use a symbolic link instead (as someone else has already >> pointed before in the ML). > > This makes it harder to have regular libdri.so packaged in same rootfs > in future. With the support for multiple CPUs in a single kernel (as > done in mainline) this should be started to be considered. I got that. Agreed Daiane