---
Somebody at XDC today said that getting rid of the static MAXSCREENS
limit from the X server would be a Good Thing, and it looked like doing
that to Xext/shm.c would be pretty easy, so I tried it.
This is my first server patch, so review gratefully accepted.
Xext/shm.c | 60 +++
Excerpts from Jamey Sharp's message of Wed Sep 30 22:29:39 -0700 2009:
> ---
> Somebody at XDC today said that getting rid of the static MAXSCREENS
> limit from the X server would be a Good Thing, and it looked like doing
> that to Xext/shm.c would be pretty easy, so I tried it.
Thanks for giving
On Thu, Oct 1, 2009 at 3:08 PM, Keith Packard wrote:
> Thanks for giving this a try. The canonical way to do this is to
> allocate a screen private index and then allocate memory per-screen
> instead of globally, ...
Hmm. I think that's what I did? I followed the pattern in
miext/damage/damage.c,
Excerpts from Jamey Sharp's message of Thu Oct 01 15:26:47 -0700 2009:
> Hmm. I think that's what I did?
Wow. 3 hours of sleep is clearly not good here. Yes, it looks quite
reasonable on actual review (and a couple of hours of napping on the plane).
> But ProcPanoramiXShmGetImage seems to need a
