Re: 3.3 kernel from TI landing teams and powervr problems.

On Tue, Apr 17, 2012 at 2:52 AM, Martin Ertsås wrote: > Thanks to this, I got x running, problem is that I don't seem to have > direct rendering. First it complained that glx could not be loaded. When > adding the glx extensions from the xserver, I get some problems with > AIGLX. It sais that /usr

Re: 3.3 kernel from TI landing teams and powervr problems.

On 04/17/12 10:50, Dechesne, Nicolas wrote: > > > On Tue, Apr 17, 2012 at 9:52 AM, Martin Ertsås > wrote: > > > Searched through the xf86-video-omap, and doesn't seem to build > anything > but omap_drv.so, but it do contain a file omap_dri2.c. Should I >

Re: 3.3 kernel from TI landing teams and powervr problems.

On Tue, Apr 17, 2012 at 9:52 AM, Martin Ertsås wrote: > > Searched through the xf86-video-omap, and doesn't seem to build anything > but omap_drv.so, but it do contain a file omap_dri2.c. Should I let the > glx warning appear, and just ignore it maybe? Do the driver provide dri2 > by itself? > >

Re: 3.3 kernel from TI landing teams and powervr problems.

Thanks to this, I got x running, problem is that I don't seem to have direct rendering. First it complained that glx could not be loaded. When adding the glx extensions from the xserver, I get some problems with AIGLX. It sais that /usr/lib/dri/omap_dri.so could not be found. Is this something I sh

Re: 3.3 kernel from TI landing teams and powervr problems.

On 04/17/12 01:17, Clark, Rob wrote: On Mon, Apr 16, 2012 at 10:07 AM, Martin Ertsås wrote: True, I renamed that file, since I got the message that it couldn't find module omap. First I renamed it to omap_drv.so, which gave me the same error, then I tried pvr_drm.so which is the attatched logfi

Re: 3.3 kernel from TI landing teams and powervr problems.

On Mon, Apr 16, 2012 at 10:07 AM, Martin Ertsås wrote: > > True, I renamed that file, since I got the message that it couldn't find > module omap. First I renamed it to omap_drv.so, which gave me the same > error, then I tried pvr_drm.so which is the attatched logfile. Both of them > are the omap_

Re: 3.3 kernel from TI landing teams and powervr problems.

True, I renamed that file, since I got the message that it couldn't find module omap. First I renamed it to omap_drv.so, which gave me the same error, then I tried pvr_drm.so which is the attatched logfile. Both of them are the omap_pvr_drv.so file. Should there be a omap_drv.so file in the sa

Re: 3.3 kernel from TI landing teams and powervr problems.

There is an omap_drv.so which should be the xorg driver to load.. it will attempt to load (if present) omap_pvr_drv.so as a submodule for EXA accel. I'm not entirely sure why it is named pvr_drv.so in your filesystem, but from list of symbols it seems to match what I would expect to be omap_pvr_dr