* RE: Gauntlet Set NOW!
@ 2003-01-04 10:57 Hell.Surfers
2003-01-04 16:35 ` Mark Rutherford
0 siblings, 1 reply; 32+ messages in thread
From: Hell.Surfers @ 2003-01-04 10:57 UTC (permalink / raw)
To: andrew, andre, ryan, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
you cant hear this, but if I was a troll, I woulda been happy, im not im off to write a decent license, that allows binaries and true free use, its not about the hardware, I wanna use a os thats just _legal_ so im gonna piss off and do that, oh and Im a elec engineer and physicist, bye.
Dean McEwan, If the drugs don't work, [sarcasm] take more...[/sarcasm].
On Sat, 04 Jan 2003 23:42:37 +1300 Andrew McGregor <andrew@indranet.co.nz> wrote:
[-- Attachment #2: Type: message/rfc822, Size: 2178 bytes --]
From: Andrew McGregor <andrew@indranet.co.nz>
To: Hell.Surfers@cwctv.net, andre@linux-ide.org, ryan@michonline.com, linux-kernel@vger.kernel.org
Subject: RE: Gauntlet Set NOW!
Date: Sat, 04 Jan 2003 23:42:37 +1300
Message-ID: <143640000.1041676957@localhost.localdomain>
Welcome to the kill file, Mr Troll.
For your edification, it *is* done. Frequently. Probably even in the
settop box you're posting with.
--On Saturday, January 04, 2003 10:12:49 +0000 Hell.Surfers@cwctv.net wrote:
> Sounds like a jumped up PIC chip, cant think why isnt done yet.
>
> Dean McEwan, If the drugs don't work, [sarcasm] take more...[/sarcasm].
>
> On Sat, 4 Jan 2003 02:07:27 -0800 (PST) Andre Hedrick
> <andre@linux-ide.org> wrote:
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-04 10:57 Gauntlet Set NOW! Hell.Surfers
@ 2003-01-04 16:35 ` Mark Rutherford
0 siblings, 0 replies; 32+ messages in thread
From: Mark Rutherford @ 2003-01-04 16:35 UTC (permalink / raw)
To: Hell.Surfers; +Cc: linux-kernel@vger.kernel.org
score -1, troll
you are a troll.
cant we just get along...
Hell.Surfers@cwctv.net wrote:
> you cant hear this, but if I was a troll, I woulda been happy, im not im off to write a decent license, that allows binaries and true free use, its not about the hardware, I wanna use a os thats just _legal_ so im gonna piss off and do that, oh and Im a elec engineer and physicist, bye.
>
> Dean McEwan, If the drugs don't work, [sarcasm] take more...[/sarcasm].
>
> On Sat, 04 Jan 2003 23:42:37 +1300 Andrew McGregor <andrew@indranet.co.nz> wrote:
>
> ------------------------------------------------------------------------
>
> Subject: RE: Gauntlet Set NOW!
> Date: Sat, 04 Jan 2003 23:42:37 +1300
> From: Andrew McGregor <andrew@indranet.co.nz>
> To: Hell.Surfers@cwctv.net, andre@linux-ide.org, ryan@michonline.com,
> linux-kernel@vger.kernel.org
> References: <0258a1111100413DTVMAIL11@smtp.cwctv.net>
>
> Welcome to the kill file, Mr Troll.
>
> For your edification, it *is* done. Frequently. Probably even in the
> settop box you're posting with.
>
> --On Saturday, January 04, 2003 10:12:49 +0000 Hell.Surfers@cwctv.net wrote:
>
> > Sounds like a jumped up PIC chip, cant think why isnt done yet.
> >
> > Dean McEwan, If the drugs don't work, [sarcasm] take more...[/sarcasm].
> >
> > On Sat, 4 Jan 2003 02:07:27 -0800 (PST) Andre Hedrick
> > <andre@linux-ide.org> wrote:
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Regards,
Mark Rutherford
mark@justirc.net
File: Mark Rutherford.ASC
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
mQGiBDqwRnsRBADTpKKSKAcphYdcVTvBpEFFNK1eL4dQ/pBwK4NimeoAA9ISD04L
Mv/CqH5g9D1wzXEhRBhbFZnmfoTPFEWH4Gjr4KIPdsXkTEfoJ2j55qksHWMkE10A
K8gZlI3Ovuf8BbIabfXmjf+XtId3F4+7+og4mc7EAkatYbbl/5pR0Niy3wCg/+I/
LUQPYGloF829jXaOW7C+tG8D/RZt8lAL/Z1NfGsQYZlE1X+Gcqf0J6HaMosnVuah
1zAbgUHCIvNq+TOC+0KydEvbs7tAq6m+Q4zQZaqEsMwufTCWxzh+v3thRBLIuT5E
jsTi4djkrdG3TTeAszymO/YEXQMg4Tq2hMiyeWlyTmH4C6enMu0zJMIu4OEef7+W
KpYhBACYnukDVI8Vnw1J5KaiCZYvERhj4cr3BTk7oeYxIRH1x5S6NXK0+uVcpusa
a8ZU4zcxvHh0k3iR8HIZcNh30eXbMF/J5pW9gorJuPwCC5Q7b+gUVaeec+1X+Wmt
2k8RAq9RtriUdrmVN5QcPBLFd4hOHQcWDcuyhmiFp68LFvxLSLQrTWFyayBSdXRo
ZXJmb3JkIDxNYXJrMjAwMEBiZWxsYXRsYW50aWMubmV0PokAWAQQEQIAGAUCOrBG
ewgLAwkIBwIBCgIZAQUbAwAAAAAKCRAudCWX7QO6ULcaAJwIsYHeAp6FC5OVWSOo
qc8O87kvBgCgz1cLgVXYcSlDWEeE32PFYb6akuy5Ag0EOrBGexAIAPZCV7cIfwgX
cqK61qlC8wXo+VMROU+28W65Szgg2gGnVqMU6Y9AVfPQB8bLQ6mUrfdMZIZJ+AyD
vWXpF9Sh01D49Vlf3HZSTz09jdvOmeFXklnN/biudE/F/Ha8g8VHMGHOfMlm/xX5
u/2RXscBqtNbno2gpXI61Brwv0YAWCvl9Ij9WE5J280gtJ3kkQc2azNsOA1FHQ98
iLMcfFstjvbzySPAQ/ClWxiNjrtVjLhdONM0/XwXV0OjHRhs3jMhLLUq/zzhsSlA
GBGNfISnCnLWhsQDGcgHKXrKlQzZlp+r0ApQmwJG0wg9ZqRdQZ+cfL2JSyIZJrqr
ol7DVekyCzsAAgIIAO5Bt3XOgo2GPNOCuLv6A6mRxPxwwVsYEMmVAIp/c5nluBMi
Tu4iQU5f3U9UqZMcFKyLr1Vh0bpO6RB6L/5tXWSRY2Yly9Ofg/e0Npgebkdd8GXE
+IuEDI4lr1kbO70hlxFUPKSOQRjSmmVKNhUAiXEFQ7OtB9k5GECsHrD6qxR6r/ny
XMBK2g2UUSh17Gx/pqH+XwXJ67DEQmF8hcnyiN9E3WQ5w3bIbKwFCaHF+tJbVnUd
XxszxQYrsb6Feo0FVdCD+VVPQGesv34CrnKuED/mF/WoI8a3eYCMiY03IQgW514X
JX+Jnmk9RFbTg75NdXIKDqKpB3wq39n3JmWRZG+JAEwEGBECAAwFAjqwRnsFGwwA
AAAACgkQLnQll+0DulAfjgCfbVxiUtJbpXPn6gVJlnlIzur1yvgAnjh/9bdLsSrd
cUaN07NL7N9NjgG1
=hpbN
-----END PGP PUBLIC KEY BLOCK-----
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: Gauntlet Set NOW!
@ 2003-01-05 6:28 Hell.Surfers
0 siblings, 0 replies; 32+ messages in thread
From: Hell.Surfers @ 2003-01-05 6:28 UTC (permalink / raw)
To: andrew, matan, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 274 bytes --]
I do not count GPL programs on top of a proprietary bios because the bios is firmware AND NOT TECHNICALLY SOFTWARE.
Dean McEwan, If the drugs don't work, [sarcasm] take more...[/sarcasm].
On Sun, 05 Jan 2003 08:43:02 +1300 Andrew McGregor <andrew@indranet.co.nz> wrote:
[-- Attachment #2: Type: message/rfc822, Size: 2878 bytes --]
From: Andrew McGregor <andrew@indranet.co.nz>
To: Matan Ziv-Av <matan@svgalib.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Gauntlet Set NOW!
Date: Sun, 05 Jan 2003 08:43:02 +1300
Message-ID: <570510000.1041709382@localhost.localdomain>
Which is all nice and good, but trying to do this in order to suspend a
laptop is going to result in vastly more code, and you just can't get the
documentation.
After all, the vendor gave you the code with the hardware in this case, so
it's not as if you can possibly not have a license for it :-)
Andrew
--On Saturday, January 04, 2003 21:31:38 +0200 Matan Ziv-Av
<matan@svgalib.org> wrote:
> On Sat, 4 Jan 2003, Andrew McGregor wrote:
>
>> Or else find that the NV3x has some stonking quick CPU embedded, and apps
>> talk GLX to it...
>>
>> Strange how noone objects to APM BIOS calls or ACPI.
>
> Actually, I object to this.
> On my via 686a, the advice on this list for getting the power saving was
> to use ACPI (after setting some bits in PCI config space). But lvcool
> program showed how to do this without proprietary programs, and I
> adapted it to bit of kernel code:
>
<snip>
>
> And I don't need to run any proprietary code during normal system run. I
> still need to use BIOS to boot and to poweroff the system, but
> that will be solved as well.
>
>
> --
> Matan Ziv-Av. matan@svgalib.org
>
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: Gauntlet Set NOW!
@ 2003-01-04 10:38 Hell.Surfers
2003-01-05 23:40 ` Florian Schmitt
0 siblings, 1 reply; 32+ messages in thread
From: Hell.Surfers @ 2003-01-04 10:38 UTC (permalink / raw)
To: andrew, andre, ryan, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 381 bytes --]
what war am I fighting? I decided that the battle is lost a long time ago, im showing the community its fate, eventual collapse from a unrealistic GPL that needs a decent funeral, sue NVidia and I collapse it, when I lose.
Dean McEwan, If the drugs don't work, [sarcasm] take more...[/sarcasm].
On Sat, 04 Jan 2003 23:28:10 +1300 Andrew McGregor <andrew@indranet.co.nz> wrote:
[-- Attachment #2: Type: message/rfc822, Size: 3875 bytes --]
From: Andrew McGregor <andrew@indranet.co.nz>
To: Andre Hedrick <andre@linux-ide.org>, Hell.Surfers@cwctv.net
Cc: ryan@michonline.com, linux-kernel@vger.kernel.org
Subject: RE: Gauntlet Set NOW!
Date: Sat, 04 Jan 2003 23:28:10 +1300
Message-ID: <142020000.1041676090@localhost.localdomain>
How about:
http://www.celoxica.com/
http://www.intel.com/design/network/products/npfamily/index.htm
http://www.hifn.com/products/Security.html
for some alternative ways to the end.
Dean, mate, give up. This is a battle you will not win, and it would
preserve the freedom you wish to have more if you did not fight.
Unfortunately, the tension between IP, profit, and technological progress
is complex. Fortunately, there is room in the ecosystem for many views,
and some of us are capable of holding different views for different
projects.
I really respect Andre for what he's trying to do, and for what he has
done. I don't see any history which gives me any reason to respect you,
and you're wearing out your default credit real fast. My own history is
more at the IETF than in Linux, but check out something called HIP and the
manet working group for an example. And www.indranet.co.nz too. I only
mention these because they're kind of obscure in the Linux context.
Andrew
--On Saturday, January 04, 2003 02:07:27 -0800 Andre Hedrick
<andre@linux-ide.org> wrote:
>
> http://www.xilinx.com/ipcenter/catalog/logicore/docs/cam.pdf
> http://aggregate.org/ECard/
> http://www.utmc.com/cam/
> http://www.openskytech.com/ContentAddressableMemory.htm
> http://www.pcs.cnu.edu/~rhodson/cam/CamPage.html
> http://ipdps.eece.unm.edu/2000/raw/18000884.pdf
> http://www.infoworld.com/research/articles/01/05/15/01051524605.xml
> http://www.stanford.edu/class/ee371/handouts/DramCam92.pdf
> http://www.altera.com/support/software/eda_quartus2/glossary/def_cam.htm
> http://www.altera.com/literature/po/apex_cam_ss.pdf
> http://www.esscirc.org/papers-96/26.pdf
>
> The list is long, the histroy is there.
>
>
>
> On Sat, 4 Jan 2003 Hell.Surfers@cwctv.net wrote:
>
>> moving the whole thing into firmware? Interesting, got _any_ meat on the
>> bone?
>>
>> Dean McEwan, If the drugs don't work, [sarcasm] take more...[/sarcasm].
>>
>> On Sat, 4 Jan 2003 01:45:44 -0800 (PST) Andre Hedrick
>> <andre@linux-ide.org> wrote:
>>
>
> Andre Hedrick
> LAD Storage Consulting Group
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-04 10:38 Hell.Surfers
@ 2003-01-05 23:40 ` Florian Schmitt
0 siblings, 0 replies; 32+ messages in thread
From: Florian Schmitt @ 2003-01-05 23:40 UTC (permalink / raw)
To: Hell.Surfers, linux-kernel
On Saturday 04 January 2003 11:38, Hell.Surfers@cwctv.net wrote:
> what war am I fighting? I decided that the battle is lost a long time ago,
> im showing the community its fate, eventual collapse from a unrealistic GPL
> that needs a decent funeral, sue NVidia and I collapse it, when I lose.
What kind of battle? Do you really want to go to court?
I'm so sorry to spoil your fun, but you don't have any chance to get a case.
As long as you don't have contributed anything significant to the kernel,
absolutely none of _your_ rights have been violated. And no, you can't sue on
behalf of others, who just don't want that.
So start coding or shut up. Oh, and you should hope that Linus still accepts
patches from you...
cheers,
Flo
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: Gauntlet Set NOW!
@ 2003-01-04 10:12 Hell.Surfers
2003-01-04 10:42 ` Andrew McGregor
0 siblings, 1 reply; 32+ messages in thread
From: Hell.Surfers @ 2003-01-04 10:12 UTC (permalink / raw)
To: andre, andrew, ryan, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 221 bytes --]
Sounds like a jumped up PIC chip, cant think why isnt done yet.
Dean McEwan, If the drugs don't work, [sarcasm] take more...[/sarcasm].
On Sat, 4 Jan 2003 02:07:27 -0800 (PST) Andre Hedrick <andre@linux-ide.org> wrote:
[-- Attachment #2: Type: message/rfc822, Size: 1678 bytes --]
From: Andre Hedrick <andre@linux-ide.org>
To: Hell.Surfers@cwctv.net
Cc: andrew@indranet.co.nz, ryan@michonline.com, linux-kernel@vger.kernel.org
Subject: RE: Gauntlet Set NOW!
Date: Sat, 4 Jan 2003 02:07:27 -0800 (PST)
Message-ID: <Pine.LNX.4.10.10301040201590.421-100000@master.linux-ide.org>
http://www.xilinx.com/ipcenter/catalog/logicore/docs/cam.pdf
http://aggregate.org/ECard/
http://www.utmc.com/cam/
http://www.openskytech.com/ContentAddressableMemory.htm
http://www.pcs.cnu.edu/~rhodson/cam/CamPage.html
http://ipdps.eece.unm.edu/2000/raw/18000884.pdf
http://www.infoworld.com/research/articles/01/05/15/01051524605.xml
http://www.stanford.edu/class/ee371/handouts/DramCam92.pdf
http://www.altera.com/support/software/eda_quartus2/glossary/def_cam.htm
http://www.altera.com/literature/po/apex_cam_ss.pdf
http://www.esscirc.org/papers-96/26.pdf
The list is long, the histroy is there.
On Sat, 4 Jan 2003 Hell.Surfers@cwctv.net wrote:
> moving the whole thing into firmware? Interesting, got _any_ meat on the bone?
>
> Dean McEwan, If the drugs don't work, [sarcasm] take more...[/sarcasm].
>
> On Sat, 4 Jan 2003 01:45:44 -0800 (PST) Andre Hedrick <andre@linux-ide.org> wrote:
>
Andre Hedrick
LAD Storage Consulting Group
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: Gauntlet Set NOW!
2003-01-04 10:12 Hell.Surfers
@ 2003-01-04 10:42 ` Andrew McGregor
0 siblings, 0 replies; 32+ messages in thread
From: Andrew McGregor @ 2003-01-04 10:42 UTC (permalink / raw)
To: Hell.Surfers, andre, ryan, linux-kernel
Welcome to the kill file, Mr Troll.
For your edification, it *is* done. Frequently. Probably even in the
settop box you're posting with.
--On Saturday, January 04, 2003 10:12:49 +0000 Hell.Surfers@cwctv.net wrote:
> Sounds like a jumped up PIC chip, cant think why isnt done yet.
>
> Dean McEwan, If the drugs don't work, [sarcasm] take more...[/sarcasm].
>
> On Sat, 4 Jan 2003 02:07:27 -0800 (PST) Andre Hedrick
> <andre@linux-ide.org> wrote:
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: Gauntlet Set NOW!
@ 2003-01-04 9:55 Hell.Surfers
2003-01-04 10:07 ` Andre Hedrick
0 siblings, 1 reply; 32+ messages in thread
From: Hell.Surfers @ 2003-01-04 9:55 UTC (permalink / raw)
To: andre, andrew, ryan, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 238 bytes --]
moving the whole thing into firmware? Interesting, got _any_ meat on the bone?
Dean McEwan, If the drugs don't work, [sarcasm] take more...[/sarcasm].
On Sat, 4 Jan 2003 01:45:44 -0800 (PST) Andre Hedrick <andre@linux-ide.org> wrote:
[-- Attachment #2: Type: message/rfc822, Size: 6170 bytes --]
From: Andre Hedrick <andre@linux-ide.org>
To: Andrew McGregor <andrew@indranet.co.nz>
Cc: Ryan Anderson <ryan@michonline.com>, linux-kernel@vger.kernel.org
Subject: Re: Gauntlet Set NOW!
Date: Sat, 4 Jan 2003 01:45:44 -0800 (PST)
Message-ID: <Pine.LNX.4.10.10301040135420.421-100000@master.linux-ide.org>
There is a solution out there and as soon as I can verify it works,
gameover for anyone thinking they will get access to soft IP again by
banging a dead drum.
CAM, Content Addressable Memory on a card.
Usage will be to stuff any binary soft code now reclassified as "firmware"
into a piece of hardware. Set the addressable memory hooks for what is
now called the open source wrapper for binary objects, and game is over.
There is hardware with a software core which is totally embedded for all
practical purposes. Use your existing GPL wrapper and call it you new
driver! Funny how people come up with ways to thwart the sticky fingers
to rip off IP and hard work. Lets see how GPL goes to get soft IP locked
into hardware.
Force rules and license into places they do not belong, and evolution
happens to push back and impose the boundaries of IP.
Surprised ? Not me.
Cheers,
Andre Hedrick
LAD Storage Consulting Group
On Sat, 4 Jan 2003, Andrew McGregor wrote:
> I am aware that there was little confirmation from other developers (so far
> as I remember, there was some, plus a few dissenting views).
>
> I was *only* talking about Linus' position, which I admit was being
> selective in that context.
>
> My real point was this: It appears to me that NVIDIA have gone as far as
> they can in releasing the code to their driver. It has certainly been my
> own policy to do so with various code, and the result was not GPL because
> of legal constraints.
>
> Punishing a company who have, with goodwill, opened up their code as far as
> they were allowed by preexisting agreements for license issues is not a
> smart move, and will only hurt the free software community in the long run.
>
> And to those who say 'well, just release the specs': Quite likely NVIDIA
> did not design all the subsystems of their chips, but instead bought 'IP
> block' licenses from someone else. The license NVIDIA have access to those
> under probably will not allow that release, whether NVIDIA would like to
> release that information or not.
>
> Effectively, the binary part of the driver can be viewed as part of the
> hardware, just as much as it can be viewed as part of the kernel. It is
> constrained in hardware-like ways, not much like software at all.
>
> My view, for what it's worth, is that if binary modules are not allowed by
> the kernel being GPL, then it is worth going to some trouble to allow
> binary hardware drivers by some other mechanism than a module, since it is
> effectively impossible to change the license on the kernel now, as you
> correctly point out. Even if they want to, many hardware vendors will not
> be able to release full specifications or GPL code for quite some time, and
> it is better to allow those that are motivated to to open up as much as
> they can, than to require only that hardware for which full information or
> GPL-able code is available to be used with Linux. And saying that the
> vendor then has to assume all the maintenance trouble keeps the pressure on
> them to evolve toward openness.
>
> Andrew
>
> --On Saturday, January 04, 2003 02:12:09 -0500 Ryan Anderson
> <ryan@michonline.com> wrote:
>
> > On Sat, Jan 04, 2003 at 12:56:53PM +1300, Andrew McGregor wrote:
> >
> > [snip]
> >
> >> Linus has made it quite clear in the past that his position on binary
> >> modules is that they are explicitly allowed, but that the maintainers of
> >> such a thing 'get everything they deserve' in terms of maintenance
> >> hassle.
> >
> > I *really* think you need to do some searches on this list to verify
> > this statement.
> >
> > Let me summarize what I remember from past discussions of this nature.
> >
> > Linus put his code under the GPL. Contributions came in, under the same
> > license. At some point, the first binary only module showed up. When
> > asked about the legality, Linus said something to the effect of, "I
> > think they're ok."
> >
> > Note the lack of clarification from the other (miriad) copyright
> > holders?
> >
> > In summary - If you want to write binary only modules, you need to talk
> > to a lawyer that understands the issues involved. "Linus said they were
> > ok" doesn't even begin to encompass the number of copyright holders
> > involved.
> >
> >
> > --
> >
> > Ryan Anderson
> > sometimes Pug Majere
> >
> >
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: Gauntlet Set NOW!
2003-01-04 9:55 Hell.Surfers
@ 2003-01-04 10:07 ` Andre Hedrick
2003-01-04 10:28 ` Andrew McGregor
0 siblings, 1 reply; 32+ messages in thread
From: Andre Hedrick @ 2003-01-04 10:07 UTC (permalink / raw)
To: Hell.Surfers; +Cc: andrew, ryan, linux-kernel
http://www.xilinx.com/ipcenter/catalog/logicore/docs/cam.pdf
http://aggregate.org/ECard/
http://www.utmc.com/cam/
http://www.openskytech.com/ContentAddressableMemory.htm
http://www.pcs.cnu.edu/~rhodson/cam/CamPage.html
http://ipdps.eece.unm.edu/2000/raw/18000884.pdf
http://www.infoworld.com/research/articles/01/05/15/01051524605.xml
http://www.stanford.edu/class/ee371/handouts/DramCam92.pdf
http://www.altera.com/support/software/eda_quartus2/glossary/def_cam.htm
http://www.altera.com/literature/po/apex_cam_ss.pdf
http://www.esscirc.org/papers-96/26.pdf
The list is long, the histroy is there.
On Sat, 4 Jan 2003 Hell.Surfers@cwctv.net wrote:
> moving the whole thing into firmware? Interesting, got _any_ meat on the bone?
>
> Dean McEwan, If the drugs don't work, [sarcasm] take more...[/sarcasm].
>
> On Sat, 4 Jan 2003 01:45:44 -0800 (PST) Andre Hedrick <andre@linux-ide.org> wrote:
>
Andre Hedrick
LAD Storage Consulting Group
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: Gauntlet Set NOW!
2003-01-04 10:07 ` Andre Hedrick
@ 2003-01-04 10:28 ` Andrew McGregor
0 siblings, 0 replies; 32+ messages in thread
From: Andrew McGregor @ 2003-01-04 10:28 UTC (permalink / raw)
To: Andre Hedrick, Hell.Surfers; +Cc: ryan, linux-kernel
How about:
http://www.celoxica.com/
http://www.intel.com/design/network/products/npfamily/index.htm
http://www.hifn.com/products/Security.html
for some alternative ways to the end.
Dean, mate, give up. This is a battle you will not win, and it would
preserve the freedom you wish to have more if you did not fight.
Unfortunately, the tension between IP, profit, and technological progress
is complex. Fortunately, there is room in the ecosystem for many views,
and some of us are capable of holding different views for different
projects.
I really respect Andre for what he's trying to do, and for what he has
done. I don't see any history which gives me any reason to respect you,
and you're wearing out your default credit real fast. My own history is
more at the IETF than in Linux, but check out something called HIP and the
manet working group for an example. And www.indranet.co.nz too. I only
mention these because they're kind of obscure in the Linux context.
Andrew
--On Saturday, January 04, 2003 02:07:27 -0800 Andre Hedrick
<andre@linux-ide.org> wrote:
>
> http://www.xilinx.com/ipcenter/catalog/logicore/docs/cam.pdf
> http://aggregate.org/ECard/
> http://www.utmc.com/cam/
> http://www.openskytech.com/ContentAddressableMemory.htm
> http://www.pcs.cnu.edu/~rhodson/cam/CamPage.html
> http://ipdps.eece.unm.edu/2000/raw/18000884.pdf
> http://www.infoworld.com/research/articles/01/05/15/01051524605.xml
> http://www.stanford.edu/class/ee371/handouts/DramCam92.pdf
> http://www.altera.com/support/software/eda_quartus2/glossary/def_cam.htm
> http://www.altera.com/literature/po/apex_cam_ss.pdf
> http://www.esscirc.org/papers-96/26.pdf
>
> The list is long, the histroy is there.
>
>
>
> On Sat, 4 Jan 2003 Hell.Surfers@cwctv.net wrote:
>
>> moving the whole thing into firmware? Interesting, got _any_ meat on the
>> bone?
>>
>> Dean McEwan, If the drugs don't work, [sarcasm] take more...[/sarcasm].
>>
>> On Sat, 4 Jan 2003 01:45:44 -0800 (PST) Andre Hedrick
>> <andre@linux-ide.org> wrote:
>>
>
> Andre Hedrick
> LAD Storage Consulting Group
>
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Why is Nvidia given GPL'd code to use in closed source drivers?
@ 2003-01-03 20:31 Richard Stallman
2003-01-03 23:01 ` Gauntlet Set NOW! Andre Hedrick
0 siblings, 1 reply; 32+ messages in thread
From: Richard Stallman @ 2003-01-03 20:31 UTC (permalink / raw)
To: andre; +Cc: mark, billh, paul, riel, Hell.Surfers, linux-kernel
What I see is a lot of people wait for new technology to be supported,
yet do nothing to enable the ones who have access and are willing to take
the risks of dealing with the vendors who are paranoid.
Yes, that is a shame. How can we change that? We have to spread the
word through our community that encouraging and rewarding Nvidia is
self-destructive until they cooperate with our freedom.
What if they decide to thumb the nose at you?
I believe that is what they are doing now. (Please correct me
if I'm wrong--I would be glad to hear it.)
What if they decide to withdraw their drivers?
We would not lose any free software that way, and it might increase
the impetus for people to work improving on the free drivers. In the
long run, this would be for the best.
If people want to use "non-free drivers", they choose to execute the
freedom to do so. Now, what is clearly stated in your text is, FREEDOM
means the vendor of the "non-free drivers" has NONE!
Making a program non-free is denying other people the freedom to
study, change and/or redistribute it. It is an act of domination. To
speak of the "freedom" to dominate others is to stretch the concept of
freedom into a Russell paradox.
^ permalink raw reply [flat|nested] 32+ messages in thread* Gauntlet Set NOW!
2003-01-03 20:31 Why is Nvidia given GPL'd code to use in closed source drivers? Richard Stallman
@ 2003-01-03 23:01 ` Andre Hedrick
2003-01-03 23:56 ` Andrew McGregor
2003-01-09 7:28 ` Richard Stallman
0 siblings, 2 replies; 32+ messages in thread
From: Andre Hedrick @ 2003-01-03 23:01 UTC (permalink / raw)
To: Richard Stallman; +Cc: linux-kernel
Richard,
I am going to sell and ship binary only models which is solely a protocol.
One which is in a working group and is not an offical document but will be
ratified soon.
I will not release the source code period. It is not a derived work.
It can and will be capable of running it on other unixs as well has have a
version for microsoft and maybe apple.
The API and boundary will execute all kernel operations and calls outside
of the core protocol. There is no hardware period. It is pure software.
I am prepared to show the the source of the API callers; however, given
the anal nature of the review I expect. I need a few more days to extract
every damn possible kernel function or caller that is even close to my
property. The object generated from that file will then be linked with a
private closed source library, which may or may not be setup under LGPL.
This would be the Library GPL and not the updated Lesser GPL.
But I am not prepared to set this position yet.
Are you prepared to SUE me ?
Are you prepared to SUE others like me ?
Are you prepared to SUE every company in Silicon Valley for embedded ?
Are you prepared to SUE every settop box vendor ?
Either, put up or walk on this issue.
Fear, Threats, and Intimidation resulting from a willful grey zone so
clearly and cleverly designed by yourself is not acceptable.
Since I am in a position of loosing revenue today because of this silly
issue of usage of headers and not any inline code inside them, I will seek
counter damages if I am forced into litigation.
Regards,
Andre Hedrick
LAD Storage Consulting Group
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-03 23:01 ` Gauntlet Set NOW! Andre Hedrick
@ 2003-01-03 23:56 ` Andrew McGregor
2003-01-04 7:12 ` Ryan Anderson
2003-01-04 23:44 ` Richard Stallman
2003-01-09 7:28 ` Richard Stallman
1 sibling, 2 replies; 32+ messages in thread
From: Andrew McGregor @ 2003-01-03 23:56 UTC (permalink / raw)
To: Andre Hedrick, Richard Stallman; +Cc: linux-kernel
Hear hear!
RMS, I've heckled you in person on this subject, so now I'm going to do it
online too.
One aspect of freedom you carefully ignore is that of the writers of code
to do what they will with it. Now, in general I and my company do place
our code under whichever free license makes sense for the particular
project, as a matter of principle. So we have produced code under GPL
(linux kernel and emacs variants), BSD licenses (network protocols, BSD
kernel, python libraries), patches to both python and perl under their own
licenses, and even MPL code with the 'original developer' rights
deliberately given to another company to maintain and distribute. We are
not hostile to free software, but neither are we to the right of original
authors to make their own decisions.
But sometimes we can't make things free, either because it comes to close
to core IP which we are legally bound to protect, or because it's a derived
work of something we bought and don't ourselves have the right to
redistribute. Often this is hardware support code, sometimes it compiles
into hardware (embedded FPGAs). Even so, if we can we make it open-source,
closed-distribution (in other words, to get the code you must have bought
the license to the original IP). This preserves as much freedom as we
ourselves have been given the option to.
Linus has made it quite clear in the past that his position on binary
modules is that they are explicitly allowed, but that the maintainers of
such a thing 'get everything they deserve' in terms of maintenance hassle.
Which is fair enough, the developers of the GPL kernel don't need the
hassle of maintaining APIs to the degree that would guarantee backwards
compatibility for pure binary modules. To keep the kernel as good as it is
and continue improving it, that is necessary.
To explicitly allow binary modules implies that the module loading process
is not linking in the terms of the GPL. The *only* grey area is the status
of inline functions and assembler in the hearder files, and clever
construction of a module's shim driver can deal with that one.
Andre, what I see you doing here is exactly what NVIDIA already did, which
is (L)GPL the interface to the kernel and keep the core algorithms
proprietary. I don't know what your constraints are, but it doesn't
matter, you are entitled to do that. Even if it is simply that you want to
make money off the code. I take it that it's an iSCSI target for the Linux
VFS or block device layer? That would be very cool, and certainly worth
basing a company on.
I understand from a former NVIDIA employee that NVIDIA are not able to GPL
the whole driver since some of it is not their code; I suspect that some of
the non-NVIDIA code actually belongs to Microsoft. So they have opened it
up to the extent possible for them.
Nowhere in any of this do I see anyone doing anything that is actually
wrong. By sueing either Andre or NVIDIA, Richard, you'd be the one
committing the wrong, by taking away either Andre's freedom to decide on
his business plans, or the communities access to NVIDIAs hardware, which
they have provided with considerable goodwill. And both Andre's goodwill
and NVIDIAs are of considerable value to the community.
Neither of these are good test cases for the spirit of the GPL; the past
events of, for instance, vendors refusing to release source for betas of a
Linux distribution, are far more to the point.
And a test case based on kernel binary modules would be very destructive to
the free software community. First because it is likely to cause a mass
exodus of vendors from Linux. Where would they go? BSD, of course, where
no such issue can arise, as well as a variety of purely proprietary
systems. But more importantly, it would reinforce the whole concept of
intellectual property in a manner that, in the end, will result in an even
more hostile to freedom environment. I think it is important for the free
software community to remember that the freedom of all creators of ideas is
vitally important, and for us not to contribute to the shackles being
placed on music, literature, and science. For ultimately, they are more
important than software alone.
Andrew
--On Friday, January 03, 2003 15:01:51 -0800 Andre Hedrick
<andre@linux-ide.org> wrote:
>
> Richard,
>
> I am going to sell and ship binary only models which is solely a protocol.
> One which is in a working group and is not an offical document but will be
> ratified soon.
>
> I will not release the source code period. It is not a derived work.
> It can and will be capable of running it on other unixs as well has have a
> version for microsoft and maybe apple.
>
> The API and boundary will execute all kernel operations and calls outside
> of the core protocol. There is no hardware period. It is pure software.
> I am prepared to show the the source of the API callers; however, given
> the anal nature of the review I expect. I need a few more days to extract
> every damn possible kernel function or caller that is even close to my
> property. The object generated from that file will then be linked with a
> private closed source library, which may or may not be setup under LGPL.
>
> This would be the Library GPL and not the updated Lesser GPL.
> But I am not prepared to set this position yet.
>
> Are you prepared to SUE me ?
> Are you prepared to SUE others like me ?
> Are you prepared to SUE every company in Silicon Valley for embedded ?
> Are you prepared to SUE every settop box vendor ?
>
> Either, put up or walk on this issue.
>
> Fear, Threats, and Intimidation resulting from a willful grey zone so
> clearly and cleverly designed by yourself is not acceptable.
>
> Since I am in a position of loosing revenue today because of this silly
> issue of usage of headers and not any inline code inside them, I will seek
> counter damages if I am forced into litigation.
>
> Regards,
>
> Andre Hedrick
> LAD Storage Consulting Group
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-03 23:56 ` Andrew McGregor
@ 2003-01-04 7:12 ` Ryan Anderson
2003-01-04 9:14 ` Andrew McGregor
2003-01-04 23:44 ` Richard Stallman
1 sibling, 1 reply; 32+ messages in thread
From: Ryan Anderson @ 2003-01-04 7:12 UTC (permalink / raw)
To: Andrew McGregor; +Cc: linux-kernel
On Sat, Jan 04, 2003 at 12:56:53PM +1300, Andrew McGregor wrote:
[snip]
> Linus has made it quite clear in the past that his position on binary
> modules is that they are explicitly allowed, but that the maintainers of
> such a thing 'get everything they deserve' in terms of maintenance hassle.
I *really* think you need to do some searches on this list to verify
this statement.
Let me summarize what I remember from past discussions of this nature.
Linus put his code under the GPL. Contributions came in, under the same
license. At some point, the first binary only module showed up. When
asked about the legality, Linus said something to the effect of, "I
think they're ok."
Note the lack of clarification from the other (miriad) copyright
holders?
In summary - If you want to write binary only modules, you need to talk
to a lawyer that understands the issues involved. "Linus said they were
ok" doesn't even begin to encompass the number of copyright holders
involved.
--
Ryan Anderson
sometimes Pug Majere
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-04 7:12 ` Ryan Anderson
@ 2003-01-04 9:14 ` Andrew McGregor
2003-01-04 9:45 ` Andre Hedrick
0 siblings, 1 reply; 32+ messages in thread
From: Andrew McGregor @ 2003-01-04 9:14 UTC (permalink / raw)
To: Ryan Anderson; +Cc: linux-kernel
I am aware that there was little confirmation from other developers (so far
as I remember, there was some, plus a few dissenting views).
I was *only* talking about Linus' position, which I admit was being
selective in that context.
My real point was this: It appears to me that NVIDIA have gone as far as
they can in releasing the code to their driver. It has certainly been my
own policy to do so with various code, and the result was not GPL because
of legal constraints.
Punishing a company who have, with goodwill, opened up their code as far as
they were allowed by preexisting agreements for license issues is not a
smart move, and will only hurt the free software community in the long run.
And to those who say 'well, just release the specs': Quite likely NVIDIA
did not design all the subsystems of their chips, but instead bought 'IP
block' licenses from someone else. The license NVIDIA have access to those
under probably will not allow that release, whether NVIDIA would like to
release that information or not.
Effectively, the binary part of the driver can be viewed as part of the
hardware, just as much as it can be viewed as part of the kernel. It is
constrained in hardware-like ways, not much like software at all.
My view, for what it's worth, is that if binary modules are not allowed by
the kernel being GPL, then it is worth going to some trouble to allow
binary hardware drivers by some other mechanism than a module, since it is
effectively impossible to change the license on the kernel now, as you
correctly point out. Even if they want to, many hardware vendors will not
be able to release full specifications or GPL code for quite some time, and
it is better to allow those that are motivated to to open up as much as
they can, than to require only that hardware for which full information or
GPL-able code is available to be used with Linux. And saying that the
vendor then has to assume all the maintenance trouble keeps the pressure on
them to evolve toward openness.
Andrew
--On Saturday, January 04, 2003 02:12:09 -0500 Ryan Anderson
<ryan@michonline.com> wrote:
> On Sat, Jan 04, 2003 at 12:56:53PM +1300, Andrew McGregor wrote:
>
> [snip]
>
>> Linus has made it quite clear in the past that his position on binary
>> modules is that they are explicitly allowed, but that the maintainers of
>> such a thing 'get everything they deserve' in terms of maintenance
>> hassle.
>
> I *really* think you need to do some searches on this list to verify
> this statement.
>
> Let me summarize what I remember from past discussions of this nature.
>
> Linus put his code under the GPL. Contributions came in, under the same
> license. At some point, the first binary only module showed up. When
> asked about the legality, Linus said something to the effect of, "I
> think they're ok."
>
> Note the lack of clarification from the other (miriad) copyright
> holders?
>
> In summary - If you want to write binary only modules, you need to talk
> to a lawyer that understands the issues involved. "Linus said they were
> ok" doesn't even begin to encompass the number of copyright holders
> involved.
>
>
> --
>
> Ryan Anderson
> sometimes Pug Majere
>
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-04 9:14 ` Andrew McGregor
@ 2003-01-04 9:45 ` Andre Hedrick
2003-01-04 10:01 ` Andrew McGregor
0 siblings, 1 reply; 32+ messages in thread
From: Andre Hedrick @ 2003-01-04 9:45 UTC (permalink / raw)
To: Andrew McGregor; +Cc: Ryan Anderson, linux-kernel
There is a solution out there and as soon as I can verify it works,
gameover for anyone thinking they will get access to soft IP again by
banging a dead drum.
CAM, Content Addressable Memory on a card.
Usage will be to stuff any binary soft code now reclassified as "firmware"
into a piece of hardware. Set the addressable memory hooks for what is
now called the open source wrapper for binary objects, and game is over.
There is hardware with a software core which is totally embedded for all
practical purposes. Use your existing GPL wrapper and call it you new
driver! Funny how people come up with ways to thwart the sticky fingers
to rip off IP and hard work. Lets see how GPL goes to get soft IP locked
into hardware.
Force rules and license into places they do not belong, and evolution
happens to push back and impose the boundaries of IP.
Surprised ? Not me.
Cheers,
Andre Hedrick
LAD Storage Consulting Group
On Sat, 4 Jan 2003, Andrew McGregor wrote:
> I am aware that there was little confirmation from other developers (so far
> as I remember, there was some, plus a few dissenting views).
>
> I was *only* talking about Linus' position, which I admit was being
> selective in that context.
>
> My real point was this: It appears to me that NVIDIA have gone as far as
> they can in releasing the code to their driver. It has certainly been my
> own policy to do so with various code, and the result was not GPL because
> of legal constraints.
>
> Punishing a company who have, with goodwill, opened up their code as far as
> they were allowed by preexisting agreements for license issues is not a
> smart move, and will only hurt the free software community in the long run.
>
> And to those who say 'well, just release the specs': Quite likely NVIDIA
> did not design all the subsystems of their chips, but instead bought 'IP
> block' licenses from someone else. The license NVIDIA have access to those
> under probably will not allow that release, whether NVIDIA would like to
> release that information or not.
>
> Effectively, the binary part of the driver can be viewed as part of the
> hardware, just as much as it can be viewed as part of the kernel. It is
> constrained in hardware-like ways, not much like software at all.
>
> My view, for what it's worth, is that if binary modules are not allowed by
> the kernel being GPL, then it is worth going to some trouble to allow
> binary hardware drivers by some other mechanism than a module, since it is
> effectively impossible to change the license on the kernel now, as you
> correctly point out. Even if they want to, many hardware vendors will not
> be able to release full specifications or GPL code for quite some time, and
> it is better to allow those that are motivated to to open up as much as
> they can, than to require only that hardware for which full information or
> GPL-able code is available to be used with Linux. And saying that the
> vendor then has to assume all the maintenance trouble keeps the pressure on
> them to evolve toward openness.
>
> Andrew
>
> --On Saturday, January 04, 2003 02:12:09 -0500 Ryan Anderson
> <ryan@michonline.com> wrote:
>
> > On Sat, Jan 04, 2003 at 12:56:53PM +1300, Andrew McGregor wrote:
> >
> > [snip]
> >
> >> Linus has made it quite clear in the past that his position on binary
> >> modules is that they are explicitly allowed, but that the maintainers of
> >> such a thing 'get everything they deserve' in terms of maintenance
> >> hassle.
> >
> > I *really* think you need to do some searches on this list to verify
> > this statement.
> >
> > Let me summarize what I remember from past discussions of this nature.
> >
> > Linus put his code under the GPL. Contributions came in, under the same
> > license. At some point, the first binary only module showed up. When
> > asked about the legality, Linus said something to the effect of, "I
> > think they're ok."
> >
> > Note the lack of clarification from the other (miriad) copyright
> > holders?
> >
> > In summary - If you want to write binary only modules, you need to talk
> > to a lawyer that understands the issues involved. "Linus said they were
> > ok" doesn't even begin to encompass the number of copyright holders
> > involved.
> >
> >
> > --
> >
> > Ryan Anderson
> > sometimes Pug Majere
> >
> >
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-04 9:45 ` Andre Hedrick
@ 2003-01-04 10:01 ` Andrew McGregor
2003-01-04 19:31 ` Matan Ziv-Av
2003-01-06 10:56 ` Helge Hafting
0 siblings, 2 replies; 32+ messages in thread
From: Andrew McGregor @ 2003-01-04 10:01 UTC (permalink / raw)
To: Andre Hedrick; +Cc: Ryan Anderson, linux-kernel
Or else find that the NV3x has some stonking quick CPU embedded, and apps
talk GLX to it...
Strange how noone objects to APM BIOS calls or ACPI. I suspect a similar
effect can be had by sticking some flash on the card, then mapping it
(cached in system RAM for performance, of course!) and jumping into it.
Then provide a proprietary app (for instance, the binary part of the X
server, for a video driver) to load the right stuff in the flash. For that
matter, you could just copy_from_user the code straight out of a userland
binary. Not to mention fun with FPGAs. Ever seen DOOM run on a system
with no CPU at all? I have.
There are umpteen ways one can frustrate the pedants, and nothing to be
gained on either side by their insistence. And plenty to lose, because how
many companies for whom Linux is already marginal will bother?
I reckon if this is pushed that NVIDIA will abandon Linux and just say 'You
want UNIX on ix86? Buy the drivers from Accelerated X or whoever, or use
FreeBSD'. And probably I will too, and go and use a BSD for my product.
And maybe Andre will too, and that just makes free software (meaning GPL)
look bad. Which would not be good for the world in general.
Andrew
--On Saturday, January 04, 2003 01:45:44 -0800 Andre Hedrick
<andre@linux-ide.org> wrote:
>
> There is a solution out there and as soon as I can verify it works,
> gameover for anyone thinking they will get access to soft IP again by
> banging a dead drum.
>
> CAM, Content Addressable Memory on a card.
>
> Usage will be to stuff any binary soft code now reclassified as "firmware"
> into a piece of hardware. Set the addressable memory hooks for what is
> now called the open source wrapper for binary objects, and game is over.
>
> There is hardware with a software core which is totally embedded for all
> practical purposes. Use your existing GPL wrapper and call it you new
> driver! Funny how people come up with ways to thwart the sticky fingers
> to rip off IP and hard work. Lets see how GPL goes to get soft IP locked
> into hardware.
>
> Force rules and license into places they do not belong, and evolution
> happens to push back and impose the boundaries of IP.
>
> Surprised ? Not me.
>
> Cheers,
>
> Andre Hedrick
> LAD Storage Consulting Group
>
>
> On Sat, 4 Jan 2003, Andrew McGregor wrote:
>
>> I am aware that there was little confirmation from other developers (so
>> far as I remember, there was some, plus a few dissenting views).
>>
>> I was *only* talking about Linus' position, which I admit was being
>> selective in that context.
>>
>> My real point was this: It appears to me that NVIDIA have gone as far
>> as they can in releasing the code to their driver. It has certainly
>> been my own policy to do so with various code, and the result was not
>> GPL because of legal constraints.
>>
>> Punishing a company who have, with goodwill, opened up their code as far
>> as they were allowed by preexisting agreements for license issues is
>> not a smart move, and will only hurt the free software community in the
>> long run.
>>
>> And to those who say 'well, just release the specs': Quite likely
>> NVIDIA did not design all the subsystems of their chips, but instead
>> bought 'IP block' licenses from someone else. The license NVIDIA have
>> access to those under probably will not allow that release, whether
>> NVIDIA would like to release that information or not.
>>
>> Effectively, the binary part of the driver can be viewed as part of the
>> hardware, just as much as it can be viewed as part of the kernel. It is
>> constrained in hardware-like ways, not much like software at all.
>>
>> My view, for what it's worth, is that if binary modules are not allowed
>> by the kernel being GPL, then it is worth going to some trouble to
>> allow binary hardware drivers by some other mechanism than a module,
>> since it is effectively impossible to change the license on the kernel
>> now, as you correctly point out. Even if they want to, many hardware
>> vendors will not be able to release full specifications or GPL code for
>> quite some time, and it is better to allow those that are motivated to
>> to open up as much as they can, than to require only that hardware for
>> which full information or GPL-able code is available to be used with
>> Linux. And saying that the vendor then has to assume all the
>> maintenance trouble keeps the pressure on them to evolve toward
>> openness.
>>
>> Andrew
>>
>> --On Saturday, January 04, 2003 02:12:09 -0500 Ryan Anderson
>> <ryan@michonline.com> wrote:
>>
>> > On Sat, Jan 04, 2003 at 12:56:53PM +1300, Andrew McGregor wrote:
>> >
>> > [snip]
>> >
>> >> Linus has made it quite clear in the past that his position on binary
>> >> modules is that they are explicitly allowed, but that the maintainers
>> >> of such a thing 'get everything they deserve' in terms of maintenance
>> >> hassle.
>> >
>> > I *really* think you need to do some searches on this list to verify
>> > this statement.
>> >
>> > Let me summarize what I remember from past discussions of this nature.
>> >
>> > Linus put his code under the GPL. Contributions came in, under the
>> > same license. At some point, the first binary only module showed up.
>> > When asked about the legality, Linus said something to the effect of,
>> > "I think they're ok."
>> >
>> > Note the lack of clarification from the other (miriad) copyright
>> > holders?
>> >
>> > In summary - If you want to write binary only modules, you need to talk
>> > to a lawyer that understands the issues involved. "Linus said they
>> > were ok" doesn't even begin to encompass the number of copyright
>> > holders involved.
>> >
>> >
>> > --
>> >
>> > Ryan Anderson
>> > sometimes Pug Majere
>> >
>> >
>>
>>
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
>> in the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-04 10:01 ` Andrew McGregor
@ 2003-01-04 19:31 ` Matan Ziv-Av
2003-01-04 19:43 ` Andrew McGregor
2003-01-06 10:56 ` Helge Hafting
1 sibling, 1 reply; 32+ messages in thread
From: Matan Ziv-Av @ 2003-01-04 19:31 UTC (permalink / raw)
To: Andrew McGregor; +Cc: linux-kernel
On Sat, 4 Jan 2003, Andrew McGregor wrote:
> Or else find that the NV3x has some stonking quick CPU embedded, and apps
> talk GLX to it...
>
> Strange how noone objects to APM BIOS calls or ACPI.
Actually, I object to this.
On my via 686a, the advice on this list for getting the power saving was
to use ACPI (after setting some bits in PCI config space). But lvcool
program showed how to do this without proprietary programs, and I
adapted it to bit of kernel code:
static void via686_idle(void) {
if (!current->need_resched)
inb(Reg_PL2);
}
static int __init init_lvcool(void)
{
nb = pci_find_device(PCI_VENDOR_ID_VIA,
PCI_DEVICE_ID_VIA_8363_0, nb);
smb = pci_find_device(PCI_VENDOR_ID_VIA,
PCI_DEVICE_ID_VIA_82C686_4, smb);
if(nb==NULL)pci_find_device(PCI_VENDOR_ID_VIA,
PCI_DEVICE_ID_VIA_8371_0, nb);
if(!Reg_PL2) {
u32 t;
pci_read_config_dword(smb, 0x48, &t);
Reg_PL2 = (t&0xff80) + 0x14;
printk(KERN_DEBUG "Reg_PL2 = %08x\n", Reg_PL2);
}
old_idle = pm_idle;
pm_idle = via686_idle;
return 0;
}
And I don't need to run any proprietary code during normal system run. I
still need to use BIOS to boot and to poweroff the system, but
that will be solved as well.
--
Matan Ziv-Av. matan@svgalib.org
^ permalink raw reply [flat|nested] 32+ messages in thread* Re: Gauntlet Set NOW!
2003-01-04 19:31 ` Matan Ziv-Av
@ 2003-01-04 19:43 ` Andrew McGregor
0 siblings, 0 replies; 32+ messages in thread
From: Andrew McGregor @ 2003-01-04 19:43 UTC (permalink / raw)
To: Matan Ziv-Av; +Cc: linux-kernel
Which is all nice and good, but trying to do this in order to suspend a
laptop is going to result in vastly more code, and you just can't get the
documentation.
After all, the vendor gave you the code with the hardware in this case, so
it's not as if you can possibly not have a license for it :-)
Andrew
--On Saturday, January 04, 2003 21:31:38 +0200 Matan Ziv-Av
<matan@svgalib.org> wrote:
> On Sat, 4 Jan 2003, Andrew McGregor wrote:
>
>> Or else find that the NV3x has some stonking quick CPU embedded, and apps
>> talk GLX to it...
>>
>> Strange how noone objects to APM BIOS calls or ACPI.
>
> Actually, I object to this.
> On my via 686a, the advice on this list for getting the power saving was
> to use ACPI (after setting some bits in PCI config space). But lvcool
> program showed how to do this without proprietary programs, and I
> adapted it to bit of kernel code:
>
<snip>
>
> And I don't need to run any proprietary code during normal system run. I
> still need to use BIOS to boot and to poweroff the system, but
> that will be solved as well.
>
>
> --
> Matan Ziv-Av. matan@svgalib.org
>
>
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-04 10:01 ` Andrew McGregor
2003-01-04 19:31 ` Matan Ziv-Av
@ 2003-01-06 10:56 ` Helge Hafting
1 sibling, 0 replies; 32+ messages in thread
From: Helge Hafting @ 2003-01-06 10:56 UTC (permalink / raw)
To: Andrew McGregor; +Cc: linux-kernel
Andrew McGregor wrote:
> Strange how noone objects to APM BIOS calls or ACPI.
Many does. But there's no need to shout about it,
you just disable the ACPI and APM config option. I never
saw them do something useful on a non-portable anyway.
Helge Hafting
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-03 23:56 ` Andrew McGregor
2003-01-04 7:12 ` Ryan Anderson
@ 2003-01-04 23:44 ` Richard Stallman
2003-01-05 1:22 ` Rik van Riel
2003-01-05 5:12 ` Andrew McGregor
1 sibling, 2 replies; 32+ messages in thread
From: Richard Stallman @ 2003-01-04 23:44 UTC (permalink / raw)
To: andrew; +Cc: andre, linux-kernel
But sometimes we can't make things free, either because it comes to close
to core IP which we are legally bound to protect, or because it's a derived
work of something we bought and don't ourselves have the right to
redistribute.
At this level of generality, I can only say that if the program is to
be published as non-free software, it will not be available to people
to use in freedom. Its effect will be to tempt people to give up
their freedom. If I had a choice to develop that program or no
program, I would develop no program.
I would rather look for constructive alternatives than just criticize.
In such a situation, I would look for a way to make the program free.
This scenario is too general to get started on that. (I explained in
another message how the term "intellectual property" tends to obscure
important distinctions; this is an example.) In any specific case
there is likely to be some way.
If there is no easy way to make the same program free, there may be a
harder way. People who value freedom strongly sometimes choose the
hard path to freedom rather than the easy path that extends
non-freedom. That is how we extend freedom.
As an ultimate fallback, there is surely some other job you could do
instead.
Linus has made it quite clear in the past that his position on binary
modules is that they are explicitly allowed, but that the maintainers of
such a thing 'get everything they deserve' in terms of maintenance hassle.
Linus has the right to permit this, with his code, and so do other
contributors to Linux. In the GNU Project we usually don't permit
this, and the FSF believes the GPL does not in general permit it, but
occasionally we make an exception when it seems best to do so.
I have no opinion yet about what Andre said, because I cannot form a
clear picture of what he plans to do; I don't know whether it would
violate the GPL, or whether the issue would involve the FSF. We do
not enforce the GPL for Linux in any case; that is the responsibility
of the copyright holders of Linux.
^ permalink raw reply [flat|nested] 32+ messages in thread* Re: Gauntlet Set NOW!
2003-01-04 23:44 ` Richard Stallman
@ 2003-01-05 1:22 ` Rik van Riel
2003-01-05 5:33 ` Milosz Tanski
2003-01-05 5:12 ` Andrew McGregor
1 sibling, 1 reply; 32+ messages in thread
From: Rik van Riel @ 2003-01-05 1:22 UTC (permalink / raw)
To: Richard Stallman; +Cc: andrew, andre, linux-kernel
On Sat, 4 Jan 2003, Richard Stallman wrote:
> I would rather look for constructive alternatives than just criticize.
> In such a situation, I would look for a way to make the program free.
> If there is no easy way to make the same program free, there may be a
> harder way.
There is of course the business model used by the ghostscript
people, used by tytso when he made resize2fs and also used by
Andre Hedrick:
1) write the software, sell it for a profit for some period
of time (eg. 18 months)
2) after that, release the program and its source code
To the copyright holder, this has all the benefits of a strictly
copyrighted work, ie. funding. It also has the additional benefit
of having free software out there that lags close enough to your
commercial program that a competitor has no chance of entering
the market with a non-free product of mediocre quality.
To the free software community, it has the benefits of free
software becoming available at a higher speed than what would
have happened without any funding at all.
Of course, the copyright holder has to choose a license like the
GPL when releasing the software as open source, since otherwise
the competitors would be able to use the older version as a basis
to develop their commercial product from.
To me, this looks like a win/win situation and I hope more
companies will choose this business model.
regards,
Rik
--
Bravely reimplemented by the knights who say "NIH".
http://www.surriel.com/ http://guru.conectiva.com/
Current spamtrap: <a href=mailto:"october@surriel.com">october@surriel.com</a>
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-05 1:22 ` Rik van Riel
@ 2003-01-05 5:33 ` Milosz Tanski
0 siblings, 0 replies; 32+ messages in thread
From: Milosz Tanski @ 2003-01-05 5:33 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1500 bytes --]
On Sat, 4 Jan 2003 23:22:44 -0200 (BRST)
Rik van Riel <riel@conectiva.com.br> wrote:
> On Sat, 4 Jan 2003, Richard Stallman wrote:
>
> > I would rather look for constructive alternatives than just
> > criticize. In such a situation, I would look for a way to make the
> > program free.
>
> > If there is no easy way to make the same program free, there may be
> > a harder way.
>
> There is of course the business model used by the ghostscript
> people, used by tytso when he made resize2fs and also used by
> Andre Hedrick:
>
> 1) write the software, sell it for a profit for some period
> of time (eg. 18 months)
>
> 2) after that, release the program and its source code
>
> To the copyright holder, this has all the benefits of a strictly
Seams to me like a perfectly good idea, infact I want to use that for a
game i'm developing in my free time(wheter or not i finish this, is out
of the scope of the discussion :)), once i'm done i'm going to see how
much time i spent working on this. Then i'm going figure out a time
period and ammount of money that would be *fair* conpensation. then i
plan to release under a free licence (such as the GPL, haven't put a lot
of though into that part quite yet), depending if I make the set ammount
of money first or the set time passes buy (since chance are then i won't
make my set goal :|). If people (not even me) can make money to put on a
table this way, have a decent place to live, and have health insurance
then this model can't be bad.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-04 23:44 ` Richard Stallman
2003-01-05 1:22 ` Rik van Riel
@ 2003-01-05 5:12 ` Andrew McGregor
2003-01-05 5:31 ` Andre Hedrick
1 sibling, 1 reply; 32+ messages in thread
From: Andrew McGregor @ 2003-01-05 5:12 UTC (permalink / raw)
To: rms; +Cc: andre, linux-kernel
By the way, I'm principally a developer of communications standards and
hardware, not so much software.
--On Saturday, January 04, 2003 18:44:49 -0500 Richard Stallman
<rms@gnu.org> wrote:
> But sometimes we can't make things free, either because it comes to
> close to core IP which we are legally bound to protect, or because
> it's a derived work of something we bought and don't ourselves have
> the right to redistribute.
>
> At this level of generality, I can only say that if the program is to
> be published as non-free software, it will not be available to people
> to use in freedom. Its effect will be to tempt people to give up
> their freedom. If I had a choice to develop that program or no
> program, I would develop no program.
Here is where we differ. I do these things because, even though they do
not promote software freedom, they can and, I hope, do promote other kinds
of freedom in other ways. I also always look to the maximally free way to
do the software parts. Sometimes it is not possible to acheive the other
goals we have and keep the software entirely free. I think, however, that
the freedom given by very inexpensive and unconstrained (that is, free as
in speech) telecommunications is somewhat more important than the absolute
freedom of the specific software we use to acheive that. In several cases,
we have chosen proprietary solutions where they make the monetary cost to
the end user dramatically lower, because one of our target problems is the
lack of economic freedom in many parts of the world. For those with an
arbitrary hardware budget, there are or soon will be interoperable free
software alternatives. We make sure of that. We make sure we use open
standards with no closed extensions, so as to make sure this continues.
> I would rather look for constructive alternatives than just criticize.
> In such a situation, I would look for a way to make the program free.
I'm often focused on the case where the total hardware + software cost is
the key factor between user of any communications and user of no
communications. I use free or partly free software wherever I can, because
I am not hostile to that goal, but that is not my overriding concern.
I am also concerned that some of the zealots in the free software, not
necessarily including yourself Richard, do not set precedents in the courts
that, while possibly reinforcing the particular technicality of the GPL,
undermine the freeness of kinds of speech other than software, such as
scientific communication, cultural artefacts and political discussion. In
the long run that would be worse for freedom in general.
> This scenario is too general to get started on that. (I explained in
> another message how the term "intellectual property" tends to obscure
> important distinctions; this is an example.) In any specific case
> there is likely to be some way.
Here I'm using that term in the sense of 'copyrighted (and possibly
patented) compilable information and its documentation', covering both
software and hardware designs. If I were to use it to cover anything else
I'd be more specific, as is common usage where I come from. I do
understand the ambiguity and hidden conflations behind the term; I have
been involved in both trademark and patenting (of hardware; software
patents are evil, no question) work, and I'm cited as an inventor on one
patent, so I have some firsthand experience.
> If there is no easy way to make the same program free, there may be a
> harder way. People who value freedom strongly sometimes choose the
> hard path to freedom rather than the easy path that extends
> non-freedom. That is how we extend freedom.
I'm principally concerned with other sorts of freedom, while attempting to
forward the cause of software freedom to the extent I can, and attempting
never to advance the cause of any sort of non-freedom. It isn't easy at
all, believe me.
> As an ultimate fallback, there is surely some other job you could do
> instead.
I could go back to being a musician or a scientist. There are freedom
issues there, too, believe me. And I'd still be debating free software,
because in those fields it's important too. It would certainly be easier
to tread the path of free software purity in those fields, but I suspect it
would make less long-term impact for me to do so.
> I have no opinion yet about what Andre said, because I cannot form a
> clear picture of what he plans to do; I don't know whether it would
> violate the GPL, or whether the issue would involve the FSF. We do
> not enforce the GPL for Linux in any case; that is the responsibility
> of the copyright holders of Linux.
I'm glad to hear that. I'm also glad that the zealot who started the
thread that has us talking about this does not appear to be one of those
copyright holders; I suspect most of them have more sense.
Andrew
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-05 5:12 ` Andrew McGregor
@ 2003-01-05 5:31 ` Andre Hedrick
2003-01-05 10:47 ` Andrew McGregor
0 siblings, 1 reply; 32+ messages in thread
From: Andre Hedrick @ 2003-01-05 5:31 UTC (permalink / raw)
To: Andrew McGregor; +Cc: rms, linux-kernel
On Sun, 5 Jan 2003, Andrew McGregor wrote:
> By the way, I'm principally a developer of communications standards and
> hardware, not so much software.
I forgot to mention the template model on each side of the iSCSI protocol
state machine we have developed is agnostic?
Initiator --- Transport --- Target --- Spindle
TCP SCSI
Quads ATA
SCI SATA
Myrinet MD
InfiniBand LVM
TELCO USB
CARRIER 1394
SAS
Fibre Channel
FLOPPY, for emergencies.
Create Your Own Create Your Own
Yeah, I am nutter than a fruitcake, but it works!
This is for Larry McVoy, it is the closest thing you will ever see today
which looks like a disk with an RJ-45 port.
Cheers,
Andre Hedrick
LAD Storage Consulting Group
> --On Saturday, January 04, 2003 18:44:49 -0500 Richard Stallman
> <rms@gnu.org> wrote:
>
> > But sometimes we can't make things free, either because it comes to
> > close to core IP which we are legally bound to protect, or because
> > it's a derived work of something we bought and don't ourselves have
> > the right to redistribute.
> >
> > At this level of generality, I can only say that if the program is to
> > be published as non-free software, it will not be available to people
> > to use in freedom. Its effect will be to tempt people to give up
> > their freedom. If I had a choice to develop that program or no
> > program, I would develop no program.
>
> Here is where we differ. I do these things because, even though they do
> not promote software freedom, they can and, I hope, do promote other kinds
> of freedom in other ways. I also always look to the maximally free way to
> do the software parts. Sometimes it is not possible to acheive the other
> goals we have and keep the software entirely free. I think, however, that
> the freedom given by very inexpensive and unconstrained (that is, free as
> in speech) telecommunications is somewhat more important than the absolute
> freedom of the specific software we use to acheive that. In several cases,
> we have chosen proprietary solutions where they make the monetary cost to
> the end user dramatically lower, because one of our target problems is the
> lack of economic freedom in many parts of the world. For those with an
> arbitrary hardware budget, there are or soon will be interoperable free
> software alternatives. We make sure of that. We make sure we use open
> standards with no closed extensions, so as to make sure this continues.
>
> > I would rather look for constructive alternatives than just criticize.
> > In such a situation, I would look for a way to make the program free.
>
> I'm often focused on the case where the total hardware + software cost is
> the key factor between user of any communications and user of no
> communications. I use free or partly free software wherever I can, because
> I am not hostile to that goal, but that is not my overriding concern.
>
> I am also concerned that some of the zealots in the free software, not
> necessarily including yourself Richard, do not set precedents in the courts
> that, while possibly reinforcing the particular technicality of the GPL,
> undermine the freeness of kinds of speech other than software, such as
> scientific communication, cultural artefacts and political discussion. In
> the long run that would be worse for freedom in general.
>
> > This scenario is too general to get started on that. (I explained in
> > another message how the term "intellectual property" tends to obscure
> > important distinctions; this is an example.) In any specific case
> > there is likely to be some way.
>
> Here I'm using that term in the sense of 'copyrighted (and possibly
> patented) compilable information and its documentation', covering both
> software and hardware designs. If I were to use it to cover anything else
> I'd be more specific, as is common usage where I come from. I do
> understand the ambiguity and hidden conflations behind the term; I have
> been involved in both trademark and patenting (of hardware; software
> patents are evil, no question) work, and I'm cited as an inventor on one
> patent, so I have some firsthand experience.
>
> > If there is no easy way to make the same program free, there may be a
> > harder way. People who value freedom strongly sometimes choose the
> > hard path to freedom rather than the easy path that extends
> > non-freedom. That is how we extend freedom.
>
> I'm principally concerned with other sorts of freedom, while attempting to
> forward the cause of software freedom to the extent I can, and attempting
> never to advance the cause of any sort of non-freedom. It isn't easy at
> all, believe me.
>
> > As an ultimate fallback, there is surely some other job you could do
> > instead.
>
> I could go back to being a musician or a scientist. There are freedom
> issues there, too, believe me. And I'd still be debating free software,
> because in those fields it's important too. It would certainly be easier
> to tread the path of free software purity in those fields, but I suspect it
> would make less long-term impact for me to do so.
>
> > I have no opinion yet about what Andre said, because I cannot form a
> > clear picture of what he plans to do; I don't know whether it would
> > violate the GPL, or whether the issue would involve the FSF. We do
> > not enforce the GPL for Linux in any case; that is the responsibility
> > of the copyright holders of Linux.
>
> I'm glad to hear that. I'm also glad that the zealot who started the
> thread that has us talking about this does not appear to be one of those
> copyright holders; I suspect most of them have more sense.
>
> Andrew
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-05 5:31 ` Andre Hedrick
@ 2003-01-05 10:47 ` Andrew McGregor
2003-01-05 15:29 ` Andre Hedrick
0 siblings, 1 reply; 32+ messages in thread
From: Andrew McGregor @ 2003-01-05 10:47 UTC (permalink / raw)
To: Andre Hedrick; +Cc: linux-kernel
Oh, that's nice!
Presumably you could substitute DCCP or whatever for TCP. I like it.
So how about this, the result of a corridor conversation at an IETF:
It is perfectly doable, using HIP and some (admittedly expensive) hardware
crypto gear to run iSCSI encrypted at Gigabit Ethernet rates and faster,
while being able to attach endpoints more or less at random in IP space and
move them around freely while connected. Mobile hotplug IP storage :-)
HIP is the Host Identity Payload, which can be seen as different things
depending on which features you like. The idea starts from distinguishing
the IP address, which basically represents a location in the net, from the
Host Identity, which is a public key that identifies an endpoint.
By some machinations, you end up being IP numbering and version agnostic,
while having an extremely lightweight opportunistic key exchange protocol.
There are several implementations and all the specs linked to at
http://www.hip4inter.net/, not presently including my own, which is purely
userspace (everything I have so far needed is provided by standard kernels,
except ESP and that is now in too), BSD licensed and written in Python and
which will be released soon, for some value of soon.
This is a less mature protocol than iSCSI at this point, but I think there
are some very interesting possibilities by combining the two.
Andrew
--On Saturday, January 04, 2003 21:31:39 -0800 Andre Hedrick
<andre@linux-ide.org> wrote:
> On Sun, 5 Jan 2003, Andrew McGregor wrote:
>
>> By the way, I'm principally a developer of communications standards and
>> hardware, not so much software.
>
> I forgot to mention the template model on each side of the iSCSI protocol
> state machine we have developed is agnostic?
>
> Initiator --- Transport --- Target --- Spindle
>
> TCP SCSI
> Quads ATA
> SCI SATA
> Myrinet MD
> InfiniBand LVM
> TELCO USB
> CARRIER 1394
> SAS
> Fibre Channel
>
> FLOPPY, for emergencies.
>
> Create Your Own Create Your Own
>
> Yeah, I am nutter than a fruitcake, but it works!
>
> This is for Larry McVoy, it is the closest thing you will ever see today
> which looks like a disk with an RJ-45 port.
>
> Cheers,
>
> Andre Hedrick
> LAD Storage Consulting Group
>
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-05 10:47 ` Andrew McGregor
@ 2003-01-05 15:29 ` Andre Hedrick
0 siblings, 0 replies; 32+ messages in thread
From: Andre Hedrick @ 2003-01-05 15:29 UTC (permalink / raw)
To: Andrew McGregor; +Cc: linux-kernel
Already drafted the model for secure supporting such a beast.
Additional the day will come when there is mobile internet radio
everywhere with good data rates. The age of corporate security as it
relates to content on laptops is just over the hill.
No longer will people/corporations need to worry about security of laptops
and that which is stored on them. Using iSCSI with ACLs, one can shutdown
data access in an instant. Now this requires or suggests the need for
Diskless Bootable iSCSI without suffering the extra cost associated with,
what is known as "iBOOT" from IBM. This is another issue, but we (the
community) have LinBIOS, and I have a full working version of DBiSCSI
today.
Well I will follow up on this later, and yes what you are asking about can
be done.
Cheers,
On Sun, 5 Jan 2003, Andrew McGregor wrote:
> Oh, that's nice!
>
> Presumably you could substitute DCCP or whatever for TCP. I like it.
>
> So how about this, the result of a corridor conversation at an IETF:
>
> It is perfectly doable, using HIP and some (admittedly expensive) hardware
> crypto gear to run iSCSI encrypted at Gigabit Ethernet rates and faster,
> while being able to attach endpoints more or less at random in IP space and
> move them around freely while connected. Mobile hotplug IP storage :-)
>
>
> HIP is the Host Identity Payload, which can be seen as different things
> depending on which features you like. The idea starts from distinguishing
> the IP address, which basically represents a location in the net, from the
> Host Identity, which is a public key that identifies an endpoint.
>
> By some machinations, you end up being IP numbering and version agnostic,
> while having an extremely lightweight opportunistic key exchange protocol.
>
> There are several implementations and all the specs linked to at
> http://www.hip4inter.net/, not presently including my own, which is purely
> userspace (everything I have so far needed is provided by standard kernels,
> except ESP and that is now in too), BSD licensed and written in Python and
> which will be released soon, for some value of soon.
>
> This is a less mature protocol than iSCSI at this point, but I think there
> are some very interesting possibilities by combining the two.
>
> Andrew
>
> --On Saturday, January 04, 2003 21:31:39 -0800 Andre Hedrick
> <andre@linux-ide.org> wrote:
>
> > On Sun, 5 Jan 2003, Andrew McGregor wrote:
> >
> >> By the way, I'm principally a developer of communications standards and
> >> hardware, not so much software.
> >
> > I forgot to mention the template model on each side of the iSCSI protocol
> > state machine we have developed is agnostic?
> >
> > Initiator --- Transport --- Target --- Spindle
> >
> > TCP SCSI
> > Quads ATA
> > SCI SATA
> > Myrinet MD
> > InfiniBand LVM
> > TELCO USB
> > CARRIER 1394
> > SAS
> > Fibre Channel
> >
> > FLOPPY, for emergencies.
> >
> > Create Your Own Create Your Own
> >
> > Yeah, I am nutter than a fruitcake, but it works!
> >
> > This is for Larry McVoy, it is the closest thing you will ever see today
> > which looks like a disk with an RJ-45 port.
> >
> > Cheers,
> >
> > Andre Hedrick
> > LAD Storage Consulting Group
> >
> >
>
Andre Hedrick
LAD Storage Consulting Group
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-03 23:01 ` Gauntlet Set NOW! Andre Hedrick
2003-01-03 23:56 ` Andrew McGregor
@ 2003-01-09 7:28 ` Richard Stallman
2003-01-09 7:41 ` Andre Hedrick
` (2 more replies)
1 sibling, 3 replies; 32+ messages in thread
From: Richard Stallman @ 2003-01-09 7:28 UTC (permalink / raw)
To: andre; +Cc: linux-kernel
I'm not sure what your project is designed to do, so I don't have an
opinion about how it stands regarding the GPL. However, I've talked
with our lawyer about one specific issue that you raised: that of
using simple material from header files.
Someone recently made the claim that including a header file always
makes a derivative work.
That's not the FSF's view. Our view is that just using structure
definitions, typedefs, enumeration constants, macros with simple
bodies, etc., is NOT enough to make a derivative work. It would take
a substantial amount of code (coming from inline functions or macros
with substantial bodies) to do that.
^ permalink raw reply [flat|nested] 32+ messages in thread* Re: Gauntlet Set NOW!
2003-01-09 7:28 ` Richard Stallman
@ 2003-01-09 7:41 ` Andre Hedrick
2003-01-09 7:50 ` Jeff Garzik
2003-01-09 8:08 ` Andrew Morton
2 siblings, 0 replies; 32+ messages in thread
From: Andre Hedrick @ 2003-01-09 7:41 UTC (permalink / raw)
To: Richard Stallman; +Cc: linux-kernel
Richard,
My Lawyers instructed me not to talk to anyone about this issue any more.
However, I will forward your note to them.
Cheers,
Andre Hedrick
LAD Storage Consulting Group
On Thu, 9 Jan 2003, Richard Stallman wrote:
> I'm not sure what your project is designed to do, so I don't have an
> opinion about how it stands regarding the GPL. However, I've talked
> with our lawyer about one specific issue that you raised: that of
> using simple material from header files.
>
> Someone recently made the claim that including a header file always
> makes a derivative work.
>
> That's not the FSF's view. Our view is that just using structure
> definitions, typedefs, enumeration constants, macros with simple
> bodies, etc., is NOT enough to make a derivative work. It would take
> a substantial amount of code (coming from inline functions or macros
> with substantial bodies) to do that.
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-09 7:28 ` Richard Stallman
2003-01-09 7:41 ` Andre Hedrick
@ 2003-01-09 7:50 ` Jeff Garzik
2003-01-09 8:08 ` Andrew Morton
2 siblings, 0 replies; 32+ messages in thread
From: Jeff Garzik @ 2003-01-09 7:50 UTC (permalink / raw)
To: Richard Stallman; +Cc: linux-kernel
On Thu, Jan 09, 2003 at 02:28:47AM -0500, Richard Stallman wrote:
> That's not the FSF's view. Our view is that just using structure
> definitions, typedefs, enumeration constants, macros with simple
> bodies, etc., is NOT enough to make a derivative work. It would take
> a substantial amount of code (coming from inline functions or macros
> with substantial bodies) to do that.
Richard,
Thanks much for posting this. I admit I have been skipping this entire
thread pretty much :) but the above is worth highlighting.
Unfortunately, while helpful, this doesn't necessarily solve the problem
in Linux; the things that are inlined are quite often fairly "smart"
pieces of code and not just things as simple as wrapper functions, or
structures and typedefs.
Regardless, thanks again to posting the above.
Regards,
Jeff
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-09 7:28 ` Richard Stallman
2003-01-09 7:41 ` Andre Hedrick
2003-01-09 7:50 ` Jeff Garzik
@ 2003-01-09 8:08 ` Andrew Morton
2003-01-09 8:57 ` Jeremy Fitzhardinge
2003-01-09 23:06 ` Oliver Xymoron
2 siblings, 2 replies; 32+ messages in thread
From: Andrew Morton @ 2003-01-09 8:08 UTC (permalink / raw)
To: rms; +Cc: andre, linux-kernel
Richard Stallman wrote:
>
> ...
> That's not the FSF's view. Our view is that just using structure
> definitions, typedefs, enumeration constants, macros with simple
> bodies, etc., is NOT enough to make a derivative work. It would take
> a substantial amount of code (coming from inline functions or macros
> with substantial bodies) to do that.
The last part doesn't make a lot of sense.
Use of an inline function is just that: usage. It matters not at
all whether that function is invoked via inline integration or via
subroutine call. This is merely an implementation detail within
the code which provides that function.
Such functions are part of the offered API which have global scope,
that's all.
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-09 8:08 ` Andrew Morton
@ 2003-01-09 8:57 ` Jeremy Fitzhardinge
2003-01-09 23:06 ` Oliver Xymoron
1 sibling, 0 replies; 32+ messages in thread
From: Jeremy Fitzhardinge @ 2003-01-09 8:57 UTC (permalink / raw)
To: Andrew Morton; +Cc: rms, andre, linux-kernel
On Thu, 2003-01-09 at 00:08, Andrew Morton wrote:
> Richard Stallman wrote:
> >
> > ...
> > That's not the FSF's view. Our view is that just using structure
> > definitions, typedefs, enumeration constants, macros with simple
> > bodies, etc., is NOT enough to make a derivative work. It would take
> > a substantial amount of code (coming from inline functions or macros
> > with substantial bodies) to do that.
>
> The last part doesn't make a lot of sense.
>
> Use of an inline function is just that: usage. It matters not at
> all whether that function is invoked via inline integration or via
> subroutine call. This is merely an implementation detail within
> the code which provides that function.
>
> Such functions are part of the offered API which have global scope,
> that's all.
The thing that copyright law cares about is whether the thing you're
shipping (in binary form) is a derivative work of something else; the
GPL cares if that "something else" is licensed under the GPL because it
requires the whole to be also (at least) GPL'd. Merely calling a
function from a piece of code doesn't make that code a derivative work
of the called function, but it would if the function were inlined.
If a non-GPL piece of code depends on a piece of GPL'd code, but they
are not shipped in a bound state (ie, dynamically linked), then the
non-GPL code is not obligated to be GPL'd because it isn't a derivative
work. This isn't the stated position of the FSF (at least last time I
asked, because they don't consider static and dynamic binding to be
separate cases), but it's the only one which makes sense in terms of
looking at code in the binary and how it got there.
There's a more complex argument that merely depending on GPL'd code (as
a client of a GPL'd library, for example) makes your program a
derivative work, even if your distributed binary contains no GPL'd
code. This argument is based on the assumption that you're depending on
an API for which all the implementations are GPL'd, so there's no way
you can run the code without binding to GPL'd code. All it takes is one
non-GPL'd implementation to break this argument.
Bear in mind that the GPL only governs the act of distribution, so
creating a derivative work dynamically at runtime is not subject to the
GPL. Doing it statically means that you have to distribute the
derivative work, which is subject to the GPL.
Also bear in mind that copyright law only protects things with a
creative input; you cannot copyright pure facts. As Richard says, the
FSF considers things like function names, types, structure definitions,
constants, etc to be pure facts which are necessary to know to call an
API (and extends that to include small pieces of code, where "small" is
not well defined). The implementation of the API itself *is* creative,
and is therefore protected by copyright law. Hence the distinction
between definitions and larger inlined implementations.
Since the thing that is under consideration is not source code, but the
distribution of binaries generated from the source, it is not merely an
implementation detail as to whether a piece of code is included by
reference (ie, an out-of-line function call) or included explicitly
(inlined code). It makes the difference between a non-derivative work
and a derivative work.
J
[Not a lawyer, but I've spent a lot of time talking to them about this
stuff. Not that it makes this message at all valuable or reliable. ]
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Gauntlet Set NOW!
2003-01-09 8:08 ` Andrew Morton
2003-01-09 8:57 ` Jeremy Fitzhardinge
@ 2003-01-09 23:06 ` Oliver Xymoron
1 sibling, 0 replies; 32+ messages in thread
From: Oliver Xymoron @ 2003-01-09 23:06 UTC (permalink / raw)
To: Andrew Morton; +Cc: rms, linux-kernel
On Thu, Jan 09, 2003 at 12:08:50AM -0800, Andrew Morton wrote:
> Richard Stallman wrote:
> >
> > ...
> > That's not the FSF's view. Our view is that just using structure
> > definitions, typedefs, enumeration constants, macros with simple
> > bodies, etc., is NOT enough to make a derivative work. It would take
> > a substantial amount of code (coming from inline functions or macros
> > with substantial bodies) to do that.
>
> The last part doesn't make a lot of sense.
>
> Use of an inline function is just that: usage. It matters not at
> all whether that function is invoked via inline integration or via
> subroutine call. This is merely an implementation detail within
> the code which provides that function.
>
> Such functions are part of the offered API which have global scope,
> that's all.
I think part of the problem is that 'derived work' here is not
something the FSF or the GPL is really in a position to define. It is
instead the other side of the 'fair use' coin of copyright law. The
question is really how much use of header files is fair use (and
therefore completely independent of copyright) and how much
constitutes a derived work (and therefore subject to the rules of the
GPL)? Only a court can decide.
However, I suspect that 'function' is not a bright line here. There
are certainly plenty of inline functions that are trivial. You can
quote f(x)=x^2 from a paper and not be infringing. Similarly,
most if not all structure definitions are also trivial in the sense
that they're simply lists of names and types - you can copy ingredient
lists, phone directories and the like wholesale and also not be
infringing. You're much more likely to get into trouble with things
like the spinlock or semaphore code which are complex, original, and
fairly unique.
(I first typed that as uniq - enough shell hacking for today)
--
"Love the dolphins," she advised him. "Write by W.A.S.T.E.."
^ permalink raw reply [flat|nested] 32+ messages in thread
end of thread, other threads:[~2003-01-09 22:57 UTC | newest]
Thread overview: 32+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-01-04 10:57 Gauntlet Set NOW! Hell.Surfers
2003-01-04 16:35 ` Mark Rutherford
-- strict thread matches above, loose matches on Subject: below --
2003-01-05 6:28 Hell.Surfers
2003-01-04 10:38 Hell.Surfers
2003-01-05 23:40 ` Florian Schmitt
2003-01-04 10:12 Hell.Surfers
2003-01-04 10:42 ` Andrew McGregor
2003-01-04 9:55 Hell.Surfers
2003-01-04 10:07 ` Andre Hedrick
2003-01-04 10:28 ` Andrew McGregor
2003-01-03 20:31 Why is Nvidia given GPL'd code to use in closed source drivers? Richard Stallman
2003-01-03 23:01 ` Gauntlet Set NOW! Andre Hedrick
2003-01-03 23:56 ` Andrew McGregor
2003-01-04 7:12 ` Ryan Anderson
2003-01-04 9:14 ` Andrew McGregor
2003-01-04 9:45 ` Andre Hedrick
2003-01-04 10:01 ` Andrew McGregor
2003-01-04 19:31 ` Matan Ziv-Av
2003-01-04 19:43 ` Andrew McGregor
2003-01-06 10:56 ` Helge Hafting
2003-01-04 23:44 ` Richard Stallman
2003-01-05 1:22 ` Rik van Riel
2003-01-05 5:33 ` Milosz Tanski
2003-01-05 5:12 ` Andrew McGregor
2003-01-05 5:31 ` Andre Hedrick
2003-01-05 10:47 ` Andrew McGregor
2003-01-05 15:29 ` Andre Hedrick
2003-01-09 7:28 ` Richard Stallman
2003-01-09 7:41 ` Andre Hedrick
2003-01-09 7:50 ` Jeff Garzik
2003-01-09 8:08 ` Andrew Morton
2003-01-09 8:57 ` Jeremy Fitzhardinge
2003-01-09 23:06 ` Oliver Xymoron
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox