On Sat, Apr 24, 2010 at 10:25 AM, Jakob Bornecrantz
wrote:
> The struct st_module isn't needed as it is the same thing as the st_api
> struct. That is they both represent the API. Instead just use a single
> function entry point to the the API.
> ---
> src/gallium/include/state_tracker/st_api.h
https://bugs.freedesktop.org/show_bug.cgi?id=24016
Sven Arvidsson changed:
What|Removed |Added
Summary|Shadowgrounds: bad |Shadowgrounds: menu fades
https://bugs.freedesktop.org/show_bug.cgi?id=19430
--- Comment #4 from Sven Arvidsson 2010-04-24 14:09:26 PDT ---
(Answering myself here)
The "No matching FBConfig" comes from the application, not Mesa. It seems it's
asking for GLX_PBUFFER_BIT and pbuffers isn't that well supported?
For referen
https://bugs.freedesktop.org/show_bug.cgi?id=27827
Summary: commit 745c4b568573fd5353e0f790251af64098742b1a causes
problems and system lockups
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
On Sat, Apr 24, 2010 at 8:01 AM, Marek Olšák wrote:
> On Tue, Apr 20, 2010 at 10:31 AM, Jerome Glisse
> wrote:
>>
>> As r300g has never been used as a production driver AFAIK i think
>> we could simply say that once it becomes such it will need at least
>> 2.6.34 kernel and thus avoid any fallbac
---
src/gallium/state_trackers/dri/common/dri_screen.h |5 +
src/gallium/state_trackers/dri/common/dri_st_api.c | 12 ++--
src/gallium/state_trackers/dri/drm/dri2.c |3 ++-
src/gallium/state_trackers/dri/drm/dri2.h |3 ---
4 files changed, 13 insertions(
---
.../state_trackers/dri/common/dri1_helper.c| 10 +-
.../state_trackers/dri/common/dri_context.c|1 -
.../state_trackers/dri/common/dri_drawable.c | 111 ++-
.../state_trackers/dri/common/dri_drawable.h |4 +
src/gallium/state_trackers/dri/common/d
---
.../state_trackers/dri/common/dri_context.c|2 +-
.../state_trackers/dri/common/dri_drawable.c |6 +--
.../state_trackers/dri/common/dri_drawable.h |7 ++--
src/gallium/state_trackers/dri/common/dri_st_api.c | 34 ++-
src/gallium/state_trackers
---
.../state_trackers/dri/common/dri_context.c| 15 +++--
.../state_trackers/dri/common/dri_context.h|2 +-
src/gallium/state_trackers/dri/common/dri_screen.c |6 +--
src/gallium/state_trackers/dri/common/dri_screen.h |6 +-
src/gallium/state_trackers/dri/common/dri_
---
.../state_trackers/dri/common/dri_drawable.c | 28 ++
.../state_trackers/dri/common/dri_drawable.h |6 ++
src/gallium/state_trackers/dri/common/dri_screen.h |7 +++
src/gallium/state_trackers/dri/common/dri_st_api.c | 36 +++--
src/gallium/state_trackers
The struct st_module isn't needed as it is the same thing as the st_api
struct. That is they both represent the API. Instead just use a single
function entry point to the the API.
---
src/gallium/include/state_tracker/st_api.h | 35 +++-
src/gallium/state_trackers/dri/com
Hi Chia-I et all
This Patch series does some minor refactoring in the st_api interface
and some major one to st/dri.
The first patch drops the st_module struct from st_api. This is because it
was overlapping the st_api struct. Both represent the API. It also drops some
extra symbols and instead j
On Tue, Apr 20, 2010 at 10:31 AM, Jerome Glisse wrote:
> As r300g has never been used as a production driver AFAIK i think
> we could simply say that once it becomes such it will need at least
> 2.6.34 kernel and thus avoid any fallback either in r300g or in
> gallium core.
>
The index_offset reg
On Thu, 2010-04-22 at 22:28 +0100, Jakob Bornecrantz wrote:
> +#define DEBUG_GET_ONCE_FLAGS_OPTION(sufix, name, flags, dfault) \
> +static unsigned long \
> +debug_get_option_ ## sufix (void) \
> +{ \
> + static boolean first = TRUE; \
> + unsigned long value; \
should be static
> + if (first
14 matches
Mail list logo
