Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Linux: Kernel

GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19]

 

 

First page Previous page 1 2 3 4 5 6 7 8 9 Next page Last page  View All Linux kernel RSS feed   Index | Next | Previous | View Threaded


w at 1wt

Dec 16, 2006, 2:50 AM

Post #101 of 214 (5420 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Sat, Dec 16, 2006 at 11:28:27AM +0100, Rafael J. Wysocki wrote:
> On Saturday, 16 December 2006 07:43, Willy Tarreau wrote:
> > On Fri, Dec 15, 2006 at 06:55:17PM -0800, Linus Torvalds wrote:
> > >
> > >
> > > On Sat, 16 Dec 2006, karderio wrote:
> > > >
> > > > As it stands, I believe the licence of the Linux kernel does impose
> > > > certain restrictions and come with certain obligations
> > >
> > > Absolutely. And they boil down to something very simple:
> > >
> > > "Derived works have to be under the same license"
> > >
> > > where the rest is just really fluff.
> > >
> > > But the point is, "derived work" is not what _you_ or _I_ define. It's
> > > what copyright law defines.
> > >
> > > And trying to push that definition too far is a total disaster. If you
> > > push the definition of derived work to "anything that touches our work",
> > > you're going to end up in a very dark and unhappy place. One where the
> > > RIAA is your best buddy.
> > >
> > > And the proposed "we make some technical measure whereby we draw our _own_
> > > lines" is exactly that total disaster.
> > >
> > > We don't draw our own lines. We accept that the lines are drawn for us by
> > > copyright law, and we actually _hope_ that the lines aren't too sharp and
> > > too clearcut. Because sharp edges on copyright is the worst possible
> > > situation we could ever be in.
> > >
> > > The reason fair use is so important is exactly that it blunts/dulls the
> > > sharp knife that overly strong copyright protection could be.
> >
> > All this is about "fair use", and "fair use" comes from compatibility
> > between the author's intent and the user's intent. For this exact reason,
> > I have added a "LICENSE" file [1] in my software (haproxy) stating that I
> > explicitly permit linking with binary code if the user has no other choice
> > (eg: protocols specs obtained under NDA), provided that "derived work"
> > does not steal any GPL code (include files are under LGPL). On the other
> > hand, all "common protocols" are developped under GPL so that normal users
> > are the winners, and everyone is strongly encouraged to use the GPL for
> > their new code to benefit from everyone else's eyes on the code.
> >
> > This clarifies my intent and let developers decide whether *they* are
> > doing legal things or not.
> >
> > Don't you think it would be a good idea to add such a precision in the
> > sources ? It could put an end to all those repeated lessons you have to
> > teach to a lot of people about fair use. Or perhaps you like to put
> > your teacher hat once a month ? :-)
>
> I think the most important problem with the binary-only drivers is that we
> can't support their users _at_ _all_, but some of them expect us to support
> them somehow.

Agreed this is the most important problem.

> So, why don't we make an official statement, like something that will appear
> on the front page of www.kernel.org, that the users of binary-only drivers
> will never get any support from us? That would make things crystal clear.

This would constitute a good starting point. But what I was trying
to address is the other side of the problem : all the politicial
discussions on LKML which make the developers waste their time
always trying to explain the same things to extremist people (you
see, "we must forbid binary drivers to protect users freedom" and
"I'm free to run whatever I want"). I don't care at all about what
those people think and I don't like the way they want to impose
their vision to others. But above all, but I'm fed up with those
recurrent subjects on development and bug reporting mailing list,
they waste everyone's time.

> Greetings,
> Rafael

Regards,
Willy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


rjw at sisk

Dec 16, 2006, 3:09 AM

Post #102 of 214 (5421 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Saturday, 16 December 2006 11:50, Willy Tarreau wrote:
> On Sat, Dec 16, 2006 at 11:28:27AM +0100, Rafael J. Wysocki wrote:
> > On Saturday, 16 December 2006 07:43, Willy Tarreau wrote:
> > > On Fri, Dec 15, 2006 at 06:55:17PM -0800, Linus Torvalds wrote:
> > > >
> > > >
> > > > On Sat, 16 Dec 2006, karderio wrote:
> > > > >
> > > > > As it stands, I believe the licence of the Linux kernel does impose
> > > > > certain restrictions and come with certain obligations
> > > >
> > > > Absolutely. And they boil down to something very simple:
> > > >
> > > > "Derived works have to be under the same license"
> > > >
> > > > where the rest is just really fluff.
> > > >
> > > > But the point is, "derived work" is not what _you_ or _I_ define. It's
> > > > what copyright law defines.
> > > >
> > > > And trying to push that definition too far is a total disaster. If you
> > > > push the definition of derived work to "anything that touches our work",
> > > > you're going to end up in a very dark and unhappy place. One where the
> > > > RIAA is your best buddy.
> > > >
> > > > And the proposed "we make some technical measure whereby we draw our _own_
> > > > lines" is exactly that total disaster.
> > > >
> > > > We don't draw our own lines. We accept that the lines are drawn for us by
> > > > copyright law, and we actually _hope_ that the lines aren't too sharp and
> > > > too clearcut. Because sharp edges on copyright is the worst possible
> > > > situation we could ever be in.
> > > >
> > > > The reason fair use is so important is exactly that it blunts/dulls the
> > > > sharp knife that overly strong copyright protection could be.
> > >
> > > All this is about "fair use", and "fair use" comes from compatibility
> > > between the author's intent and the user's intent. For this exact reason,
> > > I have added a "LICENSE" file [1] in my software (haproxy) stating that I
> > > explicitly permit linking with binary code if the user has no other choice
> > > (eg: protocols specs obtained under NDA), provided that "derived work"
> > > does not steal any GPL code (include files are under LGPL). On the other
> > > hand, all "common protocols" are developped under GPL so that normal users
> > > are the winners, and everyone is strongly encouraged to use the GPL for
> > > their new code to benefit from everyone else's eyes on the code.
> > >
> > > This clarifies my intent and let developers decide whether *they* are
> > > doing legal things or not.
> > >
> > > Don't you think it would be a good idea to add such a precision in the
> > > sources ? It could put an end to all those repeated lessons you have to
> > > teach to a lot of people about fair use. Or perhaps you like to put
> > > your teacher hat once a month ? :-)
> >
> > I think the most important problem with the binary-only drivers is that we
> > can't support their users _at_ _all_, but some of them expect us to support
> > them somehow.
>
> Agreed this is the most important problem.
>
> > So, why don't we make an official statement, like something that will appear
> > on the front page of www.kernel.org, that the users of binary-only drivers
> > will never get any support from us? That would make things crystal clear.
>
> This would constitute a good starting point. But what I was trying
> to address is the other side of the problem : all the politicial
> discussions on LKML which make the developers waste their time
> always trying to explain the same things to extremist people (you
> see, "we must forbid binary drivers to protect users freedom" and
> "I'm free to run whatever I want"). I don't care at all about what
> those people think and I don't like the way they want to impose
> their vision to others. But above all, but I'm fed up with those
> recurrent subjects on development and bug reporting mailing list,
> they waste everyone's time.

