Nat Ersoz wrote: >Hi, > >I'm debugging an X driver for the Geode hardware. > >1. I've downloaded the latest "durango" code from National. It doesn't >seem to work worth a damn (I get stuck hanging on several "loop while >bit changes state" type code). Interestingly, none of these bits are >documented in the SC1200 register spec, which is 300 pages long :( ) > >Anyone have any positive thoughts regarding National's "Durango" XF86 >driver or helpful hints? Thanks! > >2. I thought that it would be useful to work from the Cyrix driver and >add the PCI probe code to it, and start from this much simpler and >cleaner code base. > >Well this approach sort of works, in that the PCI probe succeeds and I >get all the way up to CYRIXScreenInit(), which runs all the way through, >entry to exit (I can tell by putting in liberal doses of xf86Msg() >calls). At the end of CYRIXScreenInit(), I write a bunch of data to the >mapped frame buffer memory, just to see if anything faults out >(indicating a errored mapping) and everything proceeds OK - no faults. > >However, upon exiting CYRIXScreenInit(), the Server just sits there (see >attached log). Applications cannot connect to the display (they stall >without error, much like the server). > >Obviously, since the Cyrix driver is open source, I'll gladly >redistribute whatever useful progress I can make on this. > >Thanks, > > > > The only way I have been able to use a bit of Durango, is using the kernel Geode framebuffer driver, along with a standard/beautiful/well working Kdrive Xfbdev (framebuffer) server. The X driver was distributed for Xfree86 4.1.0, I don't know if changes with 4.2.x are significant enough to make it not working.
Best Regards, Rolland Dudemaine _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
