On Wed, Mar 18, 2009 at 09:08:09PM -0700, Greg KH wrote:
> Hi,
>
> Here's 5 patches that add the Intel Poulsbo/Morrestown DRM driver to the
> kernel tree.
Ok, in reviewing the issues that Alan rightfully brought up, I'm going
to "retract" these patches right now and go back and try to only get th
Greg KH wrote:
> On Fri, Mar 20, 2009 at 03:00:32PM +, Alan Cox wrote:
>
By the same logic, would you support including the proprietary NVIDIA
driver while we wait for Nouveau to catch up?
>>> The license of the NVIDIA driver does not allow that to even be a
>>> possi
On Fri, Mar 20, 2009 at 03:00:32PM +, Alan Cox wrote:
> > > By the same logic, would you support including the proprietary NVIDIA
> > > driver while we wait for Nouveau to catch up?
> >
> > The license of the NVIDIA driver does not allow that to even be a
> > possibility.
>
> I'm not convince
On Fri, Mar 20, 2009 at 05:08:23PM +1100, Daniel Stone wrote:
> Greg,
>
> On Thu, Mar 19, 2009 at 09:27:19AM -0700, Greg KH wrote:
> > On Thu, Mar 19, 2009 at 12:03:09PM -0400, Sindhudweep Sarkar wrote:
> > > TI-OMAP 3xxx and a couple of other arm processors use similar SGX-5xx
> > > graphics core
> > By the same logic, would you support including the proprietary NVIDIA
> > driver while we wait for Nouveau to catch up?
>
> The license of the NVIDIA driver does not allow that to even be a
> possibility.
I'm not convinced this is any different. If you accept the 3D changes you
step into a da
On Thu, Mar 19, 2009 at 10:39:03AM +, Alan Cox wrote:
> > The non-existence of an open-source 3D implementation doesn't really
> > alter that situation.
>
> I think it does to an extent
With an opensource 2d solution it does?
> > However, if there's a policy issue about adding Linux kernel
On Thu, Mar 19, 2009 at 11:14:35AM +0100, Thomas Hellström wrote:
>> First off, the non-staging patches need more complete changelog entries,
>> a bit of meaning goes a long way. I'll ack them if they are documented and
>> make sense. The unlocked ioctl hook makes sense to me at least!
>>
>
> Fo
On Thu, Mar 19, 2009 at 12:02:54PM -0700, Greg KH wrote:
> On Thu, Mar 19, 2009 at 06:53:38PM +, Matthew Garrett wrote:
> > On Thu, Mar 19, 2009 at 09:27:19AM -0700, Greg KH wrote:
> >
> > > But how do I get my laptop that I currently have right now up and
> > > running properly with linux in
On Thu, Mar 19, 2009 at 04:48:54PM +1000, Dave Airlie wrote:
> On Thu, Mar 19, 2009 at 2:08 PM, Greg KH wrote:
> > 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
> >
On Thu, Mar 19, 2009 at 09:40:08PM +0100, Thomas Hellström wrote:
> Greg KH wrote:
>> On Thu, Mar 19, 2009 at 11:14:35AM +0100, Thomas Hellström wrote:
>>
First off, the non-staging patches need more complete changelog entries,
a bit of meaning goes a long way. I'll ack them if they ar
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
On Thu, Mar 19, 2009 at 09:27:19AM -0700, Greg KH wrote:
> 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?
You don't, because there's no working X driver.
--
Matthew Garrett | mj...@srcf.ucam.org
---
> Nokia's written and open-sourced some related code for DRM.
>
> My university is paying me to work on an ARM-based SoC handheld with an
> SGX core, and I might be more into this later. (Y'know, once the device
> is actually out the door.)
>
> ~ C.
>
Could you point me to the aforementioned open-
Greg,
On Thu, Mar 19, 2009 at 09:27:19AM -0700, Greg KH wrote:
> On Thu, Mar 19, 2009 at 12:03:09PM -0400, Sindhudweep Sarkar wrote:
> > 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 b
Greg KH wrote:
> On Thu, Mar 19, 2009 at 11:14:35AM +0100, Thomas Hellström wrote:
>
>>> First off, the non-staging patches need more complete changelog entries,
>>> a bit of meaning goes a long way. I'll ack them if they are documented and
>>> make sense. The unlocked ioctl hook makes sense to
Richard Purdie wrote:
> On Thu, 2009-03-19 at 12:03 -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.
>>
>> TI-OMAP 3xxx and a couple
On Thu, Mar 19, 2009 at 06:53:38PM +, Matthew Garrett wrote:
> On Thu, Mar 19, 2009 at 09:27:19AM -0700, Greg KH wrote:
>
> > 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?
>
> You don't, because the
On Thu, Mar 19, 2009 at 07:05:30PM +, Matthew Garrett wrote:
> On Thu, Mar 19, 2009 at 12:02:54PM -0700, Greg KH wrote:
> > On Thu, Mar 19, 2009 at 06:53:38PM +, Matthew Garrett wrote:
> > > On Thu, Mar 19, 2009 at 09:27:19AM -0700, Greg KH wrote:
> > >
> > > > But how do I get my laptop t
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
On Thu, 2009-03-19 at 12:03 -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.
>
> TI-OMAP 3xxx and a couple of other arm processors us
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 co
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.
TI-OMAP 3xxx and a couple of other arm processors use similar SGX-5xx
graphics cores. IIRC arm is often little endian so per
Hi,
On Thu, 2009-03-19 at 16:48 +1000, Dave Airlie wrote:
> First off, the non-staging patches need more complete changelog entries,
> a bit of meaning goes a long way. I'll ack them if they are documented and
> make sense. The unlocked ioctl hook makes sense to me at least!
>
> Now the non-core D
> The non-existence of an open-source 3D implementation doesn't really
> alter that situation.
I think it does to an extent
>
> However, if there's a policy issue about adding Linux kernel support for
> closed-source user-space drivers, I think it helps to be explicit about
> that.
Actually i
Dave and Greg,
Some quick comments below.
Dave Airlie wrote:
> On Thu, Mar 19, 2009 at 2:08 PM, Greg KH wrote:
>
>> 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
>>
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 wi
On Thu, Mar 19, 2009 at 2:08 PM, Greg KH wrote:
> 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/stagin
27 matches
Mail list logo
