mesa/src/gallium
Ilia Mirkin 89c5b56be6 nouveau: fix firmware check on nvd7/nvd9
The kernel driver expects the class to be based on chipset generation
rather than VP generation. Make sure to pass 90b1 for NVDX chipsets
instead of 95b1.

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=77102
Fixes: 40dd777b33
Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: "10.1 10.0" <mesa-stable@lists.freedesktop.org>
Reviewed-by: Maarten Lankhorst <maarten.lankhorst@ubunutu.com>
2014-04-07 08:58:15 -04:00
..
auxiliary gallium: add support for LODQ opcodes. 2014-04-07 01:06:18 -04:00
docs gallium: add support for LODQ opcodes. 2014-04-07 01:06:18 -04:00
drivers nouveau: fix firmware check on nvd7/nvd9 2014-04-07 08:58:15 -04:00
include gallium: add support for LODQ opcodes. 2014-04-07 01:06:18 -04:00
state_trackers clover: Document that the *obj*() helpers already take care of object validation. 2014-04-05 12:18:29 +02:00
targets automake: don't enable -Wl,--no-undefined on OpenBSD 2014-04-05 13:30:27 +01:00
tests automake: introduce GALLIUM_COMMON_LIB_DEPS 2014-04-05 13:00:02 +01:00
tools gallium: allow setting of the internal stream output offset 2014-03-07 12:49:33 -05:00
winsys winsys/svga: Fix prime surface references also for guest-backed surfaces 2014-04-07 03:34:52 -07:00
Android.common.mk android: build gallium auxiliaries 2011-08-21 02:01:48 +08:00
Android.mk Move nv30, nv50 and nvc0 to nouveau. 2013-09-11 21:47:07 +02:00
Automake.inc automake: don't enable -Wl,--no-undefined on OpenBSD 2014-04-05 13:30:27 +01:00
README.portability
SConscript haiku libGL: Move from gallium target to src/hgl 2014-01-06 15:50:21 -06:00

	      CROSS-PLATFORM PORTABILITY GUIDELINES FOR GALLIUM3D 


= General Considerations =

The state tracker and winsys driver support a rather limited number of
platforms. However, the pipe drivers are meant to run in a wide number of
platforms. Hence the pipe drivers, the auxiliary modules, and all public
headers in general, should strictly follow these guidelines to ensure


= Compiler Support =

* Include the p_compiler.h.

* Don't use the 'inline' keyword, use the INLINE macro in p_compiler.h instead.

* Cast explicitly when converting to integer types of smaller sizes.

* Cast explicitly when converting between float, double and integral types.

* Don't use named struct initializers.

* Don't use variable number of macro arguments. Use static inline functions
instead.

* Don't use C99 features.

= Standard Library =

* Avoid including standard library headers. Most standard library functions are
not available in Windows Kernel Mode. Use the appropriate p_*.h include.

== Memory Allocation ==

* Use MALLOC, CALLOC, FREE instead of the malloc, calloc, free functions.

* Use align_pointer() function defined in u_memory.h for aligning pointers
 in a portable way.

== Debugging ==

* Use the functions/macros in p_debug.h.

* Don't include assert.h, call abort, printf, etc.


= Code Style =

== Inherantice in C ==

The main thing we do is mimic inheritance by structure containment.

Here's a silly made-up example:

/* base class */
struct buffer
{
  int size;
  void (*validate)(struct buffer *buf);
};

/* sub-class of bufffer */
struct texture_buffer
{
  struct buffer base;  /* the base class, MUST COME FIRST! */
  int format;
  int width, height;
};


Then, we'll typically have cast-wrapper functions to convert base-class 
pointers to sub-class pointers where needed:

static inline struct vertex_buffer *vertex_buffer(struct buffer *buf)
{
  return (struct vertex_buffer *) buf;
}


To create/init a sub-classed object:

struct buffer *create_texture_buffer(int w, int h, int format)
{
  struct texture_buffer *t = malloc(sizeof(*t));
  t->format = format;
  t->width = w;
  t->height = h;
  t->base.size = w * h;
  t->base.validate = tex_validate;
  return &t->base;
}

Example sub-class method:

void tex_validate(struct buffer *buf)
{
  struct texture_buffer *tb = texture_buffer(buf);
  assert(tb->format);
  assert(tb->width);
  assert(tb->height);
}


Note that we typically do not use typedefs to make "class names"; we use
'struct whatever' everywhere.

Gallium's pipe_context and the subclassed psb_context, etc are prime examples 
of this.  There's also many examples in Mesa and the Mesa state tracker.