Agreed.

Greetings,
Rafael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


tytso at mit

Dec 16, 2006, 6:42 AM

Post #103 of 214 (5434 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Sat, Dec 16, 2006 at 07:43:44AM +0100, Willy Tarreau wrote:
> All this is about "fair use", and "fair use" comes from compatibility
> between the author's intent and the user's intent.

That is NOT TRUE. If the author's intent is that anyone who is using
a TV with a screen larger than 29" and with two chairs is a theatrical
performance, and so anyone with a large screen TV must ask permission
from the MPAA first and pay $$$ before they crack open a DVD, would
you think that they should be allowed to claim that watching a DVD
isn't fair use unless you obey their rules?

I thought not.

- Ted

P.S. For people who live in the US; write your congresscritters; the
MPAA wants to propose new legislation stating exactly this.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


gene.heskett at verizon

Dec 16, 2006, 7:15 AM

Post #104 of 214 (5414 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Saturday 16 December 2006 05:28, Rafael J. Wysocki wrote:
>On Saturday, 16 December 2006 07:43, Willy Tarreau wrote:
[...]
>I think the most important problem with the binary-only drivers is that
> we can't support their users _at_ _all_, but some of them expect us to
> support them somehow.
>
>So, why don't we make an official statement, like something that will
> appear on the front page of www.kernel.org, that the users of
> binary-only drivers will never get any support from us? That would
> make things crystal clear.
>
>Greetings,
>Rafael

I disagree with this, to the extent that I perceive this business of no
support for a 'tainted' kernel to be almost in the same category as
saying that if we configure and build our own kernels, then we are alone
and you don't want to hear about it.

Yes, there is a rather large difference in actual fact, but if I come to
the list with a firewire or usb problem, we should be capable of
divorcing the fact that I may also be using an ati or nvidia supplied
driver from the firewire or usb problem at hand.

I am not in fact using the ati driver with my 9200SE, as the in-kernel as
its plenty good enough for that I do, but that's the point. To
automaticly deny supplying what might be helpfull suggestions just
because the user has a 'tainted' kernel strikes me as being pretty darned
hypocritical, particularly when the user states he has reverted but this
instant problem persists.

Yes, there have been bad drivers, but they are generally rather quickly
known about, and replaced with newer versions in short order if problems
of a fixed pattern are known to occur with version xyz of the nvidia
stuff.

small rant:
Ati's track record is not so stellar in terms of timely fixes, but from
comments I see, their support may be getting better, but IMO the main
support we see is from their PR people announcing yet another linux
driver project we rarely see the output of while the card itself is still
in production. I've been burnt there, twice now, once I even bought
linux drivers from a 3rd party & took a bath on that too, wanting to use
such and such a card, waiting till we had a driver for that card, then
going after the card only to find it doesn't work, they've replaced the
card with a new, completely incompatible version without changing
anything on the box, and only the windows cd and the actual card in the
box. That's just plain criminal, that box should be carrying at least a
new part number so the buyer can make an intelligent choice.

/rant

But those are *my* problems and I'm a big boy now. I just want to point
out that this 'tainted' business, while 90% politically driven, is a huge
turnoff for the Joe Sixpacks looking to get the M$ shaft out of an
orifice normally used for other things.

I also have witnessed more of this argument, which seems to occur at
monthly intervals, than I care to. This is not productive use of anyones
time. And I've now contributed to the noise so I'll SU...

--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


torvalds at osdl

Dec 16, 2006, 8:28 AM

Post #105 of 214 (5409 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Sat, 16 Dec 2006, Willy Tarreau wrote:
>
> All this is about "fair use", and "fair use" comes from compatibility
> between the author's intent and the user's intent.

No. "fair use" comes from an INcompatibility between the author's intent
and the users intent.

In other words, "fair use" kicks in EXACTLY when an author says "you can't
copy this except when you [.payme, stand on your head for two hours, give
your modifications back]", and the user _disagrees_.

Users still have rights under copyright law even when the author tries to
deny them those rights.

Of course, all reasonable true authors tend to agree with fair use. People
who actually do "original work" tend to all realize that everybody really
feeds off of each others works, and that we're all inspired by authors etc
that went before us. So I doubt a lot of real authors, musicians or
computer programmers will actually disagree with the notion of fair use,
but it's important to realize that fair use is exactly for when the users
and the authors rights clash, and the user DOES have rights. Even rights
that weren't explicitly given to them by the author.

> For this exact reason, I have added a "LICENSE" file [1] in my software
> (haproxy) stating that I explicitly permit linking with binary code if
> the user has no other choice (eg: protocols specs obtained under NDA),
> provided that "derived work" does not steal any GPL code (include files
> are under LGPL). On the other hand, all "common protocols" are
> developped under GPL so that normal users are the winners, and everyone
> is strongly encouraged to use the GPL for their new code to benefit from
> everyone else's eyes on the code.
>
> This clarifies my intent and let developers decide whether *they* are
> doing legal things or not.

