Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error

[Gene Heskett <gene.heskett _at_ xxxxxxxxxxx>]

On Monday 12 January 2004 00:42, Andrew Morton wrote:
>Gene Heskett <gene.heskett _at_ verizon.net> wrote:
>> However, since I've been running 2.6.1-mm1 here, using the rivafb
>> with an elderly gforce2-mx2 32 megger, I've noted that when
>> running kde-3.1.1a with 8 windows, and a couple of them have
>> multimegabyte backdrops, the biggest one being that famous deep
>> space shot from hubble of about 4 or 5 months back.  In any other
>> kernel, switching to that window took about 12 seconds for the
>> backdrop to be converted to 1600x1200x32 and drawn the first time
>> and about 8 seconds for the next time.  But with this 2.6.1-mm1
>> kernel, that repeat window switch is so close to instant that I
>> cannot see it being drawn.
>>
>>  So as far as I'm concerned, this particular set of fb patches to
>>  rivafb *need* to stay in mainline.  I'd sure appreciate it, a
>> bunch.
>
>There are no significant fbdev patches in 2.6.1-mm1.  There is a DRM
>update.

Whatever it is, its pure speed on this system here, Andrew.  DRM? 
lemme see if thats even turned on.  Nope "# CONFIG_DRM is not set"
Doing a make xconfig, I see that if I turn it on, there is not a 
driver for my gforce2/nvidia, so I naturally turned it back off.

I do have VIA and agpgart enabled just above it, and over in the 
framebuffer menu, support for framebuffer and nvidia/riva are both 
checked.

Anyway, something has made a huge difference in window switching 
speeds here, someplace between 2.6.0-mm2 and 2.6.1-mm1.  I like it.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty: soap,
ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo _at_ vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/