[meta-freescale] [meta-fsl-arm][PATCH 0/2] Fixes for current state of 1.4

Gary Thomas samoht.yrag at gmail.com
Wed Dec 19 07:52:48 PST 2012


On 2012-12-19 08:35, Otavio Salvador wrote:
> On Wed, Dec 19, 2012 at 1:22 PM, Gary Thomas <samoht.yrag at gmail.com> wrote:
> ...
>> Thanks, I'm now using the yoctoproject.org repository and can see the
>> recent changes.
>>
>> Sadly though, I can't build X11 drivers - full log attached.
>> | In file included from ./vivante_util/vivante_common.h:69:0,
>> |                  from vivante_fbdev/vivante_fbdev_driver.c:23:
>> |
>> /home/local/imx6_poky/tmp/sysroots/sabrelite/usr/include/xorg/fbdevhw.h:50:23:
>> note: declared here
>> | vivante_fbdev/vivante_fbdev_driver.c:780:26: warning: assignment from
>> incompatible pointer type [enabled by default]
>> | vivante_fbdev/vivante_fbdev_driver.c: In function 'VivCloseScreen':
>> | vivante_fbdev/vivante_fbdev_driver.c:826:5: warning: passing argument 1 of
>> 'pScreen->CloseScreen' makes pointer from integer without a cast [enabled by
>> default]
>> | vivante_fbdev/vivante_fbdev_driver.c:826:5: note: expected 'ScreenPtr' but
>> argument is of type 'int'
>> | vivante_fbdev/vivante_fbdev_driver.c:826:5: error: too many arguments to
>> function 'pScreen->CloseScreen'
>> | make[2]: *** [vivante_fbdev_driver.lo] Error 1
>> | make[2]: *** Waiting for unfinished jobs....
>> | make[2]: Leaving directory
>> `/home/local/imx6_poky/tmp/work/sabrelite-amltd-linux-gnueabi/xf86-video-imxfb-vivante/2_12.09.01-r20.1/xserver-xorg-video-imx-viv-12.09.01/src'
>> | make[1]: *** [all-recursive] Error 1
>> | make[1]: Leaving directory
>> `/home/local/imx6_poky/tmp/work/sabrelite-amltd-linux-gnueabi/xf86-video-imxfb-vivante/2_12.09.01-r20.1/xserver-xorg-video-imx-viv-12.09.01'
>>
>> Any ideas?  Maybe I've missed something else.
>>
>
> It seems xf86 api changes; you need to check the change in API and
> prepare a patch to the driver ... otherwise I can do it ...

OK, I'll look at this.  I had expected this to already work, based on
the earlier comments, but no problem.




More information about the meta-freescale mailing list