I think that's fine, and I think it may make some of your users happier,
and breathe more easily. I don't disagree with that kind of clarification.

But:

> Don't you think it would be a good idea to add such a precision in the
> sources ?

I think it would be a hell of a lot better idea if people just realized
that they have "fair use" rights whether the authors give them or not, and
that the authors copyrights NEVER extend to anything but a "derived work".

I find the RIAA's position and the DMCA distasteful, and in that I
probably have a lot of things in common with a lot of people on this list.
But by _exactly_ the same token, I also find the FSF's position and a lot
of GPL zealots' position on this matter very distasteful.

Because "fair use" is NOT somethng that should be specified in the
license. It's very much something that people have DESPITE any license
claiming otherwise.

And I'd rather teach people that fundamental fact, than try to confuse the
issue EVEN MORE by saying that my copyright only extends to derived works
in the license text. That will just make people think that if the license
does NOT say that, they don't have fair use. AND THAT IS WRONG.

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


w at 1wt

Dec 16, 2006, 8:30 AM

Post #106 of 214 (5414 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Sat, Dec 16, 2006 at 09:42:36AM -0500, Theodore Tso wrote:
> On Sat, Dec 16, 2006 at 07:43:44AM +0100, Willy Tarreau wrote:
> > All this is about "fair use", and "fair use" comes from compatibility
> > between the author's intent and the user's intent.
>
> That is NOT TRUE. If the author's intent is that anyone who is using
> a TV with a screen larger than 29" and with two chairs is a theatrical
> performance, and so anyone with a large screen TV must ask permission
> from the MPAA first and pay $$$ before they crack open a DVD, would
> you think that they should be allowed to claim that watching a DVD
> isn't fair use unless you obey their rules?
>
> I thought not.

I don't think this is the same case. The film _author_'s primary goal is
to have a lot of families buy his DVD to watch it. Whatever the MPAA says,
I can consider it "fair use" if a family of 4..8 persons watch the DVD at
the same time. However, I may consider it an abuse when a sports club
projects the film for 30 persons.

[OT]
>
> - Ted
>
> P.S. For people who live in the US; write your congresscritters; the
> MPAA wants to propose new legislation stating exactly this.

I feel sorry for you, really. Sadly, stupid american laws generally
contaminate Europe 10 years later, so we will eventually feel sad too.

[/OT]

Regards,
Willy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


torvalds at osdl

Dec 16, 2006, 8:33 AM

Post #107 of 214 (5423 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Sat, 16 Dec 2006, Rafael J. Wysocki wrote:
>
> I think the most important problem with the binary-only drivers is that we
> can't support their users _at_ _all_, but some of them expect us to support
> them somehow.

Actually, I do think that we've made our position on that side pretty
clear.

I think people do by-and-large know that if they load a binary module,
they simply can't get supported by the kernel developers.

We make that fairly clear at module loadign time, and I think it's also
something that people who have read linux-kernel or seen other peoples
bug-reports are reasonably aware of.

I realize that a lot of people never read the kernel mailing list, but
they probably don't look at www.kernel.org either - they got their kernel
from their distribution. The only way they realize is probably by looking
at where they got whatever binary modules they use.

That said - it should be noted that a lot of the time when you use a
binary module and have an oops, the oops doesn't necessarily have anything
to do with your binary module. If I recognize the oops from other reports,
I certainly won't say "I'm not going to help you, because you used a
binary module". If I can tell where the problem is, the binary module is a
non-issue.

It's only when we try to debug things that we say "You've got a binary
module, you need to reproduce this problem _without_ it, because otherwise
we can't bother to waste our time on trying to debug something that may be
due to somebody else".

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


w at 1wt

Dec 16, 2006, 8:49 AM

Post #108 of 214 (5433 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Sat, Dec 16, 2006 at 08:28:20AM -0800, Linus Torvalds wrote:
> On Sat, 16 Dec 2006, Willy Tarreau wrote:
> >
> > All this is about "fair use", and "fair use" comes from compatibility
> > between the author's intent and the user's intent.
>
> No. "fair use" comes from an INcompatibility between the author's intent
> and the users intent.
>
> In other words, "fair use" kicks in EXACTLY when an author says "you can't
> copy this except when you [.payme, stand on your head for two hours, give
> your modifications back]", and the user _disagrees_.
>
> Users still have rights under copyright law even when the author tries to
> deny them those rights.

I understand your point, but not completely agree with the comparison,
because I think that you (as the "author") are in the type of authors
you describe below :

> Of course, all reasonable true authors tend to agree with fair use. People
> who actually do "original work" tend to all realize that everybody really
> feeds off of each others works, and that we're all inspired by authors etc
> that went before us. So I doubt a lot of real authors, musicians or
> computer programmers will actually disagree with the notion of fair use,
> but it's important to realize that fair use is exactly for when the users
> and the authors rights clash, and the user DOES have rights. Even rights
> that weren't explicitly given to them by the author.

And it is in this situation that I see the compatibility between the user's
and the author's intent : if the user doubts about his fair use and asks the
author, generally the author agrees to extend his fair use perimeter.

(...)

> I think it would be a hell of a lot better idea if people just realized
^^^^^^^^^^^^^^^^^^^^^^^
> that they have "fair use" rights whether the authors give them or not, and
> that the authors copyrights NEVER extend to anything but a "derived work".
>
> I find the RIAA's position and the DMCA distasteful, and in that I
> probably have a lot of things in common with a lot of people on this list.
> But by _exactly_ the same token, I also find the FSF's position and a lot
> of GPL zealots' position on this matter very distasteful.
^^^^^^^^^^^

You see my point ? The users generally understand "fair use" easier than
the GPL zealots which pollute the list or strip down kernel drivers to
save users' freedom. And it is to protect fair users from those people
that I explicited my intent along with the license.

> Because "fair use" is NOT somethng that should be specified in the
> license. It's very much something that people have DESPITE any license
> claiming otherwise.
>
> And I'd rather teach people that fundamental fact, than try to confuse the
> issue EVEN MORE by saying that my copyright only extends to derived works
> in the license text. That will just make people think that if the license
> does NOT say that, they don't have fair use. AND THAT IS WRONG.

That's a valid point. What is really needed is to tell them that if they
doubt, they just have to ask the author and not be advised by any GPL zealot.

> Linus

Regards,
Willy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


jeremy at goop

Dec 16, 2006, 8:54 AM

Post #109 of 214 (5429 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

Theodore Tso wrote:
> P.S. For people who live in the US; write your congresscritters; the
> MPAA wants to propose new legislation stating exactly this.
>
(Erm, that was a joke on a parody site; it got widely reported as "news".

http://www.bbspot.com/News/2006/11/home-theater-regulations.html

Other headlines:

MPAA to Thwart Pirates by Making All Movies Suck
Sony Unveils New Self-Destructive DVD Player


J)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


davidnicol at gmail

Dec 16, 2006, 9:08 AM

Post #110 of 214 (5436 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On 12/15/06, Alan <alan [at] lxorguk> wrote:
> > blather and idiotic hogwash. "Information" doesn't want to be free, nor is
> > it somethign you should fight for or necessarily even encourage.
>
> As a pedant that is the one item I have to pick you up on Linus.
> Information wants to be free, the natural efficient economic state of
> information is generally free in both senses.

I have often thought that "information wants to be free" is a meaningless
phrase that tends to stop arguments because it is difficult to understand
the words in it. Raw data does not act without agent. The universe does
tend towards increasing entropy however. Here's a fun thought experiment:
If you burn a book do you free the words?






--
He thought he could organize freedom
how naive and controlling of him
(Bjork, then some)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


torvalds at osdl

Dec 16, 2006, 9:20 AM

Post #111 of 214 (5417 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Sat, 16 Dec 2006, Willy Tarreau wrote:
>
> I understand your point, but not completely agree with the comparison,
> because I think that you (as the "author") are in the type of authors
> you describe below :
>
> > Of course, all reasonable true authors tend to agree with fair use.

Sure. Sadly, in this day and age, "copyright owner" and "author" only bear
a very passing resemblance to each other.

In a lot of areas, the AUTHOR may be a very reasonable person, and realize
that fair use is a good thing, and perhaps even realize that in some
places even unfair use can be a good thing (do you really think you should
pay $20 for a DVD if you make $3 a month in a sweatshop in china? Maybe
piracy sometimes is simply better..)

