linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: kernel@kvack.org
Cc: 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 11:02:23 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.3.95.1010301105321.12870A-101000@chaos.analogic.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1010301102756.2411B-100000@kanga.kvack.org>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1277 bytes --]

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. 

Here is a compressed `grep` of linux-kernel mail headers from Intel
who had something useful to say during the past year. Maybe you
can ask one of them for the information you need? You just need to
find an advocate at a big company.

Cheers,
Dick Johnson

Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).

"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.


[-- Attachment #2: Type: APPLICATION/octet-stream, Size: 958 bytes --]

  reply	other threads:[~2001-03-01 16:03 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 [this message]
2001-03-01 16:21     ` Matthew Jacob
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.LNX.3.95.1010301105321.12870A-101000@chaos.analogic.com \
    --to=root@chaos.analogic.com \
    --cc=kernel@kvack.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ofer@shunra.co.il \
    /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).