Around 10 o'clock on Nov 22, Michael Wake wrote:
> 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 Thanks. It's in XFree86 CVS. > Who looks after, vetting and applying fixes to the > Kdrive parts of the tree. Keith? or maybe Juliusz?. You can send them to me, or you can send them to the usual bug address for XFree86. > Or should I and others like me continue to post them > to this list? Given the small number of people using the server, I think its important to get the information out to those who might be affected via this list. If the volume ever starts to be significant, we could consider creating a separate list, but I'd rather avoid that. > 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. I'd be surprised if the trident server could manage this chip at all -- that server is targeted at the 9525DVD; that's a long ways from the CyberBlade/i7. I don't know if it would be better to start with the trident server or just starting fresh for the CyberBlade based on the vesa driver. I'd like to hear from others whether this vm86 change is reasonable; it would be nice to make Xvesa work on as many machines as possible. [EMAIL PROTECTED] XFree86 Core Team SuSE, Inc. _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
