[Xorg-driver-geode] Rendering in geode

Huang, FrankR FrankR.Huang at amd.com
Tue Jun 29 02:21:47 PDT 2010


	One question still.
	I found the root cause of the firefox issue. But there is one thing need your advice. You know if the screen resolution is 1280x1024, and the first pass result of PictOpOver need maximum 1280x1024x4(ARGB8888) size. But if our driver's framebuffer is not big enough, how do we do 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