public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: Ian Romanick <idr@us.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	"DRI developer's list" <dri-devel@lists.sourceforge.net>
Subject: Re: DRM code reorganization
Date: Mon, 2 Aug 2004 22:09:35 +0100	[thread overview]
Message-ID: <20040802210935.GF12724@redhat.com> (raw)
In-Reply-To: <20040802204204.88994.qmail@web14926.mail.yahoo.com>

On Mon, Aug 02, 2004 at 01:42:04PM -0700, Jon Smirl wrote:
 > We are really short handed for kernel level DRM developers; most 3D
 > developers work in user space. The main person that wrote it, Gareth
 > Hughes, doesn't seem to work on it any more. Right now there are three
 > to four, non-paid people working part-time on DRM. 
 > 
 > How about you kernel developers working in other areas giving us a hand
 > with reorganizing the DRM code? You don't need to know anything about
 > 3D you would just be reworking the code without changing how it
 > functions.

Whip me, beat me, make me clean up drivers/char/drm

8-)

Seriously, it's not a fun job at all, so finding volunteers may be
somewhat difficult, but for someone with a high pain threshold, it might
be fun[1], but as Ian mentioned, it depends on the payoff.  If subsequent
DRI tree -> kernel merges back out any cleanup work, it's definitly going
to be a waste of time even trying.

Additionally, assuming some grand cleanup happens. Going back the other way
(keeping stuff in the DRI tree up to date with whatever kernel changes were
 made) is going to prove interesting. In short, I'd not expect other OS's to
work out-of-the-box until someone put in the legwork to make them adapt
to whatever changes were made.

Another possibility of course is that the BSD & Linux kernel side bits
go their seperate ways. How active is the kernel side of the BSD world ?

		Dave

[1] Well, fun perhaps for the same sort of person who enjoyed pulling legs
    off of insects as a child, to see if it still wiggles.


  reply	other threads:[~2004-08-02 21:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-02 15:53 DRM code reorganization Jon Smirl
2004-08-02 18:02 ` Ian Romanick
2004-08-02 18:27   ` Keith Whitwell
2004-08-02 18:57   ` Dave Jones
2004-08-02 18:16     ` Alan Cox
2004-08-02 20:11     ` Ian Romanick
2004-08-02 20:42       ` Jon Smirl
2004-08-02 21:09         ` Dave Jones [this message]
2004-08-02 21:51           ` Michel Dänzer
2004-08-02 23:09           ` Jon Smirl
2004-08-02 23:24           ` Alan Cox
2004-08-02 20:45       ` Dave Jones
2004-08-02 23:53         ` Ian Romanick
2004-08-03  7:52           ` Keith Whitwell
2004-08-03 16:28             ` Ian Romanick
2004-08-03 16:49               ` Keith Whitwell
2004-08-03  0:06     ` Dave Airlie
2004-08-03  6:13     ` Eric Anholt
2004-08-02 23:48   ` Dave Airlie
2004-08-02 23:26     ` Alan Cox

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=20040802210935.GF12724@redhat.com \
    --to=davej@redhat.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=idr@us.ibm.com \
    --cc=jonsmirl@yahoo.com \
    --cc=linux-kernel@vger.kernel.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