But the author may also have his own reasons for wanting to _deny_ fair
use. Maybe he's just a royal a-hole, and wants to milk his work for
whatever it's worth. But maybe he's a person with an agenda, and wants to
ignore fair use because he wants to "improve the world for everybody",
never mind that he tries to deny people a fundamental right in the
process. I call those people a-holes too (in all fairness, they return the
favor, so we're all even ;)

But even more commonly, the author simply doesn't control the copyright at
all any more. In many areas (and software is one - including even large
swaths of free software), the copyrights of a work is not really
controlled by the author of the work, but by companies or foundations that
have no reason to really try to educate people about "fair use".

So I actually think that the authors that actually UNDERSTAND fair use,
and realize that people can use portions of their work without permission,
AND that actually control their work is a very very very small subset of
authors in general.

This has nothing to do with software per se, btw. Pick up one of the
Calvin & Hobbes books by Bill Watterson - I think it may have been the "10
year anniversary" one - where he talks about the disagreements he had with
the people who actually controlled the copyrights (and I think also some
of the people who used his artwork without any permission - the line
between "fair use" and "illegal" really is a murky one, and while we
should celebrate that murkiness, it's also why people disagree).

> > And I'd rather teach people that fundamental fact, than try to confuse the
> > issue EVEN MORE by saying that my copyright only extends to derived works
> > in the license text. That will just make people think that if the license
> > does NOT say that, they don't have fair use. AND THAT IS WRONG.
>
> That's a valid point. What is really needed is to tell them that if they
> doubt, they just have to ask the author and not be advised by any GPL zealot.

Well, in open source, there often isn't any one "the author". So you can't
do that. And when there is, as mentioned, he may not actually even have
the legal right any more to give you any license advice. And even when he
does hold the copyrights, he may change his mind later.

So in the end, the thing you can and should depend on is: the license text
itself (and happily, the GPLv2 very clearly talks about the real line
being "derived work" - it may be a murky line, and they seem to want to
change that to something harder in the GPLv3, but it's a good line), a
separate signed contract, or simply a legal opinion, preferably by a judge
in a court of law.

Of course, it very seldom gets to that kind of issue. People tend to just
walk very gently around it all.

If you want to be safe, you NEVER do any binary modules. The only
_obviously_ safe thing is to always do only what the license very
explicitly allows you to, and in the case of the GPLv2, that's to release
all modifications under the same GPLv2.

Anything else, you have to make some really scary decisions. Can a judge
decide that a binary module is a derived work even though you didn't
actually use any code? The real answer is: HELL YES. It's _entirely_
possible that a judge would find NVidia and ATI in violation of the GPLv2
with their modules.

Judges have done stranger things. And it's not my place to say what the
limit of "derived work" actually is. It all probably depends on a lot of
circumstances, and there simply isn't an easy answer.

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


gallir at gmail

Dec 16, 2006, 10:27 AM

Post #112 of 214 (5425 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

> I think it would be a hell of a lot better idea if people just realized
> that they have "fair use" rights whether the authors give them or not, and
^^^^^^^^^
> that the authors copyrights NEVER extend to anything but a "derived work"
...
> I find the RIAA's position and the DMCA distasteful, and in that I
> probably have a lot of things in common with a lot of people on this list.
> But by _exactly_ the same token, I also find the FSF's position and a lot
> of GPL zealots' position on this matter very distasteful.
...
> Because "fair use" is NOT somethng that should be specified in the
^^^^^^^^^
> license.

As you probably know, the GPL, the FSF, RMS or even GPL "zealots" never tried
to change or restrict "fair use". GPL[23] covers only to "distibution" of the
covered program. The freedom #0 says explicitly: "right to use the program
for any purpose".

So, I don't see any clash here between GPL/FSF/RMS with "fair use"

And you probably know that any GPLed code can be linked and executed with any
other program, whatever is its license if it's for personal use (is that
worse than "fair use"?).

And even if there is a function in linux that disables loading of non GPL
modules, it's still allowed under the GPL to distribute a kernel with those
functions removed. Any user can load any other module in this kernel without
worrying about "fair use" or "derived work", GPL allows her to do it.

So, where's the freaking relationship between GPL (or its "zealots") and "fair
use"? Who is trying to re-define it?

FUD, FUD, FUD.

--
ricardo galli GPG id C8114D34
http://mnm.uib.es/gallir/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


davej at redhat

Dec 16, 2006, 10:33 AM

Post #113 of 214 (5412 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Sat, Dec 16, 2006 at 09:20:15AM -0800, Linus Torvalds wrote:

> Anything else, you have to make some really scary decisions. Can a judge
> decide that a binary module is a derived work even though you didn't
> actually use any code? The real answer is: HELL YES. It's _entirely_
> possible that a judge would find NVidia and ATI in violation of the GPLv2
> with their modules.

ATI in particular, I'm amazed their lawyers OK'd stuff like..

+ifdef STANDALONE
MODULE_LICENSE(GPL);
+endif

This a paraphrased diff, it's been a while since I've seen it.
It's GPL if you build their bundled copy of the AGPGART code as agpgart.ko,
but the usual use case is that it's built-in to fglrx.ko, which sounds
incredibly dubious.

Now, AGPGART has a murky past wrt licenses. It initally was imported
into the tree with the license "GPL plus additional rights".
Nowhere was it actually documented what those rights were, but I'm
fairly certain it wasn't to enable nonsense like the above.
As it came from the XFree86 folks, it's more likely they really meant
"Dual GPL/MIT" or similar.

When I took over, any new code I wrote I explicitly set out to mark as GPL
code, as my modifications weren't being contributed back to X, they were
going back to the Linux kernel. ATI took those AGPv3 modifications from
a 2.5 kernel, backported them to their 2.4 driver, and when time came
to do a 2.6 driver, instead of doing the sensible thing and dropping
them in favour of using the kernel AGP driver, they chose to forward
port their unholy abomination to 2.6.
It misses so many fixes (and introduces a number of other problems)
that its just unfunny.

The thing that really ticks me off though is the free support ATI seem
to think they're entitled to. I've had end-users emailing me
"I asked ATI about this crash I've been seeing with fglrx, and they
asked me to mail you".

I invest my time into improving free drivers. When companies start
expecting me to debug their part binary garbage mixed with license
violations, frankly, I think they're taking the piss.

A year and a half ago, I met an ATI engineer at OLS, who told me they
were going to 'resolve this'. I'm still waiting.
I live in hope that the AMD buyout will breathe some sanity into ATI.
Then again, I've only a limited supply of optimism.

Dave

--
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


tytso at mit

Dec 16, 2006, 12:23 PM

Post #114 of 214 (5427 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Sat, Dec 16, 2006 at 05:30:31PM +0100, Willy Tarreau wrote:
> I don't think this is the same case. The film _author_'s primary goal is
> to have a lot of families buy his DVD to watch it. Whatever the MPAA says,
> I can consider it "fair use" if a family of 4..8 persons watch the DVD at
> the same time.

"You can consider it"? But you're not the author. This is the
hypocrisy that Linus was talking about. At the same time that you're
trying to dictate to other other people can use their copy of the
Linux kernel, when it comes to others people's copyrighted work, you
feel to dictate what is and isn't "fair use".

That's the big thing about dynamic linking. The GPL has always said
it is about distribution, not about use. The dynamic linking of a
kernel module happens in the privacy of someone's home. When we try
to dictate what people are doing in the privacy in their home, we're
no better than the MPAA or the RIAA.

As far as whether or not someone is allowed to distribute a binary
module that can be linked into the Linux kernel, that's a question of
whether the binary module is a derived work or not. And that's not up
to us, that's up to the local laws. But before you decide that you
want the most extreme form of anything that wanders close to one
person's code or header files is a derived work, and to start going to
work lobbying your local legislature, recall that there have been
those who have claimed that Linux is a derived work of Unix because we
used things like #define's for errno codes and structure definitions
of ELF binaries. You really sure you want to go there?

- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


torvalds at osdl

Dec 16, 2006, 1:01 PM

Post #115 of 214 (5429 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Sat, 16 Dec 2006, Ricardo Galli wrote:

> As you probably know, the GPL, the FSF, RMS or even GPL "zealots" never tried
> to change or restrict "fair use". GPL[23] covers only to "distibution" of the
> covered program. The freedom #0 says explicitly: "right to use the program
> for any purpose".

I'm sorry, but you're just rewriting history.

The FSF very much _has_ tried to make "fair use" a very restricted issue.
The whole reason the LGPL exists is that people realized that if they
don't do something like that, the GPL would have been tried in court, and
the FSF's position that anything that touches GPL'd code would probably
have been shown to be bogus.

In reality, if the FSF actually believed in "fair use", they would just
have admitted that GNU libc could have continued to be under the GPL, and
that any programs that link against it are obviously not "derived" from
it.

But no. The FSF has very much tried to confuse and muddle the issue, and
instead have claimed that projects like glibc should be done under the
"Lesser" GPL.

That's just idiocy, but it works as a way to defuse the problem that the
FSF has always had with admitting that not only _they_ have "fair use"
rights, but others have them too.

Do you REALLY believe that a binary becomes a "derived work" of any random
library that it gets linked against? If that's not "fair use" of a library
that implements a standard library definition, I don't know what is.

And yes, the FSF really has tried to push that totally insane argument.

So don't tell me that the FSF honors "fair use". They say they do, but
they only seem to honor it when it helps _their_ argument, not when it
helps "those evil people who try to take advantage of our hard work".

The fact is, if you accept fair use, you have to accept it for other
people to take advantage of too. Fair use really isn't just a one-way
street.

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


w at 1wt

Dec 16, 2006, 1:04 PM

Post #116 of 214 (5434 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Sat, Dec 16, 2006 at 03:23:12PM -0500, Theodore Tso wrote:
> On Sat, Dec 16, 2006 at 05:30:31PM +0100, Willy Tarreau wrote:
> > I don't think this is the same case. The film _author_'s primary goal is
> > to have a lot of families buy his DVD to watch it. Whatever the MPAA says,
> > I can consider it "fair use" if a family of 4..8 persons watch the DVD at
> > the same time.
>
> "You can consider it"? But you're not the author. This is the
> hypocrisy that Linus was talking about. At the same time that you're
> trying to dictate to other other people can use their copy of the
> Linux kernel, when it comes to others people's copyrighted work, you
> feel to dictate what is and isn't "fair use".

No, I don't want to dictate, it's the opposite, I say what _I_ consider
fair use. Other people will consider it other ways. It's exactly the
gray area Linus was talking about. As long as all parties agree on one
given fair use, there's no problem. Discussion and sometimes litigation
is needed when some parties disagree.

> That's the big thing about dynamic linking. The GPL has always said
> it is about distribution, not about use. The dynamic linking of a
> kernel module happens in the privacy of someone's home. When we try
> to dictate what people are doing in the privacy in their home, we're
> no better than the MPAA or the RIAA.

100% agreed with you on this !

> As far as whether or not someone is allowed to distribute a binary
> module that can be linked into the Linux kernel, that's a question of
> whether the binary module is a derived work or not. And that's not up
> to us, that's up to the local laws. But before you decide that you
> want the most extreme form of anything that wanders close to one
> person's code or header files is a derived work, and to start going to
> work lobbying your local legislature, recall that there have been
> those who have claimed that Linux is a derived work of Unix because we
> used things like #define's for errno codes and structure definitions
> of ELF binaries. You really sure you want to go there?

Ted, I think you get me wrong. I don't want to dictate anyone what's
derived work and what is not. Instead, it's the opposite. I just want
to indicate them what's explicitly permitted by the author and copyright
owner (at least by me as the author/copyright owner when I can) so that
people can decide by themselves what level of risk they take by doing
whatever they want. What I consider the most important is to encourage
fair use even in areas I never anticipated, and when possible, try to
protect fair users from the GPL zealots who want to bite whenever one
gives them an opportunity to abuse the gray area to feel stronger.

I have opened even more my software and tried to clarify the reasons
why I chose the dual license exactly for this reason.

What I was suggesting is to add a clarification with the kernel to
avoid those overly long threads on LKML such as this one. It would
basically be structured like this :

"Use in the following order" :
1) fully respect the license and you're OK.
2) play in the gray area if you need and if you consider it fair use,
but seek legal advice from a lawyer (and not LKML) before !
3) explicitly violate the license, and prepare to get sued sooner or later.
For GPL zealots : please do not report what _you_ consider abuse to LKML,
contact the abuser, then a lawyer or specialized sites for this.

But Linus is right, he's not the only copyright owner, and that makes it
harder to touch anything related to license and use.

> - Ted

Willy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


gallir at gmail

Dec 16, 2006, 4:22 PM

Post #117 of 214 (5439 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Saturday 16 December 2006 22:01, Linus Torvalds wrote:
> On Sat, 16 Dec 2006, Ricardo Galli wrote:
> > As you probably know, the GPL, the FSF, RMS or even GPL "zealots" never
> > tried to change or restrict "fair use". GPL[23] covers only to
> > "distibution" of the covered program. The freedom #0 says explicitly:
> > "right to use the program for any purpose".
>
> I'm sorry, but you're just rewriting history.
>
> The FSF very much _has_ tried to make "fair use" a very restricted issue.
> The whole reason the LGPL exists is that people realized that if they
> don't do something like that, the GPL would have been tried in court, and
> the FSF's position that anything that touches GPL'd code would probably
> have been shown to be bogus.
>
> In reality, if the FSF actually believed in "fair use", they would just
> have admitted that GNU libc could have continued to be under the GPL, and
> that any programs that link against it are obviously not "derived" from
> it.
>
> But no. The FSF has very much tried to confuse and muddle the issue, and
> instead have claimed that projects like glibc should be done under the
> "Lesser" GPL.

OK, let assume your perspective of the history is the valid and real one,
then, ¿where are all lawsits against other big GPL only projects? For example
libqt/kdelibs. You can hardly provide any example where the GPL wasn't hold
in court.

> The fact is, if you accept fair use, you have to accept it for other
> people to take advantage of too. Fair use really isn't just a one-way
> street.

"Fair use: The right set forth in Section 107 of the United States Copyright
Act, to use copyrighted materials for certain purposes, such as criticism,
comment, news reporting, teaching, scholarship, and research. The Copyright
Act does not define fair use. Instead, whether a use is fair use is
determined by balancing these factors: ..."

According to the law, I don't see how FSF tries to avoid or to reject the fair
use rights.

It seems to me you provides us with a copyright law interpretation supported
only by the very [narrow] exceptions of the copyright law, a logical fallacy.


--
ricardo galli GPG id C8114D34
http://mnm.uib.es/gallir/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


bunk at stusta

Dec 16, 2006, 5:56 PM

