On Fri, Oct 10, 2003 at 03:16:45PM -0700, Ian Romanick wrote:
|
| Since I was part of that working group, I'd like to clarify why some of
| those decisions were made. ...
Apologies if I sounded too critical -- I agree that compromise was a
reasonable thing to do in the VBO case.
|
On Fri, Oct 10, 2003 at 11:24:24PM +0100, Alan Cox wrote:
> On Iau, 2003-10-09 at 17:16, Alan Hourihane wrote:
> > I've just committed a version of the DRI's common code mm.[ch] linear allocator
> > into the XFree86 CVS which extends the FBManager's ability to serve
> > real linear space rather tha
On Fri, Oct 10, 2003 at 11:24:24PM +0100, Alan Cox wrote:
> On Iau, 2003-10-09 at 17:16, Alan Hourihane wrote:
> > I've just committed a version of the DRI's common code mm.[ch] linear allocator
> > into the XFree86 CVS which extends the FBManager's ability to serve
> > real linear space rather tha
On Gwe, 2003-10-10 at 23:16, Ian Romanick wrote:
> on some it's dumped but the driver has a change to back it up, and on
> others it's just dumped.
>
> AFAIK, perhaps someone can correct me, XFree86 on Linux falls into the
> last category.
It depends on the BIOS and other factors. For ACPI it i
On Iau, 2003-10-09 at 17:16, Alan Hourihane wrote:
> I've just committed a version of the DRI's common code mm.[ch] linear allocator
> into the XFree86 CVS which extends the FBManager's ability to serve
> real linear space rather than pinching it from the XY area's that's
> usually occupied by the
>>>Right. And certainly now with the new linear allocator the Xserver can
>>>manage the whole lot.
>>
>>Does the X server make any promises about preserving the contents of the
>>fb memory? EG, if there's a VT switch, will the contents be saved
>>somehow?
>
>
> No. No preservation is done. We ne
Allen Akin wrote:
Besides performance loss and memory bloat, the lack of framebuffer
memory preservation on Windows has forced some new extensions to have
ugly semantics. See the vertex buffer object extension
http://oss.sgi.com/projects/ogl-sample/registry/ARB/vertex_buffer_object.txt
for on
On Thu, Oct 09, 2003 at 12:04:08PM -0700, Ian Romanick wrote:
> Alan Hourihane wrote:
> >On Thu, Oct 09, 2003 at 05:30:08PM +0100, Keith Whitwell wrote:
> >>Alan Hourihane wrote:
> >>
> >>>I've just committed a version of the DRI's common code mm.[ch] linear
> >>>allocator
> >>>into the XFree86 CV
On Fri, Oct 10, 2003 at 12:24:56PM +0100, Keith Whitwell wrote:
|
| >No. No preservation is done. We need to invalidate everything.
|
| That's a problem, as the only way we can do things like accelerated
| CopyTexSubImage() and single-copy textures is if the FB contents are
| guarenteed to be p
On Fri, Oct 10, 2003 at 12:24:56PM +0100, Keith Whitwell wrote:
>
> >>>Right. And certainly now with the new linear allocator the Xserver can
> >>>manage the whole lot.
> >>
> >>Does the X server make any promises about preserving the contents of the
> >>fb memory? EG, if there's a VT switch, wi
Right. And certainly now with the new linear allocator the Xserver can
manage the whole lot.
Does the X server make any promises about preserving the contents of the fb
memory? EG, if there's a VT switch, will the contents be saved somehow?
No. No preservation is done. We need to invalidate ev
On Fri, Oct 10, 2003 at 11:16:06AM +0100, Keith Whitwell wrote:
> Alan Hourihane wrote:
> >On Thu, Oct 09, 2003 at 06:36:11PM +0100, Keith Whitwell wrote:
> >
> >>Alan Hourihane wrote:
> >>
> >>>On Thu, Oct 09, 2003 at 05:30:08PM +0100, Keith Whitwell wrote:
> >>>
> >>>
> Alan Hourihane wrote:
Alan Hourihane wrote:
On Thu, Oct 09, 2003 at 06:36:11PM +0100, Keith Whitwell wrote:
Alan Hourihane wrote:
On Thu, Oct 09, 2003 at 05:30:08PM +0100, Keith Whitwell wrote:
Alan Hourihane wrote:
I've just committed a version of the DRI's common code mm.[ch] linear
allocator
into the XFree86 C
On Thu, Oct 09, 2003 at 06:36:11PM +0100, Keith Whitwell wrote:
> Alan Hourihane wrote:
> >On Thu, Oct 09, 2003 at 05:30:08PM +0100, Keith Whitwell wrote:
> >
> >>Alan Hourihane wrote:
> >>
> >>>I've just committed a version of the DRI's common code mm.[ch] linear
> >>>allocator
> >>>into the XFre
Alan Hourihane wrote:
On Thu, Oct 09, 2003 at 05:30:08PM +0100, Keith Whitwell wrote:
Alan Hourihane wrote:
I've just committed a version of the DRI's common code mm.[ch] linear
allocator
into the XFree86 CVS which extends the FBManager's ability to serve
real linear space rather than pinching it
On Thu, Oct 09, 2003 at 05:30:08PM +0100, Keith Whitwell wrote:
> Alan Hourihane wrote:
> >I've just committed a version of the DRI's common code mm.[ch] linear
> >allocator
> >into the XFree86 CVS which extends the FBManager's ability to serve
> >real linear space rather than pinching it from the
Alan Hourihane wrote:
On Thu, Oct 09, 2003 at 05:30:08PM +0100, Keith Whitwell wrote:
Alan Hourihane wrote:
I've just committed a version of the DRI's common code mm.[ch] linear
allocator
into the XFree86 CVS which extends the FBManager's ability to serve
real linear space rather than pinching i
On Thu, Oct 09, 2003 at 05:30:08PM +0100, Keith Whitwell wrote:
> Alan Hourihane wrote:
> >I've just committed a version of the DRI's common code mm.[ch] linear
> >allocator
> >into the XFree86 CVS which extends the FBManager's ability to serve
> >real linear space rather than pinching it from the
Alan Hourihane wrote:
I've just committed a version of the DRI's common code mm.[ch] linear allocator
into the XFree86 CVS which extends the FBManager's ability to serve
real linear space rather than pinching it from the XY area's that's
usually occupied by the pixmap cache.
This way we can now han
I've just committed a version of the DRI's common code mm.[ch] linear allocator
into the XFree86 CVS which extends the FBManager's ability to serve
real linear space rather than pinching it from the XY area's that's
usually occupied by the pixmap cache.
This way we can now hand over all memory to
20 matches
Mail list logo
