[Prev][Next][Index][Thread]
Re: Mouse with linux SVGAlib (1.3.99 kernel)
>>>>> "Chris" == Chris Dodd <cdodd@super.win.or.jp> writes:
In article <31be94a1.2367014@super.win.or.jp> cdodd@super.win.or.jp (Chris Dodd) writes:
Chris> cdodd@super.win.or.jp (Chris Dodd) wrote:
>> Hi there,
>>
>> Just wondering if the patch mentioned in the faq would make the
>> mouse work in executor-svga, and kernel 1.3.99. The faq writes
>> about 1.2.13, I believe.
>>
>> Perhaps I need a newer SVGAlib? If so, just tell me and I will
>> go check the comp.os.linux.misc.
>>
>> Thanks, Chris
>>
>> Chris Dodd cdodd@super.win.or.jp
>>
>> Passing my senior year at Waseda University in Japan.
Chris> Hello,
Chris> I solved this one myself. If anyone has this problem,
Chris> their config file is probably not complete. Make sure you
Chris> have your mouse specified correctly in it...it was
Chris> defaulting to microsoft for me even though I use a PS/2
Chris> style mouse in kernel, etc. Just set the mouse in the
Chris> config, and it works fine.
Yay. Glad to hear it.
Chris> Also seems faster in svgalib than in X. Or is that just
Chris> me?
Currently E/L/SVGAlib *is* faster than E/L/X, for a few reasons, the
first of which is that E/L/SVGAlib can, on many graphics cards, write
directly to the frame buffer, while the X version has to write to an
ofscreen pixmap and then pass that to the X-server to display. This
means that you have both extra memory copies and extra context
switches with the X version. Additionally, the X server itself takes
up some memory, so on memory starved systems you'll page more if
you're running E/L/X.
Most of this will change when we support the new X optional feature
that allows programs to write directly to the screen. Then, except
for memory starved machines (and at the price of memory, fewer people
will have that problem), the X version will be superior in almost all
ways.
Chris> Chris
Chris> Chris Dodd cdodd@super.win.or.jp
Chris> Passing my senior year at Waseda University in Japan.
--Cliff
ctm@ardi.com
References: