public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Anholt <eta@lclark.edu>
To: Keith Whitwell <keith@tungstengraphics.com>
Cc: Jon Smirl <jonsmirl@gmail.com>,
	Discuss issues related to the xorg tree  <xorg@freedesktop.org>,
	DRI <dri-devel@lists.sourceforge.net>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: New DRM driver model - gets rid of DRM() macros!
Date: Wed, 29 Sep 2004 17:00:40 -0700	[thread overview]
Message-ID: <1096502440.16006.3.camel@leguin> (raw)
In-Reply-To: <415AC5C2.9030707@tungstengraphics.com>

On Wed, 2004-09-29 at 07:25, Keith Whitwell wrote:
> Jon Smirl wrote:
> >
> > Drivers provide these callbacks......
> > 
> > struct drm_driver_fn {
> >        u32 driver_features;
> >        int dev_priv_size;
> >        int permanent_maps;
> >        drm_ioctl_desc_t *ioctls;
> >        int num_ioctls;
> 
> >        int (*preinit)(struct drm_device *, unsigned long flags);
> >        void (*prerelease)(struct drm_device *, struct file *filp);
> >        void (*pretakedown)(struct drm_device *);
> >        int (*postcleanup)(struct drm_device *);
> >        int (*presetup)(struct drm_device *);
> >        int (*postsetup)(struct drm_device *);
> >        int (*dma_ioctl)( DRM_IOCTL_ARGS );
> >        /* these are opposites at the moment */
> >        int (*open_helper)(struct drm_device *, drm_file_t *);
> >        void (*free_filp_priv)(struct drm_device *, drm_file_t *);
> 
> >        void (*release)(struct drm_device *, struct file *filp);
> >        void (*dma_ready)(struct drm_device *);
> 
> Is this used by any driver?
> 
> >        int (*dma_quiescent)(struct drm_device *);
> 
> >        int (*context_ctor)(struct drm_device *dev, int context);
> >        int (*context_dtor)(struct drm_device *dev, int context);
> >        int (*kernel_context_switch)(struct drm_device *dev, int old, int new);
> >        int (*kernel_context_switch_unlock)(struct drm_device *dev);
> 
> The whole context thing in the kernel is pretty much cruft.  The gamma module 
> used to rely on it, maybe the ffb module if that still exists?  It would be 
> good to see this disappear.
> 
> Though the drivers don't rely on it, I don't know if the server-side code 
> persists in setting it up regardless, which might make it hard to get rid of.

SiS relies on context ctor/dtor (dtor only, when I'm done) for its
kernel memory manager.

-- 
Eric Anholt                                eta@lclark.edu          
http://people.freebsd.org/~anholt/         anholt@FreeBSD.org



  reply	other threads:[~2004-09-30  0:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 15:54 New DRM driver model - gets rid of DRM() macros! Jon Smirl
2004-09-28 16:56 ` Ian Romanick
2004-09-28 17:28   ` Jon Smirl
2004-09-28 19:35   ` Helge Hafting
2004-09-28 23:10 ` Dave Airlie
2004-09-29  1:27   ` Jon Smirl
2004-09-29  2:11     ` Dave Airlie
2004-09-29  5:25       ` Jon Smirl
2004-09-29 12:37 ` Christoph Hellwig
2004-09-29 11:59   ` Alan Cox
2004-09-29 13:16     ` Dave Airlie
2004-09-29 13:29   ` Keith Whitwell
2004-09-29 13:31     ` Christoph Hellwig
2004-09-29 13:35       ` Keith Whitwell
2004-09-29 14:12         ` Keith Whitwell
2004-09-29 14:16           ` Christoph Hellwig
2004-09-29 14:27             ` Keith Whitwell
2004-09-29 14:39               ` Keith Whitwell
2004-09-29 19:16                 ` Keith Packard
2004-09-30 18:10         ` Jon Smirl
2004-09-29 13:41   ` Dave Airlie
2004-10-01  5:15   ` Jon Smirl
2004-09-29 14:25 ` Keith Whitwell
2004-09-30  0:00   ` Eric Anholt [this message]
2004-09-29 21:52 ` Felix Kühling
2004-09-29 21:02   ` Alan Cox
2004-09-29 23:25   ` Jon Smirl
     [not found]     ` <20041006133714.GA26860@localdomain>
     [not found]       ` <9e47339104100609307307f8ea@mail.gmail.com>
     [not found]         ` <20041006211922.GA5167@localdomain>
2004-10-06 21:46           ` Code status (Was: New DRM driver model - gets rid of DRM() macros!) Ian Romanick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1096502440.16006.3.camel@leguin \
    --to=eta@lclark.edu \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=jonsmirl@gmail.com \
    --cc=keith@tungstengraphics.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xorg@freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox