Re: [Xpert]Re: Using the chips XFree86 driver on a PowerBook3400 (almost there.)
Michael Stephen Hanni writes: G'day Egbert, The funny thing is that using either cursor I get this behavior. I'll look into this, maybe I did something that made the hardware cursor be used regardless of the option setting. Hmm, that's funny. It is possible that the cursor Image is goffed before. You usually have a foreground and a background mask. If one of the masks is goofed you get this behavior regardless if you use sw or hw cursor. BTW, I'm working off CVS HEAD. Oh, I haven't really touched this but XVideo is still fscked. I'm getting BadAllocs all over the place. Please see my last email about this. Yeah, what you said sounds absolutely correct. I've disabled the CHIPSVideoInit/Reset in my build. You should not have to. I assume you do that to force your application to do a fallback to SW rendering. This however should always happen if Xv signals an error. I had to mess around with the aperture, but I think I've got the aperture and the MMIOBase setup correctly now. By dropping a slightly modified ct_BltHiQV.h from the last Xpmac tarball into the latest XFree86 source everything works nicely. If you send me the patch I'll check this. I'll do this when I get back to the other side (i.e. Linux). Beware this ct_BltHiQV.h has some interesting looking asm code to accomplish the ct* macros. I'm pretty sure this is powerpc specific so it may not be something you would want to put into the official source. However, the bonus of this is that I had to make very few changes to the driver as it currently stands, plus I got all the accelerated functions for free -- save for the aforementioned WritePixmap. I will take a look. We can (however it is discouraged) use #ifdef __powerpc__ . Anyhow, I'll clean it up and send it to you tonight. Thanks! I'm using this modified chips driver as my default X setup and I haven't noticed anything broken or unusual. It seems to be snappier and smoother than the FBDev driver I had been using, but that may just be the placebo effect at work. I'll run some x11perf tests and check it out. OK, great! Thanks, Egbert. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Re: Using the chips XFree86 driver on a PowerBook3400 (almost there.)
Michael Stephen Hanni writes: Howdy. Well I've got it all to work save for the WritePixmap acceleration as it makes use of some fun MoveDataFromCPU/MoveDWORDS magic. With WritePixmap active there is a small box of color distortion around the mouse cursor. I'm sure the MoveDataFromCPU function is assuming little endian data, but I don't know exactly what I'm looking at. Are you using SW Cursor? Otherwise WritePixmap shouldn't affect the Cursor. Oh, I haven't really touched this but XVideo is still fscked. I'm getting BadAllocs all over the place. Please see my last email about this. I had to mess around with the aperture, but I think I've got the aperture and the MMIOBase setup correctly now. By dropping a slightly modified ct_BltHiQV.h from the last Xpmac tarball into the latest XFree86 source everything works nicely. If you send me the patch I'll check this. As for the hardware cursor, you will have to swap the image of the cursor. See the hw cursor support for radeon (or r128) and apply similair necessary the big endian bits. Ah, got ya. I'm going to run some more tests and then I'll upload a patch somewhere for general consumption. Maybe, just maybe, there are other people that use this chip on a big endian machine. Please send the patch this way. As I'm the CT maintainer. Regards, Egbert. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Re: Using the chips XFree86 driver on a PowerBook3400 (almost there.)
G'day Egbert, on 10-10-2002 7:30 AM, Egbert Eich at [EMAIL PROTECTED] wrote: Michael Stephen Hanni writes: Well I've got it all to work save for the WritePixmap acceleration as it makes use of some fun MoveDataFromCPU/MoveDWORDS magic. With WritePixmap active there is a small box of color distortion around the mouse cursor. I'm sure the MoveDataFromCPU function is assuming little endian data, but I don't know exactly what I'm looking at. Are you using SW Cursor? Otherwise WritePixmap shouldn't affect the Cursor. The funny thing is that using either cursor I get this behavior. I'll look into this, maybe I did something that made the hardware cursor be used regardless of the option setting. BTW, I'm working off CVS HEAD. Oh, I haven't really touched this but XVideo is still fscked. I'm getting BadAllocs all over the place. Please see my last email about this. Yeah, what you said sounds absolutely correct. I've disabled the CHIPSVideoInit/Reset in my build. I had to mess around with the aperture, but I think I've got the aperture and the MMIOBase setup correctly now. By dropping a slightly modified ct_BltHiQV.h from the last Xpmac tarball into the latest XFree86 source everything works nicely. If you send me the patch I'll check this. I'll do this when I get back to the other side (i.e. Linux). Beware this ct_BltHiQV.h has some interesting looking asm code to accomplish the ct* macros. I'm pretty sure this is powerpc specific so it may not be something you would want to put into the official source. However, the bonus of this is that I had to make very few changes to the driver as it currently stands, plus I got all the accelerated functions for free -- save for the aforementioned WritePixmap. Anyhow, I'll clean it up and send it to you tonight. I'm using this modified chips driver as my default X setup and I haven't noticed anything broken or unusual. It seems to be snappier and smoother than the FBDev driver I had been using, but that may just be the placebo effect at work. I'll run some x11perf tests and check it out. Cheers, Michael ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Re: Using the chips XFree86 driver on a PowerBook3400 (almost there.)
Howdy. Well I've got it all to work save for the WritePixmap acceleration as it makes use of some fun MoveDataFromCPU/MoveDWORDS magic. With WritePixmap active there is a small box of color distortion around the mouse cursor. I'm sure the MoveDataFromCPU function is assuming little endian data, but I don't know exactly what I'm looking at. Oh, I haven't really touched this but XVideo is still fscked. I'm getting BadAllocs all over the place. on 10-9-2002 12:49 PM, Ani Joshi at [EMAIL PROTECTED] wrote: It seems you have changed the address space to use the big endian aperture, this is correct. As for the accel engine, try turning off all acceleration (just #if them out in the driver, no need for several XaaNo* Options), and leave on SolidFills, this is the easiset to debug. There is a problem with some 65550's and polling of the BR04 register which tends to lockup the engine, you may be running into that. I would grab the old source from Xpmac (I believe it had ct accel) and poke around there to see where the engine is initialized and the proper way to BLTWAIT on this chip, its been long since I hacked on the ct65550 so I don't remember sorry. I had to mess around with the aperture, but I think I've got the aperture and the MMIOBase setup correctly now. By dropping a slightly modified ct_BltHiQV.h from the last Xpmac tarball into the latest XFree86 source everything works nicely. As for the hardware cursor, you will have to swap the image of the cursor. See the hw cursor support for radeon (or r128) and apply similair necessary the big endian bits. Ah, got ya. I'm going to run some more tests and then I'll upload a patch somewhere for general consumption. Maybe, just maybe, there are other people that use this chip on a big endian machine. Cheers, Michael ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
