Jonathan,
Based on this formula, I ask you a question:
I found that our HW can not support PICT_a8 destination, only support
PICT_r3g3b2 destination. Can you use PICT_r3g3b2? From the experiment, the
result is not correct. I think the HW will split the 8 bits value into 3,3,2
and do the PictOpAdd separately instead a whole 8 bits value?
Or do that in SW way (I wrote in the driver)?
Thanks,
Frank
-----Original Message-----
From: xorg-driver-geode-bounces+frankr.huang=amd....@lists.x.org
[mailto:xorg-driver-geode-bounces+frankr.huang=amd....@lists.x.org] On Behalf
Of Jonathan Morton
Sent: 2010?7?14? 19:22
To: Mart Raudsepp
Cc: Huang, FrankR; xorg-driver-geode@lists.x.org; mic...@daenzer.net
Subject: Re: [Xorg-driver-geode] Glyph rendering
On Wed, 2010-07-14 at 14:17 +0300, Mart Raudsepp wrote:
> Op:PictOpAdd, Src:PICT_a8 Mask:0 Dest:PICT_a8
Okay, this is really really easy to do - it's a saturating addition:
d = MIN(s + d, 255);
That should solve your immediate problem.
--
------
From: Jonathan Morton
jonathan.mor...@movial.com
_______________________________________________
Xorg-driver-geode mailing list
Xorg-driver-geode@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-geode
_______________________________________________
Xorg-driver-geode mailing list
Xorg-driver-geode@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-geode