Post #118 of 214 (5415 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Sat, Dec 16, 2006 at 01:33:01PM -0500, Dave Jones wrote:
> On Sat, Dec 16, 2006 at 09:20:15AM -0800, Linus Torvalds wrote:
>
> > Anything else, you have to make some really scary decisions. Can a judge
> > decide that a binary module is a derived work even though you didn't
> > actually use any code? The real answer is: HELL YES. It's _entirely_
> > possible that a judge would find NVidia and ATI in violation of the GPLv2
> > with their modules.
>
> ATI in particular, I'm amazed their lawyers OK'd stuff like..
>
> +ifdef STANDALONE
> MODULE_LICENSE(GPL);
> +endif
>
> This a paraphrased diff, it's been a while since I've seen it.
> It's GPL if you build their bundled copy of the AGPGART code as agpgart.ko,
> but the usual use case is that it's built-in to fglrx.ko, which sounds
> incredibly dubious.
>...

Current versions contain
MODULE_LICENSE("GPL and additional rights");
...

> The thing that really ticks me off though is the free support ATI seem
> to think they're entitled to. I've had end-users emailing me
> "I asked ATI about this crash I've been seeing with fglrx, and they
> asked me to mail you".
>
> I invest my time into improving free drivers. When companies start
> expecting me to debug their part binary garbage mixed with license
> violations, frankly, I think they're taking the piss.
>
> A year and a half ago, I met an ATI engineer at OLS, who told me they
> were going to 'resolve this'. I'm still waiting.
> I live in hope that the AMD buyout will breathe some sanity into ATI.
> Then again, I've only a limited supply of optimism.

But who's actually taking legal actions?

Perhaps pending legal changes that will turn copyright violations into
crimes might help to take legal actions without the legal risks of
civil trials.

Otherwise, it seems to be highly unlikely that anyone will want to sue a
company that is often located in a different country, and the only
possible legal action will be cease and desist letters against people
who are infriding the copyright by e.g. selling Linux distributions
containing fglrx at Ebay or operating Debian ftp mirrors. That sounds
highly unfair, but unfortunately it also seems to be the only effective
way for someone without a big wallet to effectively act against such
licence violations...

> Dave

cu
Adrian

--

"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


bunk at stusta

Dec 16, 2006, 7:06 PM

Post #119 of 214 (5400 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Sun, Dec 17, 2006 at 02:56:09AM +0100, Adrian Bunk wrote:
>...
> Otherwise, it seems to be highly unlikely that anyone will want to sue a
> company that is often located in a different country, and the only
> possible legal action will be cease and desist letters against people
> who are infriding the copyright by e.g. selling Linux distributions
> containing fglrx at Ebay or operating Debian ftp mirrors. That sounds
> highly unfair, but unfortunately it also seems to be the only effective
> way for someone without a big wallet to effectively act against such
> licence violations...

To avoid any misunderstandings:

I do not want to threaten anyone, and I do not plan to do such legal
actions myself.

My point is simply that whoever considers this grey area a good thing
and wants to leave clarifications to the lawyers should be aware that
e.g. in the fglrx and nvidia cases it's quite possible that the target
of legal actions might not be AMD but e.g. the Technical University of
Dresden that is distributing the offending code in Germany [1].

cu
Adrian

[1] by operating ftp.de.debian.org

--

"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


tytso at mit

Dec 16, 2006, 8:10 PM

Post #120 of 214 (5412 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Sun, Dec 17, 2006 at 01:22:12AM +0100, Ricardo Galli wrote:
> OK, let assume your perspective of the history is the valid and real one,
> then, ¿where are all lawsits against other big GPL only projects? For example
> libqt/kdelibs. You can hardly provide any example where the GPL wasn't hold
> in court.

There's no need for lawsuits against things like libqt. The question
is whether someone who writes a commercial program that happens to
dynamically link against libqt is in fact in violation of copyright
claims. In such a case, the owners of libqt would have to sue the
commercial application writer, not the other way around. There
haven't been any such cases, mostly because (a) the FUD generated by
the FSF about GPL vs. LGPL has generally been enough to cause
application authors to avoid using GPL'ed code even if it would be
legally defensible in court, and (b) I personally suspect that the FSF
has deliberately not tried to make a test case out of a commercial
application dynamically linking against a GPL'ed library.

In point of fact, if you compile libss from e2fsprogs on a Solaris
machine, and then let the Sun Enterprise Authentication Mechanism (a
propietary version of Kerberos v5) link against that version of libss
(as opposed to the one derived from the MIT Kerberos version of
libss), you can have a propietary Sun binary linking against libss
which will called will dynamically pull in the GPL'ed version of
readline (or the BSD licensed editline library, whichever one it finds
first in its search path). Quick! Is there a GPL violation involved,
and if so, who should the FSF try to sue first?

There are indeed plenty of cases where the GPL has been upheld in a
court of law, but usually it's some straightforward case of an
embedded version of Linux being used without releasing source. As far
as I know, there has been no case on point about GPL and dynamic
linking, and I personally suspect it's at least partially because the
FSF is afraid it would lose such a case. (As I've said, at least one
law professor of mine from the MIT Sloan School of Management has told
me that in her opinion the FSF's theory would be "laughed out of
court").

- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


geert at linux-m68k

Dec 17, 2006, 2:11 AM

Post #121 of 214 (5420 views)
Permalink
RE: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Thu, 14 Dec 2006, David Schwartz wrote:
> > And there's also the common misconception all costumers had enough
> > information when buying something. If you are a normal Linux user and
> > buy some hardware labelled "runs under Linux", it could turn out that's
> > with a Windows driver running under ndiswrapper...
>
> That is something that I think is well worth fixing. Doesn't Linus own the
> trademark 'Linux'? How about some rules for use of that trademark and a
> 'Works with Linux' logo that can only be used if the hardware specifications
> are provided?

Exactly my thoughts...

> Let them provide a closed-source driver if they want. Let them provide
> user-space applications for which no source is provided if they want. But
> don't let them use the logo unless they release sufficient information to
> allow people to develop their own drivers and applications to interface with
> the hardware.
>
> That makes it clear that it's not about giving us the fruits of years of
> your own work but that it's about enabling us to do our own work. (I would
> have no objection to also requiring them to provide a minimal open-source
> driver. I'm not trying to work out the exact terms here, just get the idea
> out.)

