From: Ofer Fryman <ofer@shunra.co.il>
To: "'kernel@kvack.org'" <kernel@kvack.org>
Cc: "'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 17:51:30 +0200 [thread overview]
Message-ID: <F1629832DE36D411858F00C04F24847A11DECF@SALVADOR> (raw)
I need a giga fiber PMC cards for linux2.0.36-pre14, the only cards I know
are either Intel based or level-one lxt-1001 card, the level-one lxt-1001
has very bad performance so I cannot use it.
Thanks,
Ofer
-----Original Message-----
From: kernel@kvack.org [mailto:kernel@kvack.org]
Sent: Thursday, March 01, 2001 5:31 PM
To: Ofer Fryman
Cc: 'linux-kernel@vger.kernel.org'
Subject: Re: Intel-e1000 for Linux 2.0.36-pre14
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.
-ben
next reply other threads:[~2001-03-01 15:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-01 15:51 Ofer Fryman [this message]
2001-03-01 15:51 ` kernel
2001-03-01 17:06 ` Jes Sorensen
-- strict thread matches above, loose matches on Subject: below --
2001-03-05 17:45 Ofer Fryman
2001-03-05 17:44 ` Matthew Jacob
2001-03-05 17:21 Ofer Fryman
2001-03-05 8:12 Ofer Fryman
2001-03-01 19:01 Ofer Fryman
2001-03-01 17:21 Ofer Fryman
2001-03-01 16:49 Ofer Fryman
2001-03-01 15:33 Ofer Fryman
2001-03-01 15:30 ` kernel
2001-03-01 16:02 ` Richard B. Johnson
2001-03-01 16:21 ` Matthew Jacob
2001-03-01 16:42 ` Richard B. Johnson
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=F1629832DE36D411858F00C04F24847A11DECF@SALVADOR \
--to=ofer@shunra.co.il \
--cc=kernel@kvack.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®