On August 22, 2014 9:16:31 AM EDT, Jeremy White <jwh...@codeweavers.com> wrote: >On 08/22/2014 08:07 AM, Alon Levy wrote: >> Sorry for top posting. I was replying to Marc-Andre's assertion. If >the >> subject isnt arbitrary resolution, aka dynamic, continuous, then I >> missed it. If it is, since agent support for Xspice this feature >works >> per my memory. > >Ah, okay. Yes, my patch broke^H^H^H^H^Htouched x mode support, but the > >main emphasis was on configuring the ram buffer allocation; I think >that's what Marc-Andre was referring to. (And dynamic resolutions do, >in fact, work nicely with the agent turned on).
Actually no excuse for the top post. I see. I like the idea of making sane memory allocation. When I ''fused'' Xspice I took what I thought was was simplest. I think you can replace mspace with malloc. There is no api to disable the address translation we do (i.e. memslots) but it's already equallity. I can't think of any other complication. Yes, the framebuffer is one allocation but it can be changed on every create primary, before it actually and after the destroy primary, with realloc. Maybe even the address can be changed, I think it could, but realloc takes care of that. I guess that has some cost though. > >Cheers, > >Jeremy -- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
