On Sun, Feb 20, 2011 at 10:23:18PM +0100, Enrico Weigelt wrote:
> * Dave Airlie schrieb:
>
> > The proper way is to design ioctls so compat layers aren't needed, to work
> > across all 32/64 combos, so that means using 64-bit aligned types as much
> > as possible, and padding to make sure 64-bit
* Dave Airlie schrieb:
> The proper way is to design ioctls so compat layers aren't needed, to work
> across all 32/64 combos, so that means using 64-bit aligned types as much
> as possible, and padding to make sure 64-bit types don't end up unaligned.
Until, in several years, pointers get large
On Mon, Feb 7, 2011 at 9:42 AM, Casey Dahlin wrote:
> On Mon, Feb 07, 2011 at 07:28:35AM +1000, Dave Airlie wrote:
>>
>> We then use libdrm in userspace to abstract away the internal details
>> of the interface,
>> you shouldn't ever be directly talking to drm ioctls.
>>
>
> I'll take this moment
On Mon, Feb 07, 2011 at 07:28:35AM +1000, Dave Airlie wrote:
>
> We then use libdrm in userspace to abstract away the internal details
> of the interface,
> you shouldn't ever be directly talking to drm ioctls.
>
I'll take this moment to point out that, while its no excuse to go using them,
libd
On 02/06/2011 04:28 PM, Dave Airlie wrote:
> On Mon, Feb 7, 2011 at 6:48 AM, Marty Jack wrote:
>> Well, I have over 40 years experience, a lot of it on Unix and more recently
>> Linux and a lot of it doing compilers, so data typing is second nature.
>>
>> But, I'm getting a little older, I coul
On Feb 6, 2011, at 3:17 PM, Dave Airlie wrote:
>>
>> (It is also a great pity that whoever designed the modesetting ioctls
>> thought _u64 was a good type for all the pointer values. Whoever designed
>> the original ioctls used pointer types very successfully.)
>
> Why would you consider yours
On Mon, Feb 7, 2011 at 6:48 AM, Marty Jack wrote:
> Well, I have over 40 years experience, a lot of it on Unix and more recently
> Linux and a lot of it doing compilers, so data typing is second nature.
>
> But, I'm getting a little older, I could be mistaken and I'm always happy to
> learn some
Well, I have over 40 years experience, a lot of it on Unix and more recently
Linux and a lot of it doing compilers, so data typing is second nature.
But, I'm getting a little older, I could be mistaken and I'm always happy to
learn something new. Maybe sometime when you have a moment you would
>
> (It is also a great pity that whoever designed the modesetting ioctls thought
> _u64 was a good type for all the pointer values. Whoever designed the
> original ioctls used pointer types very successfully.)
Why would you consider yourself even remotely qualified to make such
a statement? i
I spent the weekend learning my way around and debugging the DRM compositor
running on bare hardware. Successful, but some issues and observations.
As is documented, you need to make sure you have your video and input devices
labelled with the udev property WAYLAND_SEAT="1". I have
10 matches
Mail list logo
