From: Greg KH <greg@kroah.com>
To: Sindhudweep Sarkar <sindhudweep.sarkar@gmail.com>
Cc: linux-kernel@vger.kernel.org, David Airlie <airlied@linux.ie>,
dri-devel@lists.sourceforge.net,
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 13:14:04 -0700 [thread overview]
Message-ID: <20090319201404.GD17094@kroah.com> (raw)
In-Reply-To: <6c046ab30903191111y408a6c9g4cb392ad0331c011@mail.gmail.com>
On Thu, Mar 19, 2009 at 02:11:18PM -0400, Sindhudweep Sarkar wrote:
> Of course real support for poulsbo is really important and desirable
> since netbooks make such a huge percentage of computer sales these
> days. I'm guessing, however, that the number of
> embedded/mobile/appliance devices that use or will use the SGX5xx is
> much larger than even the plethora of netbooks being pumped out. If
> more hardware support can be gained for a little extra burden why not
> go for it? I would argue that a unified driver stack would actually
> have less maintenance cost since common bugs could be killed. Even
> ignoring all the arm devices that will use that graphics core, what
> about intel's own use of the SGX 535 elsewhere? Does this "poulsbo"
> driver support the intel CE3100 processors?
>
>
> I think i'm really apprehensive about device specific one-offs. Of
> course a mainline driver upstream is an important step to prevent that
> but without a roadmap it only seems marginally better.
Staging is all aobut "device specific one-offs". the code is then in a
common area where everyone can work to fix it up properly.
I don't want to burry this work again in random git trees that no one
has any clue how to put together, like has already been done in the
past.
thanks,
greg k-h
next prev parent reply other threads:[~2009-03-19 20:15 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 ` [patch 0/5] Intel Poulsbo/Morrestown DRM driver and DRM core changes 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
2009-03-19 18:11 ` Sindhudweep Sarkar
2009-03-19 20:14 ` Greg KH [this message]
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=20090319201404.GD17094@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