Since `works with' may sound a bit too vague, something like
`LinuxFriendly(tm)', with a happy penguin logo?

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert [at] linux-m68k

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


geert at linux-m68k

Dec 17, 2006, 2:54 AM

Post #122 of 214 (5426 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Thu, 14 Dec 2006, Jan Engelhardt wrote:
> On Dec 14 2006 14:10, Arjan van de Ven wrote:
> >On Thu, 2006-12-14 at 13:55 +0100, Jan Engelhardt wrote:
> >> >On Thu, 14 Dec 2006 12:31:16 +0100
> >> >Hans-Jürgen Koch wrote:
> >> >
> >> >You think its any easier to debug because the code now runs in ring 3 but
> >> >accessing I/O space.
> >>
> >> A NULL fault won't oops the system,
> >
> >.. except when the userspace driver crashes as a result and then the hw
> >still crashes the hw (for example via an irq storm or by tying the PCI
> >bus or .. )
>
> hw crashes the hw? Anyway, yes it might happen, the more with non-NULL pointers
> (dangling references f.ex.)
> However, if the userspace part is dead, no one acknowledges the irq, hence an
> irq storm (if not caused by writing bogus stuff into registers) should not
> happen.

Shared level IRQ?

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert [at] linux-m68k

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds


rjw at sisk

Dec 17, 2006, 2:56 AM

Post #123 of 214 (5417 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Sunday, 17 December 2006 11:11, Geert Uytterhoeven wrote:
> On Thu, 14 Dec 2006, David Schwartz wrote:
> > > And there's also the common misconception all costumers had enough
> > > information when buying something. If you are a normal Linux user and
> > > buy some hardware labelled "runs under Linux", it could turn out that's
> > > with a Windows driver running under ndiswrapper...
> >
> > That is something that I think is well worth fixing. Doesn't Linus own the
> > trademark 'Linux'? How about some rules for use of that trademark and a
> > 'Works with Linux' logo that can only be used if the hardware specifications
> > are provided?
>
> Exactly my thoughts...
>
> > Let them provide a closed-source driver if they want. Let them provide
> > user-space applications for which no source is provided if they want. But
> > don't let them use the logo unless they release sufficient information to
> > allow people to develop their own drivers and applications to interface with
> > the hardware.
> >
> > That makes it clear that it's not about giving us the fruits of years of
> > your own work but that it's about enabling us to do our own work. (I would
> > have no objection to also requiring them to provide a minimal open-source
> > driver. I'm not trying to work out the exact terms here, just get the idea
> > out.)
>
> Since `works with' may sound a bit too vague, something like
> `LinuxFriendly(tm)', with a happy penguin logo?

I like this idea.

Greetings,
Rafael


--
If you don't have the time to read,
you don't have the time or the tools to write.
- Stephen King
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


geert at linux-m68k

Dec 17, 2006, 2:57 AM

Post #124 of 214 (5399 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Thu, 14 Dec 2006, Christoph Hellwig wrote:
> On Thu, Dec 14, 2006 at 09:08:41AM -0800, Chris Wedgwood wrote:
> > On Thu, Dec 14, 2006 at 09:03:57AM -0800, Linus Torvalds wrote:
> >
> > > I actually think the EXPORT_SYMBOL_GPL() thing is a good thing, if
> > > done properly (and I think we use it fairly well).
> > >
> > > I think we _can_ do things where we give clear hints to people that
> > > "we think this is such an internal Linux thing that you simply
> > > cannot use this without being considered a derived work".
> >
> > Then why not change the name to something more along those lines?
>
> Yes, EXPORT_SYMBOL_INTERNAL would make a lot more sense.

I find all those names confusing. If these special symbols are
GPL/INTERNAL/WHATEVER, what are the other exported symbols?

GPL -> Non-GPL?
INTERNAL -> External?

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert [at] linux-m68k

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


geert at linux-m68k

Dec 17, 2006, 3:04 AM

Post #125 of 214 (5408 views)
Permalink
Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] [In reply to]

On Sat, 16 Dec 2006, Gene Heskett wrote:
> On Saturday 16 December 2006 05:28, Rafael J. Wysocki wrote:
> >On Saturday, 16 December 2006 07:43, Willy Tarreau wrote:
> [...]
> >I think the most important problem with the binary-only drivers is that
> > we can't support their users _at_ _all_, but some of them expect us to
> > support them somehow.
> >
> >So, why don't we make an official statement, like something that will
> > appear on the front page of www.kernel.org, that the users of
> > binary-only drivers will never get any support from us? That would
> > make things crystal clear.
>
> I disagree with this, to the extent that I perceive this business of no
> support for a 'tainted' kernel to be almost in the same category as
> saying that if we configure and build our own kernels, then we are alone
> and you don't want to hear about it.
>
> Yes, there is a rather large difference in actual fact, but if I come to

There's indeed a big difference. That's why people ask for your .config and for
the changes you made to your kernel (especially in cases like `Hi, the kernel
crashes with my newly written driver').

> the list with a firewire or usb problem, we should be capable of
> divorcing the fact that I may also be using an ati or nvidia supplied
> driver from the firewire or usb problem at hand.

You can divorce it by not loading the binary-only driver(s) and reproducing the
problem.

> I am not in fact using the ati driver with my 9200SE, as the in-kernel as
> its plenty good enough for that I do, but that's the point. To
> automaticly deny supplying what might be helpfull suggestions just
> because the user has a 'tainted' kernel strikes me as being pretty darned
> hypocritical, particularly when the user states he has reverted but this
> instant problem persists.

Then the kernel is no longer tainted, right?

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert [at] linux-m68k

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

First page Previous page 1 2 3 4 5 6 7 8 9 Next page Last page  View All Linux kernel RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.