Re: XFree86 4.1.0: call for help
Kostas Gewrgiou wrote:
>
> On Tue, 19 Jun 2001, Ani Joshi wrote:
>
> > On Tue, 19 Jun 2001, Michel [iso-8859-1] Dänzer wrote:
> >
> > > That would be nice, unfortunately it doesn't. For the record, here's the
> > > patch against xf-4_1-branch I tested:
> >
> >
> > Please try the attached patch. This fixes the problem on PCI machines and
> > could possibly fix yours too.
> >
> > It is against the stock 4.1.0 driver.
It works BTW.
> It will probably work for us, but it can't go in the XFree code
> the problem is linux/ppc specific and has to be fixed in the
> os specific part of the code. LynxOS/Pmax handle the
> ioBase problem (only the first bridge is supported there) and
> i assume that they need the vga font restore code.
Why don't we need that and colormap anyway?
> The #ifdef __powerpc__ isn't right (and we can't use os specific
> code in the drivers) so the fix has to go in another layer,
> crippling another os to fix our problems isn't the right solution.
So, what can we do? We can't put arch or OS specific code to handle this in
vgaHW either. Maybe it's really best to handle it in the kernel?
While we're at it: The last other real issue in the r128 driver is mostly
exposed by Xv: the data is moved to the framebuffer word by word, but it gets
swapped depending on the current depth, so the video is broken. Does anyone
have a better idea than to use different ways to move the data depending on
the depth?
Wait, I have an idea: Disable byte swapping before moving the data and restore
it after. I'm going to test that.
--
Earthling Michel Dänzer (MrCooper) \ Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast \ XFree86 and DRI project member
Reply to: