mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pekka Paalanen <pq@iki.fi>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Maarten Maathuis <madman2003@gmail.com>,
	Dave Airlie <airlied@linux.ie>,
	dri-devel@lists.sf.net, linux-kernel@vger.kernel.org,
	Xavier Bestel <xavier.bestel@free.fr>
Subject: Re: [git pull] drm
Date: Thu, 10 Dec 2009 21:49:48 +0200	[thread overview]
Message-ID: <20091210214948.3d3c958c@daedalus.pq.iki.fi> (raw)
In-Reply-To: <alpine.LFD.2.00.0912101035140.3560@localhost.localdomain>

On Thu, 10 Dec 2009 10:42:46 -0800 (PST)
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Thu, 10 Dec 2009, Maarten Maathuis wrote:
> > 
> > You assume that Red Hat has full control over the project,
> > which i don't think is the case. The reason it isn't in staging
> > yet (as far as i know) is because of some questions over the
> > copyright of some (essential) microcode. Either the question
> > needs to be answered, or it has to be reverse engineered to the
> > point that it's possible to generate it.
> 
> I think people are just making up excuses, as evidenced by the
> fact that you're quoting a different excuse than I've heard
> before.

That is because priorities change. The ABI has not seen changes
for some time now, so it's probably not an issue anymore. And it
is not an issue for staging. The other issue has become more
important. That said, there are features that likely require
revising the ABI at some point, and we know about those already.

> The fact is, if there are license questions, then Fedora had
> better not be distributing the code either. And they clearly are.

I've no idea how they pulled that, but I have not heard anyone
say that there are *no* legal issues at all.

> I've heard the "but it's hard to merge" excuse too - which I also
> know is bullshit, because I can look at the git tree Fedora
> apparently uses, and it merges without any conflicts what-so-ever.

No-one has said that about Nouveau, have they?

> The most common excuse is the "oh, but it might change" crap. But
> that's not even a very good excuse to start with, and it's what
> staging is for anyway.

Yes, and to my understanding Nouveau is past that excuse. People
just like to quote what they heard last.

The big question is what we call ctxprogs: binary blobs that are
clearly executable, running somewhere in the GPU. No-one seems
to know, if those are copyrightable, or if they can be redistributed.
In their current form, they have been recorded from the nvidia
proprietary driver using mmiotrace, and copied verbatim for each
card type.

Would you be willing to pull that kind of stuff into Linux?

I would not even dare sending them to the Linux firmware
repository, since they have some license requirements, too.

-- 
Pekka Paalanen
http://www.iki.fi/pq/

  parent reply	other threads:[~2009-12-10 19:49 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10  6:17 Dave Airlie
2009-12-10 15:17 ` Linus Torvalds
2009-12-10 15:40   ` Xavier Bestel
2009-12-10 16:24     ` Linus Torvalds
2009-12-10 17:40       ` Maarten Maathuis
2009-12-10 18:42         ` Linus Torvalds
2009-12-10 19:13           ` Pekka Enberg
2009-12-10 19:13           ` Robert Noland
2009-12-10 19:28           ` Alan Cox
2009-12-10 19:36           ` Jesse Barnes
2009-12-10 19:37           ` Dave Airlie
2009-12-10 19:45             ` Roland Dreier
2009-12-10 19:49           ` Pekka Paalanen [this message]
2009-12-10 20:35             ` Will Dyson
2009-12-10 21:12               ` Pekka Paalanen
2009-12-10 19:53           ` Stephane Marchesin
2009-12-10 23:37             ` Linus Torvalds
2009-12-10 23:50               ` Dave Airlie
2009-12-10 23:58               ` Alan Cox
2009-12-11  0:09                 ` Linus Torvalds
2009-12-11  0:20                   ` "C. Bergström"
2009-12-11  0:32                     ` Linus Torvalds
2009-12-11  0:47                       ` Dave Airlie
2009-12-11  1:34                       ` Kyle McMartin
2009-12-11  0:21                   ` Dave Airlie
2009-12-11  0:45                     ` Linus Torvalds
2009-12-11  9:18                   ` Alan Cox
2009-12-11  9:34                     ` David Miller
2009-12-11 10:15                       ` Andy Walls
2009-12-11 10:20                       ` Dave Airlie
2009-12-11 12:45                         ` tytso
2009-12-11 12:50                           ` Alan Cox
2009-12-11 10:28                     ` Jeff Garzik
2009-12-11 10:46                       ` Dave Airlie
2009-12-11 15:28                       ` Linus Torvalds
2009-12-11 17:49                         ` Jeff Garzik
2009-12-11 10:02                 ` Stephane Marchesin
2009-12-11 10:24                   ` Andy Walls
2009-12-10 16:47     ` Alan Cox
2009-12-10 21:49       ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2011-02-04  5:11 Dave Airlie
2010-02-11  4:20 Dave Airlie
2010-02-15  9:53 ` Christian Borntraeger
2010-02-15 20:12   ` Marcin Slusarz
2010-02-15 20:39     ` Maarten Maathuis
2010-02-15 22:13       ` Marcin Slusarz
2010-02-15 22:55   ` Christian Borntraeger
2010-02-16  1:19     ` Ben Skeggs
2010-02-16 11:39       ` Christian Borntraeger
2010-01-11  4:52 Dave Airlie
2009-09-29  3:52 Dave Airlie
2009-09-29  4:26 ` [git pull] drm Dave Airlie
2009-02-09  8:30 Dave Airlie
2009-01-07  1:59 Dave Airlie
2008-12-29  8:32 Dave Airlie
2009-01-04 19:19 ` Gabriel C
2009-01-10  2:03   ` Dave Airlie
2009-01-09 15:07 ` Richard Purdie
2009-01-09 18:03   ` Richard Purdie
2009-01-10  1:13     ` Richard Purdie
2009-01-10  2:04       ` Dave Airlie
2009-01-10  9:58         ` Richard Purdie
2009-01-10 23:04           ` Dave Airlie
2009-01-10 23:51             ` Richard Purdie
2009-01-16  6:53               ` Brice Goglin
2009-01-11  9:29   ` Graham Murray
2009-01-11  9:56     ` Dave Airlie

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=20091210214948.3d3c958c@daedalus.pq.iki.fi \
    --to=pq@iki.fi \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sf.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madman2003@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=xavier.bestel@free.fr \
    /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®