[OE-core] [PATCH v3 12/12] xf86-video-omap: add new recipe to follow the maintained repo

[Martin Jansa]

On Thu, Nov 22, 2012 at 1:34 PM, Nicolas Dechesne <ndec13 at gmail.com> wrote:
> On Thu, Nov 22, 2012 at 9:59 AM, Laurentiu Palcu
> <laurentiu.palcu at intel.com> wrote:
>>
>> The autobuilder nightly for arm (for example) does, among other things,
>> the following:
>> * Builds core-image-sato, core-image-sato-dev, core-image-sato-sdk,
>> core-image-minimal, core-image-minimal-dev for qemuarm
>> * Builds core-image-sato, core-image-sato-sdk, core-image-minimal for
>> beagleboard
>> * Builds the meta-toolchain-gmae
>>
>> Here's a link to one of the latest arm nightly builds. You can see that,
>> for beagleboard, it includes xf86-video-omap driver:
>>
>> http://autobuilder.yoctoproject.org:8010/builders/nightly-arm/builds/727
>>
>> This is the production autobuilder. The autobuilder server I used to
>> test the patches is internal and cannot be accessed from outside.
>
>
> and we can see that the build failed with
>
> | checking for ANSI C header files... (cached) yes
> | checking whether to include DRI support... checking for
> /usr/include/xorg/dri.h... configure: error: cannot check for file
> existence when cross compiling
> | Configure failed. The contents of all config.log files follows to
> aid debugging
> | /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/xf86-video-omap/2_0.4.2+gitr1+ae0394e687f1a77e966cf72f895da91840dffb8f-r20.0/git/config.log
> | This file contains any messages produced by compilers while
> | running configure, to aid debugging if configure makes a mistake.
> |
> | It was created by xf86-video-omap configure 0.4.2, which was
> | generated by GNU Autoconf 2.69.  Invocation command line was
>
> from http://autobuilder.yoctoproject.org:8010/builders/nightly-arm/builds/727/steps/shell_55/logs/stdio
>
> I am looking at Ross patch, as our configure.ac file is clearly wrong
> here in xf86-video-omap (in fact most of the testing for this X11
> driver was done in ubuntu, so using native compilation...). will make
> sure to get that fixed upstream asap.

Ross's patch fixes the build issue, but then xf86-video-omap does not
work in runtime (at least on nokia900)

[   275.922] (II) Module omap: vendor="X.Org Foundation"
[   275.922]    compiled for 1.13.0, module version = 0.83.0
[   275.922]    Module class: X.Org Video Driver
[   275.922]    ABI class: X.Org Video Driver, version 13.0
[   275.924] (II) OMAP: Driver for TI OMAP: OMAP3430 with PowerVR SGX530,
        OMAP3630 with PowerVR SGX530, OMAP4430 with PowerVR SGX540,
        OMAP4460 with PowerVR SGX540, OMAP5430 with PowerVR SGX544 MP,
        OMAP5432 with PowerVR SGX544 MP
[   275.925] (--) using VT number 2

[   275.944] (WW) Falling back to old probe method for omap
[   276.469] (EE) No devices detected.

Well that's probably the same issue GNUtoo reported on xf86-video-omap
patch, before it was merged and xf86-video-omapfb removed..

Pity that bits of red in autobuilder logs are the most important
quality indicator for some people...

Cheers,