From: Chia-I Wu
MESA_FORMAT_RGBX_REV is one of the opaque pixel formats used on Android.
Thanks to texture-from-pixmap, drivers may actually see texture images with
this format on Android.
MESA_FORMAT_RGBX is added only for completeness.
---
src/mesa/main/format_unpack.c | 28 +++
On 11/23/2011 02:35 PM, Brian Paul wrote:
> This simplifies a few callers. And it adds a bit of robustness.
> ---
> src/mesa/main/bufferobj.c|6 +++---
> src/mesa/main/bufferobj.h|2 +-
> src/mesa/state_tracker/st_draw.c | 10 +-
> 3 files changed, 9 insertions(+
On 11/24/2011 04:47 AM, Marek Olšák wrote:
> On Wed, Nov 23, 2011 at 7:25 PM, Ian Romanick wrote:
>> Let me paraphrase this a little bit in a way that I think concisely captures
>> the intention:
>>
>>"We need to work really hard to make things work on older hardware."
>>
>> I don't think anyo
On Wed, 23 Nov 2011 15:08:23 -0800, Ian Romanick wrote:
> On 11/23/2011 02:35 PM, Brian Paul wrote:
> > If alpha test is enabled and there's no color buffers we still need the
> > fragment shader to emit a color.
> >
> > Fixes piglit fbo-alphatest-nocolor-ff failures with Gallium drivers.
>
> It
On Wed, 23 Nov 2011 12:24:37 -0700, Brian Paul wrote:
> On 11/23/2011 12:12 PM, Eric Anholt wrote:
> > On Wed, 23 Nov 2011 17:34:30 +0800, Yuanhan
> > Liu wrote:
> >> From 9a1da8748f0faa23f34398213ff7ee45fda6bf36 Mon Sep 17 00:00:00 2001
> >> From: Yuanhan Liu
> >> Date: Wed, 23 Nov 2011 17:37:
On 11/24/11 05:25, Dave Airlie wrote:
On UNIX malloc generally hasn't returned NULL since overcommit was
invented, what happens now is some time in the future
you attempt to use a page and your app dies.
s/UNIX/Linux/ - other Unixes still prefer reliability over random
OOM crashes.
--
> By this same logic, malloc should never return NULL because most apps can't
> handle it. Instead it should mmap /dev/null and return a pointer to that.
> That analogy isn't as far off as it may seem: in both cases the underlying
> infrastructure has lied to the application that an operation su
On Wed, Nov 23, 2011 at 7:25 PM, Ian Romanick wrote:
> Let me paraphrase this a little bit in a way that I think concisely captures
> the intention:
>
> "We need to work really hard to make things work on older hardware."
>
> I don't think anyone disagrees with that. However, the solutions you
