public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas@shipmail.org>
To: Greg KH <greg@kroah.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Thomas Hellstrom <thellstrom@vmware.com>,
	David Airlie <airlied@linux.ie>,
	linux-kernel@vger.kernel.org, Daniel Stone <daniel@fooishbar.org>,
	Richard Purdie <rpurdie@linux.intel.com>,
	Sindhudweep Sarkar <sindhudweep.sarkar@gmail.com>,
	dri-devel@lists.sourceforge.net
Subject: Re: [patch 0/5] Intel Poulsbo/Morrestown DRM driver and DRM core changes
Date: Fri, 20 Mar 2009 17:59:52 +0100	[thread overview]
Message-ID: <49C3CB88.2000202@shipmail.org> (raw)
In-Reply-To: <20090320155010.GA13556@kroah.com>

Greg KH wrote:
> On Fri, Mar 20, 2009 at 03:00:32PM +0000, 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 convinced this is any different. If you accept the 3D changes you
>> step into a dangerous world of estoppel and since it has many
>> rightsholders also the wonderful world of contributory infringement. It
>> really really needs lawyers to look into it.
>>     
>
> I would hope that Intel's lawyers would have done such a thing before
> releasing the kernel and xorg code under the licenses that they did :)
>
>   
>> Now the other way to do it that might be more productive and simpler
>> would be to rip all the 3D crap out of that driver and just include the
>> minimum needed 2D bits for the open source X driver. Makes the code
>> smaller and cleaner, avoids an legal questions and lets people get on
>> with real work.
>>     
>
> Hm, that sounds fine to me.
>
> Does that mean that all of these drm patches that I posted are _only_
> needed for the 3d portions of the driver?  If I rip out the portions of
> the psb kernel driver that need these changes, do I end up with an
> working 2d driver as well?  Richard and Thomas, any thoughts here?
>
> thanks,
>
> greg k-h
>
>   
Greg,
Let's not forget the video stuff. I'm not sure about the status of that.

But all the other patches are needed for 2D functionality and kernel 
modesetting.
If you want to strip 3D you can strip.

psb_schedule.[ch] - The 3D scheduler.
psb_xhw.c - The interface to the binary X server module.
psb_scene.c - The 3D scene tracker.

and anything that appears unused after that.
This means you lose Render acceleration and textured video and 
downscaling in the X server as well,
although accelerated rotation should still work, since it uses the 2D 
engine.

I think the video acceleration sits in

psb_msvdx.c
psb_msvdxinit.c
lnc_topaz.c
lnc_topazinit.c

/Thomas




  reply	other threads:[~2009-03-20 17:01 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
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 [this message]
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=49C3CB88.2000202@shipmail.org \
    --to=thomas@shipmail.org \
    --cc=airlied@linux.ie \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=daniel@fooishbar.org \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=greg@kroah.com \
    --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