From: Greg KH <greg@kroah.com>
To: David Airlie <airlied@linux.ie>
Cc: dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Thomas Hellstrom <thellstrom@vmware.com>,
Richard Purdie <rpurdie@linux.intel.com>
Subject: [patch 0/5] Intel Poulsbo/Morrestown DRM driver and DRM core changes
Date: Wed, 18 Mar 2009 21:08:09 -0700 [thread overview]
Message-ID: <20090319040809.GA29249@kroah.com> (raw)
Hi,
Here's 5 patches that add the Intel Poulsbo/Morrestown DRM driver to the
kernel tree.
There are 4 patches that make changes to the DRM core, and one patch
that adds the DRM driver itself. The driver is added to the
drivers/staging/ directory because it is not the "final" driver that
Intel wishes to support over time. The userspace api is going to
change, and work is currently underway to hook up properly with the
memory management system.
However this work is going to take a while, and in the meantime, users
want to run Linux on this kind of hardware. I'd really like to add the
driver to the staging tree, but it needs these core DRM changes in order
to get it to work properly.
Originally I had a patch that basically duplicated the existing DRM
core, and embedded it with these changes and the PSB driver together
into one big mess of a kernel module. But Richard convinced me that
this wasn't the "nicest" thing to do, and he did work on the PSB code
and dug out these older DRM patches.
The only thing that looks a bit "odd" to me is the unlocked ioctl patch,
Thomas, is that thing really correct?
David, I'd be glad to take the DRM changes through the staging tree, but
only if you ack them.
thanks,
greg k-h
next reply other threads:[~2009-03-19 4:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090319035834.875839585@mini.kroah.org>
2009-03-19 4:08 ` Greg KH [this message]
2009-03-19 4:08 ` [patch 1/5] drm: Split out the mm declarations in a separate header. Add atomic operations Greg KH
2009-03-19 4:08 ` [patch 4/5] drm: Add unlocked IOCTL functionality from the drm repo Greg KH
2009-03-19 4:08 ` [patch 3/5] drm: Export hash table functionality Greg KH
2009-03-19 4:08 ` [patch 2/5] drm: Add a tracker for global objects Greg KH
2009-03-19 6:48 ` [patch 0/5] Intel Poulsbo/Morrestown DRM driver and DRM core changes Dave Airlie
2009-03-19 10:14 ` Thomas Hellström
2009-03-19 10:39 ` Alan Cox
2009-03-19 20:13 ` Greg KH
2009-03-19 20:11 ` Greg KH
2009-03-19 20:40 ` Thomas Hellström
2009-03-20 0:23 ` Greg KH
2009-03-20 14:17 ` Thomas Hellström
2009-03-19 10:43 ` Richard Purdie
2009-03-19 20:10 ` Greg KH
2009-03-19 16:03 ` Sindhudweep Sarkar
2009-03-19 16:27 ` Greg KH
2009-03-19 18:11 ` Sindhudweep Sarkar
2009-03-19 20:14 ` Greg KH
2009-03-19 18:53 ` Matthew Garrett
2009-03-19 19:02 ` Greg KH
2009-03-19 19:05 ` Matthew Garrett
2009-03-19 19:20 ` Greg KH
2009-03-20 6:08 ` Daniel Stone
2009-03-20 14:53 ` Greg KH
2009-03-20 15:00 ` Alan Cox
2009-03-20 15:50 ` Greg KH
2009-03-20 16:59 ` Thomas Hellström
2009-03-19 17:12 ` Richard Purdie
2009-03-19 20:15 ` Corbin Simpson
2009-03-19 21:14 ` Sindhudweep Sarkar
2009-03-21 2:39 ` Greg KH
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=20090319040809.GA29249@kroah.com \
--to=greg@kroah.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@linux.intel.com \
--cc=thellstrom@vmware.com \
/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