Around 16 o'clock on May 20, Alex Pavloff wrote:
> Option B) Attempt to figure out what Keith Packard was doing with the > "other" drivers in the kdrive directory, and modify the geode source code to > match that. That's the right option -- you'll find several existing servers which layer on top of the basic fbdev/vesa servers to add a bit of acceleration. Kdrive contains 'kaa.c', which looks a bit like XAA, except that it accelerates only two operations -- solid fills and screen->screen blts. For modern applications, that's about all you'll need to have a respectable server. Take a look at the hw/kdrive/mach64 driver, it's layered on vesa, but doing much the same on top of fbdev is also possible. If the geode provides a VESA bios, you'll want to use the vesa layer instead of fbdev as that can support RandR while fbdev provides only a single size. > Option C) Say fuggedaboutit, and just use the Xfbdev server as is, because > its not going to be much faster. For screen sizes over 800x600 and depths over 16 bits, you really need screen->screen copies to make a reasonable X server. Keith Packard XFree86 Core Team HP Cambridge Research Lab _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
