On Tue, 4 Oct 2011 12:37:59 -0700, Aaron Plattner <[email protected]> wrote:

> With the old CreatePixmap API, drivers could override the width and 
> height when calling down to prevent the fb layer from allocating the 
> pixmap memory, and then plug in its own.  It looks like a driver could 
> do the same thing now by changing the pixmap structure's width and 
> height to 0 temporarily, but it looks like that will cause the new code 
> to call malloc(0) and then fail if it returns NULL.

Might make sense to have the fb code *not* allocate memory if
devPrivate.ptr is non-zero?

-- 
[email protected]

Attachment: pgpM4xyT5j0xZ.pgp
Description: PGP signature

_______________________________________________
[email protected]: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel

Reply via email to