Yes, absolutely, we should have a CAP for that.
Marek
On Wed, Jul 24, 2013 at 12:20 AM, Jose Fonseca wrote:
> - Original Message -
>> FYI, OpenGL 4.4, which was released yesterday, adds GL_MAP_PERSISTENT
>> and GL_MAP_COHERENT bits as valid parameters of glMapBufferRange and
>> glBufferS
- Original Message -
> FYI, OpenGL 4.4, which was released yesterday, adds GL_MAP_PERSISTENT
> and GL_MAP_COHERENT bits as valid parameters of glMapBufferRange and
> glBufferStorage, allowing to use buffers for rendering while they are
> mapped and upload/download data to/from the buffers s
FYI, OpenGL 4.4, which was released yesterday, adds GL_MAP_PERSISTENT
and GL_MAP_COHERENT bits as valid parameters of glMapBufferRange and
glBufferStorage, allowing to use buffers for rendering while they are
mapped and upload/download data to/from the buffers simultaneously.
It's now clear that Ga
- Original Message -
> On Don, 2012-01-26 at 20:45 +0100, Marek Olšák wrote:
> > On Tue, Jan 10, 2012 at 6:20 PM, Jose Fonseca
> > wrote:
> > >> On Tue, Jan 10, 2012 at 5:15 PM, Jose Fonseca
> > >>
> > >> wrote:
> > >> >
> > >> > Also, please provide app name and performance figures w/
On Don, 2012-01-26 at 20:45 +0100, Marek Olšák wrote:
> On Tue, Jan 10, 2012 at 6:20 PM, Jose Fonseca wrote:
> >> On Tue, Jan 10, 2012 at 5:15 PM, Jose Fonseca
> >> wrote:
> >> >
> >> > Also, please provide app name and performance figures w/ this
> >> > change.
> >>
> >> OK. Torcs, the Forza t
On Tue, Jan 10, 2012 at 6:20 PM, Jose Fonseca wrote:
>
>
> - Original Message -
>> On Tue, Jan 10, 2012 at 5:15 PM, Jose Fonseca
>> wrote:
>> > - Original Message -
>> >> The flag is optional, it doesn't have to implemented by everybody.
>> >> If
>> >> we do the uploads in the sta
- Original Message -
> On Tue, Jan 10, 2012 at 5:15 PM, Jose Fonseca
> wrote:
> > - Original Message -
> >> The flag is optional, it doesn't have to implemented by everybody.
> >> If
> >> we do the uploads in the state tracker, we will also do any
> >> required
> >> data transfor
On Tue, Jan 10, 2012 at 5:15 PM, Jose Fonseca wrote:
> - Original Message -
>> The flag is optional, it doesn't have to implemented by everybody. If
>> we do the uploads in the state tracker, we will also do any required
>> data transformation so that drivers don't have to do it at all.
>
- Original Message -
> On 01/10/2012 01:13 PM, Jose Fonseca wrote:
> > - Original Message -
> >> On 10.01.2012 12:29, Jose Fonseca wrote:
> >>> Still catching up on email traffic during holidays...
> >>>
> >>> I agree that user buffer uploads should be moved out of drivers,
> >>>
On 01/10/2012 01:13 PM, Jose Fonseca wrote:
> - Original Message -
>> On 10.01.2012 12:29, Jose Fonseca wrote:
>>> Still catching up on email traffic during holidays...
>>>
>>> I agree that user buffer uploads should be moved out of drivers,
>>> but I don't think this is the way to go.
>>
>
- Original Message -
> On Tue, Jan 10, 2012 at 12:29 PM, Jose Fonseca
> wrote:
> > Still catching up on email traffic during holidays...
> >
> > I agree that user buffer uploads should be moved out of drivers,
> > but I don't think this is the way to go.
> >
> > This "PIPE_TRANSFER_MAP_PER
On Tue, Jan 10, 2012 at 12:29 PM, Jose Fonseca wrote:
> Still catching up on email traffic during holidays...
>
> I agree that user buffer uploads should be moved out of drivers, but I don't
> think this is the way to go.
>
> This "PIPE_TRANSFER_MAP_PERMANENTLY" means the driver relinquishes the
- Original Message -
> On 10.01.2012 12:29, Jose Fonseca wrote:
> > Still catching up on email traffic during holidays...
> >
> > I agree that user buffer uploads should be moved out of drivers,
> > but I don't think this is the way to go.
>
> I don't. If the state tracker uploads user buf
On 10.01.2012 12:29, Jose Fonseca wrote:
> Still catching up on email traffic during holidays...
>
> I agree that user buffer uploads should be moved out of drivers, but I don't
> think this is the way to go.
I don't. If the state tracker uploads user buffers and presents them to
the driver as n
Still catching up on email traffic during holidays...
I agree that user buffer uploads should be moved out of drivers, but I don't
think this is the way to go.
This "PIPE_TRANSFER_MAP_PERMANENTLY" means the driver relinquishes the ability
to transform this data in any way before reashing the G
Looks good on first sign. I'm waiting for this for quite some time now,
cause it makes XvMC state tracker implementation more cleaner and faster.
Acked-by: Christian König
On 02.01.2012 01:22, Marek Olšák wrote:
Please see the diff for further info.
This paves the way for moving user buffer
Please see the diff for further info.
This paves the way for moving user buffer uploads out of drivers and should
allow to clean up the mess in u_upload_mgr in the meantime.
For now only allowed for buffers on r300 and r600.
---
src/gallium/drivers/i915/i915_resource_buffer.c |7 ++-
sr
17 matches
Mail list logo
