From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Riley Williams <rhw@MemAlpha.CX>
Cc: Ion Badulescu <ionut@moisil.cs.columbia.edu>,
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: Thu, 14 Jun 2001 17:10:47 -0400 [thread overview]
Message-ID: <3B292857.EE72EBE7@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0106142155360.16844-100000@infradead.org>
Riley Williams wrote:
>
> Hi Ion.
>
> >> 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...
>
> > 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.
>
> That presupposes that the person they give the specs to is the person
> writing the driver. I don't remember shawn offering to write a driver
> or anything approaching that.
>
> As I see it, if Shawn has permission to freely distribute the specs,
> he can send a copy to Alan Cox for forwarding to the relevant driver
> developers. However, if he has to sign an NDA to get them, they're
> useless...
>
> Alan: Am I right in assuming this?
If you can find specs, I have tested cards and help write a driver...
Jeff
--
Jeff Garzik | Andre the Giant has a posse.
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-06-14 21:11 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
2001-06-14 20:59 ` Riley Williams
2001-06-14 21:10 ` Jeff Garzik [this message]
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=3B292857.EE72EBE7@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ionut@moisil.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.