Re: [Dri-devel] Re: VIA's Savage Drivers

2003-10-15 Thread Alan Cox
On Mer, 2003-10-15 at 21:07, Alex Deucher wrote: the 3D drvier needs to be updated to mesa 5.x. Not much work has been done on it and I think there are some issues with the 2D driver. There's no way it will make it into 4.4.0. the current code is on a branch in DRI cvs. If you are

Re: [Fwd: Re: Fwd: Vblank support in kernel and X server]

2003-09-11 Thread Alan Cox
On Mer, 2003-09-10 at 23:21, Michel Dnzer wrote: On Wed, 2003-09-10 at 19:00, Jim Gettys wrote: Here's Alan Cox's mail about it. In 2.4.20-ac1. Won't this conflict with the DRM vblank interrupt handling? (I've also seen framebuffer device patches for this...) Thats a matter for the X

Re: [Dri-devel] Re: User sponsored drivers

2003-07-16 Thread Alan Cox
On Mer, 2003-07-16 at 15:08, Alex Deucher wrote: Support for HW accelerated indirect rendering is just a matter of restructuring some library interfaces so that GLX commands can get decoded and sent to the hardware rather than the sw renderer. It's in the pipeline for future development by

Re: [Dri-devel] Re: [Xpert]Re: But *why* no vblank?

2002-11-22 Thread Alan Cox
On Sun, 2002-11-03 at 22:46, Elladan wrote: could be wrong about that, but I think you'd need rtlinux style extensions to the kernel to achieve direct interrupt deliveries to user-space (and you'd need to be root, and such). You cannot deliver interrupts directly to user space without

[Xpert]Re: [Dri-devel] Savage and nVidia DRI drivers

2002-11-02 Thread Alan Cox
On Thu, 2002-10-31 at 02:16, José Fonseca wrote: project. Also the proprietary nVidia Linux drivers come with some source code (which was also the basis for the Utah-GLX drivers). I have the last release they did that was merely all obfuscated, and some tools for partially deobfuscating it.

[Xpert]Re: [Dri-devel] Savage and nVidia DRI drivers

2002-11-02 Thread Alan Cox
On Thu, 2002-10-31 at 11:26, Keith Whitwell wrote: At one point there was a shadowfb based 2d driver for the voodoo cards -- it would be interesting an interesting approach to add a dri layer to that driver, if it still exists. I use it on several boxes. It has some endian limitations (from

[Xpert]Re: [Dri-devel] Savage and nVidia DRI drivers

2002-11-02 Thread Alan Cox
On Thu, 2002-10-31 at 15:58, José Fonseca wrote: I don't know much about SIS 6326. I know that there is some deprecated (it hasn't been updated for the architectural changes) support for SIS 630 chips on the CVS. 6326 is much older than 630 and 315 etc. Its in the PIO with very small fifo

Re: [Xpert]Patches for xfree86 cyrix (NatSemi GX1) driver

2002-10-27 Thread Alan Cox
Tested the geode driver as of current CVS - it crashes my hardware dead with a blank screen and so hard it needs a power cycle to get it back. Looks like it explodes during the mode switch. Send along any patches you make, but I've tested the geode driver on at least 4 platforms here and

Re: [Xpert]Patches for xfree86 cyrix (NatSemi GX1) driver

2002-10-27 Thread Alan Cox
The BIOS says XpressROM V3.1.0 (National's), built 03/08/2001, with chip 5530A Rev B1. I'm Ok thats much newer firmware. I need to go back over my mode switch find out why the newer VSA doesnt like it. Its working on older VSA1 stuff. ___ Xpert

Re: [Xpert]Patches for xfree86 cyrix (NatSemi GX1) driver

2002-10-23 Thread Alan Cox
Yes, Sorry Alan. I've not even looked at your stuff yet, but as the current Cyrix driver in CVS purely deals with the (ISA based) integrated There isnt really an ISA version. All of them appear on PCI (5510, 5520 and 5530/5530+). Neither 5520 or 5530 actually work with the cyrix driver from my

Re: [Xpert]Patches for xfree86 cyrix (NatSemi GX1) driver

2002-10-23 Thread Alan Cox
I'm not familiar with the original MediaGX chips, but the 4.2 driver has a FindIsaDevice function that probes ports directly rather than using any PCI vendor codes. Is the MediaGX the 5510 ? MediaGX is a brand name for the CPU side of the CPU+5510/5520/5530. The history goes something like

Re: [Xpert]Patches for xfree86 cyrix (NatSemi GX1) driver

2002-10-23 Thread Alan Cox
I'm surprised that if the original 5510/5520 chips are PCI then why aren't we using the PCI information rather than port probing ? Nobody ever finished the driver ? They are all PCI I checked ___ Xpert mailing list [EMAIL PROTECTED]

Re: [Xpert]Patches for xfree86 cyrix (NatSemi GX1) driver

2002-10-23 Thread Alan Cox
- The cyrix driver as is in the xfree86 CVS does not work on National's current Centaurus II development board (GX1+5530). (Presumably it works on older chipsets, I don't know enough to speak to that). It doesnt work on anything as far as I can tell. Incomplete code. - Alan's version of

Re: [Xpert]Patches for xfree86 cyrix (NatSemi GX1) driver

2002-10-23 Thread Alan Cox
But I have disabled the 5530 support for now, to encourage geode driver testing. Sure. I'm going to do some testing myself. I'll also see if I can get your driver to do 5520. The 5520 VSA1 (if you can find working 5520 VSA1!) is much like the 5530 but without Xv. If I can get 5520 VSA1 working

Re: [Xpert]Patches for xfree86 cyrix (NatSemi GX1) driver

2002-10-23 Thread Alan Cox
is much like the 5530 but without Xv. If I can get 5520 VSA1 working in geode then I can make the cyrix driver just a biosfree driver for the older/weirder end of the universe. Well, it'd be even nicer to deprecate the cyrix driver in favour of the geode driver if you can bring across

[Xpert]XFree86 driver work

2002-10-08 Thread Alan Cox
On ftp://people.redhat.com/alan please find - A Cyrix driver for XFree86 4.2 (CS5520/CS5530) The shipped driver appears to be incomplete, the detection didn't work, mode change didn't work and was done wrongly, palette handling didn't work and a few other

[Xpert]RE: [Dri-devel] DRI/DRM handshake API

2002-10-08 Thread Alan Cox
On Fri, 2002-08-23 at 00:21, Sottek, Matthew J wrote: So what is the solution? A XFree - DRM handshake would also make this an easy fix but we only have a one way version checking. If everyone learns from my mistake and is vigilant in the future we can just stick with the current system,