From: Greg KH <greg@kroah.com>
To: Sindhudweep Sarkar <sindhudweep.sarkar@gmail.com>
Cc: David Airlie <airlied@linux.ie>,
dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Thomas Hellstrom <thellstrom@vmware.com>,
Richard Purdie <rpurdie@linux.intel.com>
Subject: Re: [patch 0/5] Intel Poulsbo/Morrestown DRM driver and DRM core changes
Date: Thu, 19 Mar 2009 09:27:19 -0700 [thread overview]
Message-ID: <20090319162719.GB32078@kroah.com> (raw)
In-Reply-To: <6c046ab30903190903r298a0334n939e64403b8aeda6@mail.gmail.com>
On Thu, Mar 19, 2009 at 12:03:09PM -0400, Sindhudweep Sarkar wrote:
> This might be the opinion of a completely non educated end user but it
> seems that an intel specific drm and other bits (xorg, mesa) would be
> somewhat of a maintenance waste.
What do you mean by this?
> TI-OMAP 3xxx and a couple of other arm processors use similar SGX-5xx
> graphics cores. IIRC arm is often little endian so perhaps a unified
> driver would be easier in the long term.
Long term lots of things are good.
But how do I get my laptop that I currently have right now up and
running properly with linux in a better-than-800x600-framebuffer mode?
That's why I need/want this driver now, there are hundreds of thousands
of these types of laptops in the pipeline to users and I want them to
run Linux, not be forced to run some other operating system...
thanks,
greg k-h
next prev parent reply other threads:[~2009-03-19 16:28 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
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 [this message]
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=20090319162719.GB32078@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=sindhudweep.sarkar@gmail.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
all inboxes | Powered by JetHome®