Heya Kdrive people,
Here is a small one line startup/server regeneration
related bug fix in the mouse handling code that I
think should be added into
xc/programs/Xserver/hw/kdrive/linux/mouse.c
@@ -941,6 +941,7 @@
mi->driver = km;
km->iob.fd = fd;
km->iob.avail = km->iob.used = 0;
+ km->prot = NULL;
MouseFirstProtocol (km, mi->prot);
if (KdRegisterFd (MouseInputType, fd,
MouseRead, (void *) mi))
n++;
To stimulate the bug, Try running "xhost +" on a
kdrive server Xfbdev or Xvesa when it is not running
any clients and you should get a SEG Fault.
Who looks after, vetting and applying fixes to the
Kdrive parts of the tree. Keith? or maybe Juliusz?. Is
there a link to help people with fixes find people
with the power and responsibility to submit to cvs.
Or should I and others like me continue to post them
to this list?
PS I am trying to get the kdrive accelerated driver
to work on an pc-chips based motherboard. It uses
a VIA Technologies, Inc. VT8501 and lspci -V reports
the type of trident chip is a Trident Microsystems
CyberBlade/i7 (rev 5b) .... device 7000.... I have
got it to at least start up after allowing
tridentstub.c to look for the pci id, and telling
vm86.c to allow reads and writes from rom between
c0000 and fffff since this motherboard/bios has int10
pointing much higher than what seems to be the
standard.
The cursor seems a little dark, and so I will be
looking into that shortly.
I would be interested to hear from anyone who is
playing around with the trident driver for kdrive.
anyhow, having some fun,
Mike Wake.
__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
