On Tue, Oct 29, 2013 at 05:36:43PM +0100, Gilles Cafedjian wrote:
> I have the same problem but on a dell laptop with integrated NVidia
> chip. 
> The chip is NVidia Geforce 8600M GS and since I upgraded to 5.4 my
> laptop is 
> unusable (very slow window movement). I'm thinking of reinstall 5.3 to
> have a 
> working laptop. I can't change GPU chipset. 
> There is a solution to get a working window manager back? 

If the VESA BIOS on you machine supports the native resolution of the
panel, then running the vesa driver is probably faster than the nv
driver. 

Otherwise, if some people with development skills want to help, I can
see 3 different projects there, with different levels of complexity
and interest (I currently miss time to work on these issues.):

project 1 - relatively easy 
get yourself familiar with the shadowfb implementation in the vesa
driver and then fix it in xf86-video-nv. xf86-video-nv's shadowfb is
currently disabled because it crashes the driver. This would probably
bring most of the speed back for a relatively low effort.

project 2 - a bit harder
get yourself familiar with the EXA acceleration framework, and port
the current XAA code in xf86-video-nv to EXA. Bitblt operations should
give you a reasonable speed-up back on supported cards. But the XAA
code is full of magic numbers (no docs, remember) and since EXA is
probably also going to get dropped by X.Org in the future, this is
probably not the best choice, but it's still interesting to learn
about 2D acceleration in X.Org drivers.

project 3 - hard
dive into the world of DRI and TTM and port the nouveau kernel
driver(s) to OpenBSD. Thanks to jsg@ and kettenis@, OpenBSD has now a
Linux kernel kernel 3.8 compatible version of the dri infrastructure
(including TTM) for intel and radon chipsets. Getting the
corresponding nouveau code is thus possible. This is a multi-months
project but it's an exciting one and it will provide the most benefit
for people forced to use nVidia cards, and for the project in general
since having more people hacking in the dri code is also good for the
other drivers.
-- 
Matthieu Herrb

Reply via email to