From: "Felix Kühling" <fxkuehl@gmx.de>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: dri-devel@lists.sourceforge.net, xorg@freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: New DRM driver model - gets rid of DRM() macros!
Date: Wed, 29 Sep 2004 23:52:38 +0200 [thread overview]
Message-ID: <20040929235238.46c55c58.felix@trabant> (raw)
In-Reply-To: <9e4733910409280854651581e2@mail.gmail.com>
On Tue, 28 Sep 2004 11:54:35 -0400
Jon Smirl <jonsmirl@gmail.com> wrote:
> I've checked two new directories into DRM CVS for Linux 2.6 -
> linux-core, shared-core. This code implements a new model for DRM
> where DRM is split into a core piece and personality modules that
> share the core. The major reason for doing this is that it allows me
> to remove all of the DRM() macros; something that is causing lot's of
> complaints from the Linux kernel people.
A single savage works just fine. This is lsmod output with X running:
Module Size Used by
savage 3520 0
drm 62500 3 savage
Is it normal that the savage module looks unused? I can actually rmmod
the savage module while X is running. After that direct rending fails
with some error message about permissions ... reloading savage didn't
help (of course, because X wouldn't reinitialize it). A bit later the
box locked up. Is this 0 usage count and the ability to rmmod the module
while X is running specific to the savage driver or do other drivers
show the same behaviour?
Some questions about future driver development: So the new linux-core
and shared-core are the place to do new driver development? If this is
correct then it will be for 2.6 kernels only, right? I suppose there
would some back-porting effort involved in getting a future savage
driver to work with 2.4 again (like adding back all the DRM() macros).
>
[snip]
> --
> Jon Smirl
> jonsmirl@gmail.com
| Felix Kühling <fxkuehl@gmx.de> http://fxk.de.vu |
| PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 |
next prev parent reply other threads:[~2004-09-29 21:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 15:54 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
2004-09-29 21:52 ` Felix Kühling [this message]
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=20040929235238.46c55c58.felix@trabant \
--to=fxkuehl@gmx.de \
--cc=dri-devel@lists.sourceforge.net \
--cc=jonsmirl@gmail.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
all inboxes | Powered by JetHome®