archive mirror
 help / color / mirror / Atom feed
From: Matthew Jacob <>
To: Riley Williams <rhw@MemAlpha.CX>
Cc: Ion Badulescu <>,
	Shawn Starr <>, <>,
	Alan Cox <>
Subject: Re: Gigabit Intel NIC? - Intel Gigabit Ethernet Pro/1000T
Date: Thu, 14 Jun 2001 14:14:56 -0700 (PDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Sorry for jumping in late in this thread....

With respect to Intel- I've had a number of meetings with these folks on just
this topic- mostly trying to work these issues from the *BSD side of our

Basically- as far as I understand what they've said, is that they're trying
to figure out how they can:

	Formulate a different NDA than they currently have set up for
	companies. This NDA means that they can release documents to engineers
	writing software *and* allow the engineers to release a driver under
	some kind of Open Source- *possibly* with a feature set less than that
	described in the documents.

My personal estimation is that they're serious about trying to do this. As the
engineers I've talked to have put it (roughly), "The Intel IP is *not* in the
)!*$)!*$!)*$ Chip APIs!". This will probably take a Very Long Time for them to
implement though. They may not, ultimately,  be able to figure it out. The
jury's still out.

If any of you want to talk to the Intel folks who are dealing with this (at
least from the marketing side of the Lan group), contact me and I can try and
put you in touch with those people.


On Thu, 14 Jun 2001, 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?
> Best wishes from Riley.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to
> More majordomo info at
> Please read the FAQ at

  parent reply	other threads:[~2001-06-14 21:16 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
2001-06-14 21:14             ` Matthew Jacob [this message]
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] <>
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:

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

  git send-email \ \ \ \ \ \
    --cc=rhw@MemAlpha.CX \ \

* 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).