linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Sutherland <jas88@cam.ac.uk>
To: Ralf Baechle <ralf@uni-koblenz.de>
Cc: Ion Badulescu <ionut@moisil.cs.columbia.edu>,
	Riley Williams <rhw@MemAlpha.CX>, Shawn Starr <spstarr@sh0n.net>,
	<linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Gigabit Intel NIC? - Intel Gigabit Ethernet Pro/1000T
Date: Wed, 13 Jun 2001 18:07:36 +0100 (BST)	[thread overview]
Message-ID: <Pine.SOL.4.33.0106131804480.10878-100000@orange.csi.cam.ac.uk> (raw)
In-Reply-To: <20010613144017.E31221@bacchus.dhis.org>

On Wed, 13 Jun 2001, Ralf Baechle wrote:

> On Wed, Jun 13, 2001 at 03:25:22AM -0700, Ion Badulescu wrote:
> > Date: 	Wed, 13 Jun 2001 03:25:22 -0700
> > From: Ion Badulescu <ionut@moisil.cs.columbia.edu>
> > To: Riley Williams <rhw@MemAlpha.CX>
> > Cc: Shawn Starr <spstarr@sh0n.net>, <linux-kernel@vger.kernel.org>,
> >         Alan Cox <alan@lxorguk.ukuu.org.uk>
> > Subject: Re: Gigabit Intel NIC? - Intel Gigabit Ethernet Pro/1000T
> >
> > On Tue, 12 Jun 2001 18:20:58 +0100 (BST), Riley Williams <rhw@memalpha.cx> wrote:
> >
> > > Shawn, I'd suggest you tell the said sales guy that IF he can get you
> > > the FULL specs TOGETHER WITH permission to freely distribute them, AND
> >
> > Permission to freely distribute the specs isn't necessary, although it
> > is nice indeed. All that's needed is permission to GPL the driver sources
> > written using knowledge from said specs.
>
> Which would still be a problem.  You then have a GPL'ed driver which still
> cannot be sanely modified in the way the GPL would like to guarantee.

That isn't a problem - the GPL doesn't attempt to guarantee users the
INFORMATION needed to make sane changes, just that they have the facility
to do so. Just as the kernel doesn't come with a copy of the POSIX specs,
the RFCs, etc. - some of the standards the kernel implements aren't
available publicly, but that doesn't stop the kernel being freely
modifiable!


James.


  reply	other threads:[~2001-06-13 17:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-11 17:37 softirq bugs in pre2 Andrea Arcangeli
2001-06-11 19:09 ` Linus Torvalds
2001-06-11 19:41   ` Andrea Arcangeli
2001-06-11 20:55   ` Alan Cox
2001-06-11 22:42   ` Gigabit Intel NIC? - Intel Gigabit Ethernet Pro/1000T Shawn Starr
2001-06-12 16:34     ` Alan Cox
2001-06-12 17:20       ` Riley Williams
2001-06-13 10:25         ` Ion Badulescu
2001-06-13 12:40           ` Ralf Baechle
2001-06-13 17:07             ` James Sutherland [this message]
2001-06-14 20:59           ` Riley Williams
2001-06-14 21:10             ` Jeff Garzik
2001-06-14 21:14             ` Matthew Jacob
2001-06-14 21:29             ` Alan Cox
2001-06-14 21:52               ` Matthew Dharm
2001-06-14 21:58                 ` Alan Cox
2001-06-14 22:03                 ` Matthew Jacob
2001-06-15  2:20             ` Shawn Starr
2001-06-12  2:54   ` softirq bugs in pre2 Andrew Morton
2001-06-11 21:58 ` Pavel Machek
     [not found] <200106112259.RAA20183@asooo.flowerfire.com>
2001-06-12  0:39 ` Gigabit Intel NIC? - Intel Gigabit Ethernet Pro/1000T Shawn Starr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.SOL.4.33.0106131804480.10878-100000@orange.csi.cam.ac.uk \
    --to=jas88@cam.ac.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ionut@moisil.cs.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@uni-koblenz.de \
    --cc=rhw@MemAlpha.CX \
    --cc=spstarr@sh0n.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).