From: Will Dyson <will.dyson@gmail.com>
To: Pekka Paalanen <pq@iki.fi>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Dave Airlie <airlied@linux.ie>,
Xavier Bestel <xavier.bestel@free.fr>,
linux-kernel@vger.kernel.org, dri-devel@lists.sf.net
Subject: Re: [git pull] drm
Date: Thu, 10 Dec 2009 15:35:08 -0500 [thread overview]
Message-ID: <8e6f94720912101235l30d05c03m54b769d9fd6ac35d@mail.gmail.com> (raw)
In-Reply-To: <20091210214948.3d3c958c@daedalus.pq.iki.fi>
On Thu, Dec 10, 2009 at 2:49 PM, Pekka Paalanen <pq@iki.fi> wrote:
> 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.
This seems similar to the unfortunate situation with the b43 wireless
card firmware. Broadcom refuses to provide the firmware under a
redistributable license (or even as files separate from their
proprietary drivers). This did not stop b43 from being included in
Linux. Distributions have dealt with it by providing a script that
downloads the proprietary driver and extracts the firmware from it to
files in /lib/firmware.
Do you think that a similar solution for nouveau would be legally
problematic? Or is the issue technical, since you mention that the
ctxprogs were obtained by mmiotrace, instead of a more straightforward
extraction from the binary driver blobs?
--
Will Dyson
next prev parent reply other threads:[~2009-12-10 20:35 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
2009-12-10 20:35 ` Will Dyson [this message]
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=8e6f94720912101235l30d05c03m54b769d9fd6ac35d@mail.gmail.com \
--to=will.dyson@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pq@iki.fi \
--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®