> I'll try it out as soon as there is time.

I've just tested glxgears and a few mesa tests on it and it seems to
be working fine....

We should probably think about pulling this over into the DRM sooner
rather than later, there are also some changes to the DDX
i830_driver.c compat code to deal with...


> BTW what rules should we use for scalar types in drm?
>
> I assume "unsigned", "int", "unsigned long" etc are OK when no specific
> size is needed in kernel code?
> "u32" and similar can be used in linux-only kernel code. In shared code
> we use "uint32_t" and similar?
> "__u32" is used in linux-only user-space interface code. What about
> shared interface code?  "unsigned"? "uint32_t"?
>

I'd rather not use unsigned or unsigned long ever, unsigned int is
well defined IMHO, unsigned i feel isn't informative enough and
unsigned long or void * is just a bad idea for 32/64bit so to be
avoided at all costs...

So I guess we use unsigned int and uint32_t in any many places as we
can I think we need to add an include to drm.h for uint32_t to work in
it.. the kernel people might give out a bit, but I'm quite happy to
standover using uint32_t and friends..

Dave.

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to