From: Jon Smirl <jonsmirl@yahoo.com>
To: Ian Romanick <idr@us.ibm.com>, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: [Dri-devel] Re: DRM reorganization
Date: Mon, 15 Mar 2004 16:42:54 -0800 (PST) [thread overview]
Message-ID: <20040316004254.18671.qmail@web14903.mail.yahoo.com> (raw)
In-Reply-To: <40564723.4010105@us.ibm.com>
--- Ian Romanick <idr@us.ibm.com> wrote:
> That's part of why I'm asking. From talking to Linus in the past, I
> know that merging in changes is a PITA due to our funky directory
> structure. I'd like to make that easier. :)
Part of the pain could be caused by the shared/linux split in the DRM tree. The
kernel tree doesn't have that split.
Also DRM makefile.kernel and the kernel char/drm/Makefile are similar but not
the same. So any changes to the build procedure would need to be updated into
char/drm/Makefile.
drmstat.c/dristat.c should be pulled out of the driver directory and put it in a
directory for apps.
Where should Doxyfile and config.in go?
The savage driver is not currently in the kernel. Should the mach64 driver be
moved out of the branch and into the DRM project?
The best solution would be to have some kind of scipt in the DRM project that
builds a directory that can simply be copied into char/drm.
=====
Jon Smirl
jonsmirl@yahoo.com
__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com
prev parent reply other threads:[~2004-03-16 0:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 22:15 Ian Romanick
2004-03-15 23:26 ` Andrew Morton
2004-03-15 23:51 ` [Dri-devel] " Alex Deucher
2004-03-16 0:15 ` Ian Romanick
2004-03-16 0:31 ` Andrew Morton
2004-03-16 19:21 ` Dave Jones
2004-03-16 0:42 ` Jon Smirl [this message]
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=20040316004254.18671.qmail@web14903.mail.yahoo.com \
--to=jonsmirl@yahoo.com \
--cc=akpm@osdl.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=idr@us.ibm.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
all inboxes | Powered by JetHome®