Re: [Dri-devel] Re: Three proposed new generic DRM IOCTLs

2004-03-15 Thread Keith Whitwell
Michel DÃnzer wrote: On Sun, 2004-03-14 at 07:14, Jon Smirl wrote: This is a first pass at the three new IOCTL patch. It is against the DRM copy in the Mesa tree. And exactly why does that still exist? I know you don't listen to me, but I don't think you can ignore Keith. If there's any reason

[Dri-devel] Re: Three proposed new generic DRM IOCTLs

2004-03-14 Thread Jon Smirl
This is a better patch for the three proposed IOCTLs. 1) Fixes a merge bug that made the first one segfault 2) Plays nice with framebuffer. If framebuffer is found DRM will revert to stealth mode and disable the new features. 3) Compiles and works on 2.4. New features are disabled on 2.4 but with

[Dri-devel] Re: Three proposed new generic DRM IOCTLs

2004-03-14 Thread Michel Dänzer
On Sun, 2004-03-14 at 07:14, Jon Smirl wrote: > This is a first pass at the three new IOCTL patch. > > It is against the DRM copy in the Mesa tree. And exactly why does that still exist? I know you don't listen to me, but I don't think you can ignore Keith. > 2) It uses the kernel to bind the

Re: [Dri-devel] Re: Three proposed new generic DRM IOCTLs

2004-03-13 Thread Jon Smirl
This is a first pass at the three new IOCTL patch. It is against the DRM copy in the Mesa tree. Building DRM from mesa works fine. It includes the radeon mode setting IOCTL. 1) It is 2.6 only since it has sysfs and hotplug support. I will need to add ifdef's to remove these on 2.4. 2) It uses the

[Dri-devel] Re: Three proposed new generic DRM IOCTLs

2004-03-13 Thread Michel Dänzer
On Sat, 2004-03-13 at 17:35, Jon Smirl wrote: > --- Michel Dnzer <[EMAIL PROTECTED]> wrote: > > On Sat, 2004-03-13 at 04:54, Jon Smirl wrote: > > > > > > A fourth call will be a driver specific call for setting the video mode. I > > am > > > implementing this by completely computing the register v

Re: [Dri-devel] Re: Three proposed new generic DRM IOCTLs

2004-03-13 Thread Alan Cox
On Sad, 2004-03-13 at 16:35, Jon Smirl wrote: > Yes. Big chunks of Benh's driver and the mode parts of fb can easily be moved to > user space. It only took a couple of days. Mode setting code is seldom used as > compared to an interrupt handler, this gives the space back for more important > things

Re: [Dri-devel] Re: Three proposed new generic DRM IOCTLs

2004-03-13 Thread Jon Smirl
--- Michel Dänzer <[EMAIL PROTECTED]> wrote: > On Sat, 2004-03-13 at 04:54, Jon Smirl wrote: > > > > The code for the proposed IOCTLs is written and tested. They would be added > one > > at a time. > > Do you have a patch for us to look at? I'll start sending the patches out if everyone is ok w

[Dri-devel] Re: Three proposed new generic DRM IOCTLs

2004-03-13 Thread Michel Dänzer
On Sat, 2004-03-13 at 04:54, Jon Smirl wrote: > > The code for the proposed IOCTLs is written and tested. They would be added one > at a time. Do you have a patch for us to look at? > 3) BLANK - simple call to allow Vesa power management to blank the display. > > A fourth call will be a drive