linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Jacob <mjacob@feral.com>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: kernel@kvack.org, Ofer Fryman <ofer@shunra.co.il>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Intel-e1000 for Linux 2.0.36-pre14
Date: Thu, 1 Mar 2001 08:21:04 -0800 (PST)	[thread overview]
Message-ID: <Pine.BSF.4.21.0103010812200.11811-100000@beppo.feral.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1010301105321.12870A-101000@chaos.analogic.com>



On Thu, 1 Mar 2001, Richard B. Johnson wrote:

> On Thu, 1 Mar 2001 kernel@kvack.org wrote:
> 
> > On Thu, 1 Mar 2001, Ofer Fryman wrote:
> > 
> > > I managed to compiled e1000 for Linux 2.0.36-pre14, I can also load it
> > > successfully. 
> > > With the E1000_IMS_RXSEQ bit set in IMS_ENABLE_MASK I get endless interrupts
> > > and the computer freezes, without this bit set it works but I cannot receive
> > > or send anything.
> > 
> > Intel refuses to provide complete documentation for any of their ethernet
> > cards.  I recommend purchasing alternative products from vendors like 3com
> > and National Semiconduct who are cooperative in providing data needed by
> > the development community.
> > 
> 
> Well Intel has been a continual contributor to Linux and BSD. Somebody
> is not getting to the right person. There are lazy people at all
> companies. 

Sorry, I don't believe that that this is correct in this case. I spoke on the
telephone with the "Manager for Open Source Systems", and the concept of
releasing documents to that a driver could be written whose source would be
available was a concept too far. He kept on asking about NDAs- I kept on
saying, yes, I'll sign an NDA (presumably so knowledge of advanced features,
such as VLAN taggging, e.g., would not be released if they did not want it to
be)- but the basic driver source would have to be OPEN! (this was for *BSD,
but that's the same as linux in this case- we *all* want the damned source
open). No meeting of minds. I have been trying this on and off for two years
so that I can properly support the Wiseman && Livengood chipsets in *BSD. No
luck, ergo, reverse engineering of what little they release with the Linux
driver is the order of the day still. The Linux driver, btw, is pretty clearly
a port of an NT driver- which is quite amusing.

FWIW.....I just think that the overall company policy within Intel, much like
that of NetApp and others, is, "Open Source? Well, maybe, err,umm.. "...  It's
just not that important to them (as a company, they think). That said- if you
can get access to said documentation (which I understand comes in a certain
notebook that indicates releasing outside of Intel is a firing offense)- more
power to you!

-matt





  reply	other threads:[~2001-03-01 16:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-01 15:33 Intel-e1000 for Linux 2.0.36-pre14 Ofer Fryman
2001-03-01 15:30 ` kernel
2001-03-01 16:02   ` Richard B. Johnson
2001-03-01 16:21     ` Matthew Jacob [this message]
2001-03-01 16:42       ` Richard B. Johnson
2001-03-01 15:51 Ofer Fryman
2001-03-01 15:51 ` kernel
2001-03-01 17:06 ` Jes Sorensen
2001-03-01 16:49 Ofer Fryman
2001-03-01 17:21 Ofer Fryman
2001-03-01 19:01 Ofer Fryman
2001-03-05  8:12 Ofer Fryman
2001-03-05 17:21 Ofer Fryman
2001-03-05 17:45 Ofer Fryman
2001-03-05 17:44 ` Matthew Jacob

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.BSF.4.21.0103010812200.11811-100000@beppo.feral.com \
    --to=mjacob@feral.com \
    --cc=kernel@kvack.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ofer@shunra.co.il \
    --cc=root@chaos.analogic.com \
    /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).