On Wed, 12 May 2004, Ian Romanick wrote:
Or is the installed 64-bit user base small enough that we
can make them take one for the team, so to speak?
With cheap 64-bit processors coming out from AMD and
Intel the base is growing faster than ever, so better
get on with it yesterday :)
Or is the installed 64-bit user base small enough that we
can make them take one for the team, so to speak?
With cheap 64-bit processors coming out from AMD and
Intel the base is growing faster than ever, so better
get on with it yesterday :)
--j
with that in mind I'll
Linus Torvalds writes:
On Wed, 12 May 2004, Dave Airlie wrote:
I just looked at drm.h and nearly all the ioctls use int, this file is
included in user-space applications also at the moment, I'm worried
changing all ints to __u32 will break some of these, anyone on DRI list
On Tue, May 11, 2004 at 08:07:09PM -0400, Daniel Jacobowitz wrote:
On Tue, May 11, 2004 at 04:43:29PM -0700, Greg KH wrote:
On Tue, May 11, 2004 at 07:34:39PM -0400, [EMAIL PROTECTED] wrote:
On Wed, 12 May 2004 00:20:51 BST, Dave Airlie said:
I just looked at drm.h and nearly all the
On Tue, May 11, 2004 at 07:34:39PM -0400, [EMAIL PROTECTED] wrote:
On Wed, 12 May 2004 00:20:51 BST, Dave Airlie said:
I just looked at drm.h and nearly all the ioctls use int, this file is
included in user-space applications also at the moment, I'm worried
changing all ints to __u32 will
On Tue, May 11, 2004 at 06:07:27PM -0700, Jon Smirl wrote:
Would int16_t and int32_t work?
No, sorry. See the lkml archives for why.
Those int's were in there before I started working on it. __u16 and
__u32 are Linux kernel defines that aren't always there in user space.
Don't share header
On Wed, 12 May 2004 00:20:51 BST, Dave Airlie said:
I just looked at drm.h and nearly all the ioctls use int, this file is
included in user-space applications also at the moment, I'm worried
changing all ints to __u32 will break some of these, anyone on DRI list
care to comment?
Is this a
On Tue, May 11, 2004 at 04:43:29PM -0700, Greg KH wrote:
On Tue, May 11, 2004 at 07:34:39PM -0400, [EMAIL PROTECTED] wrote:
On Wed, 12 May 2004 00:20:51 BST, Dave Airlie said:
I just looked at drm.h and nearly all the ioctls use int, this file is
included in user-space applications
Dave Airlie wrote:
Ick, you can't use int as an ioctl structure member, sorry. Please
use the proper __u16 or __u32 value instead.
I just looked at drm.h and nearly all the ioctls use int, this file is
included in user-space applications also at the moment, I'm worried
changing all ints to __u32
On Wed, 12 May 2004, Dave Airlie wrote:
I just looked at drm.h and nearly all the ioctls use int, this file is
included in user-space applications also at the moment, I'm worried
changing all ints to __u32 will break some of these, anyone on DRI list
care to comment?
Right now, all
Linus Torvalds wrote:
On Wed, 12 May 2004, Dave Airlie wrote:
I just looked at drm.h and nearly all the ioctls use int, this file is
included in user-space applications also at the moment, I'm worried
changing all ints to __u32 will break some of these, anyone on DRI list
care to comment?
Right
is the installed 64-bit user base small enough that we can make them take one
for the team, so to speak?
yeah I'm getting the feeling a flag day may be necessary
---
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up
On Tue, 2004-05-11 at 16:34, [EMAIL PROTECTED] wrote:
On Wed, 12 May 2004 00:20:51 BST, Dave Airlie said:
I just looked at drm.h and nearly all the ioctls use int, this file is
included in user-space applications also at the moment, I'm worried
changing all ints to __u32 will break some
Ick, you can't use int as an ioctl structure member, sorry. Please
use the proper __u16 or __u32 value instead.
I just looked at drm.h and nearly all the ioctls use int, this file is
included in user-space applications also at the moment, I'm worried
changing all ints to __u32 will break some
Would int16_t and int32_t work? Those int's were in there before I started
working on it. __u16 and __u32 are Linux kernel defines that aren't always there
in user space.
I would much rather have one h file than two. When we had two the variable and
structure names, comments, etc had drifted over
On Tuesday 11 May 2004 18:20, Dave Airlie wrote:
Ick, you can't use int as an ioctl structure member, sorry. Please
use the proper __u16 or __u32 value instead.
I just looked at drm.h and nearly all the ioctls use int, this file is
included in user-space applications also at the moment,
I would really like to keep a single h file for the IOCTL defines. There are
equivalent drm.h's, like radeon_drm.h, files for each of the drivers too. We
could make a user space wrapper that just 'typedef uint16_t __u16' for user
space and then includes the kernel version. Or we could write a
17 matches
Mail list logo
