[Xorg-driver-geode] Rendering in geode

Huang, FrankR FrankR.Huang at amd.com
Mon Jun 28 21:08:08 PDT 2010

	The Off-screen region is 256KB.
	But in my function, I will use the space more than that. Such as a 700x300 rectangle, it need 700x300x4 byte = 820KB. So it is greater than 256KB, right now I give the off-screen region to 2MB, this issue is not appeared till now.
	So please give a try
	Line 90:
	#define DEFAULT_EXA_SCRATCH_BFRSZ from 0x40000 to 0x200000
	The accurate memory the off-screen need is not 2MB, just a test and I'll keep on research on that. 


-----Original Message-----
From: xorg-driver-geode-bounces+frankr.huang=amd.com at lists.x.org [mailto:xorg-driver-geode-bounces+frankr.huang=amd.com at lists.x.org] On Behalf Of Jonathan Morton
Sent: 2010?6?24? 20:03
To: Huang, FrankR
Cc: xorg-driver-geode at lists.x.org; xorg-devel at lists.x.org
Subject: Re: [Xorg-driver-geode] Rendering in geode

On Thu, 2010-06-24 at 17:21 +0800, Huang, FrankR wrote:
> The reason I use 4*PITCH is that the src is A8 picture, and the src'
> format is ARGB32, so it is 4*PITCH. I don't know if that is reasonable
> to appoint that pitch directly instead of exaGetPixmapPitch().

Since the source is typically a 1-pixel "solid colour" image in this
situation, the stride of that image would not be directly relevant.  The
stride of the destination would be independent of both source and mask.

Looking very briefly at your code, it seems that you are using a
temporary image to expand the source colour to cover the required area.
You are, of course, in complete control of that temporary image, so you
can use any stride you like that does not cause overlaps.

From: Jonathan Morton
      jonathan.morton at movial.com

Xorg-driver-geode mailing list
Xorg-driver-geode at lists.x.org

More information about the Xorg-driver-geode mailing list