: Thursday, March 01, 2001 5:31 PM
To: Ofer Fryman
Cc: '[EMAIL PROTECTED]'
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
Thanks Richard,
I guess I have know choice but to try your suggestion.
Ofer
-Original Message-
From: Richard B. Johnson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 01, 2001 6:02 PM
To: [EMAIL PROTECTED]
Cc: Ofer Fryman; '[EMAIL PROTECTED]'
Subject: Re: Intel-e1000 for Linux 2.0.36
I am upgrading to 2.2.x, but mean while I need e1000 driver to run on 2.0.x,
I'm sure that others might need it too.
-Original Message-
From: Jes Sorensen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 01, 2001 7:07 PM
To: Ofer Fryman
Cc: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED
Some more info:
I compiled it with support for IANS and without, but I get the same outcome,
only setting E1000_IMS_RXSEQ will cause endless interrupts that cannot be
stopped not with int_disable and not with cli(), so I guess there must be a
bug somewhere, so I activated it on 2.2.x and
I finally managed to get the interrupt handler running successfully. The
problem was, if you run the driver in debug mode, the interrupt handler goes
crazy, this also happened to me on 2.2.x.
Now the driver appears to be running successfully, but I still cannot pass
traffic through, any clue of
Finally e1000 works on linux2.0.x kernel. If only I had the specs a couple
of days ago...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
any of my calls.
Ofer
-Original Message-
From: Matthew Jacob [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 05, 2001 7:22 PM
To: Ofer Fryman
Subject: RE: Intel-e1000 for Linux 2.0.36-pre14
I saw no 'specs' on the website.
-
To unsubscribe from this list: send the line "unsubs
Did you try looking at Becker eepro100 driver it seems to be simple, no
unnecessary spin_lock_irqsave?.
-Original Message-
From: Hen, Shmulik [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 07, 2001 11:21 AM
To: '[EMAIL PROTECTED]'; Manoj Sontakke
Cc: [EMAIL PROTECTED]
Subject: RE:
: Hen, Shmulik [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 07, 2001 12:47 PM
To: 'Ofer Fryman'; Hen, Shmulik
Cc: [EMAIL PROTECTED]
Subject: RE: spinlock help
e100 implements all sorts of hooks for our intermediate driver (kind of a
co-development effort), so eepro100 is out of the question
I believe that Linux 2.2.x and 2.4.x do support it well, however I tried
using it with Linux 2.0.x and it caused me many problems with PCI drivers. I
also tried server-works chipset, which also works with 64-bit PCI bus, it
worked well under Linux 2.0.x no problems what so ever.
Any way since the
You need to use diagnostic or setup utility of that specific device, the
utility usually comes with the specific driver using the driver to receive
info about mii registers (the registers in charge of full/half 10/100 etc').
you can find many drivers and diagnostic utilities at
Has any one tested the performance of the Tulip or AMD cards (or any other
network card) on any Linux version, with any CPU and any chip-set?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
At what frame size?.
Thanks
Ofer
-Original Message-
From: Bart Trojanowski [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 4:30 PM
To: Ofer Fryman
Cc: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
Subject: Re: network cards (drivers) performance.
On Tue, 10 Apr 2001, Ofer Fryman
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.
Does any one have a clue?.
Thanks
Ofer
: Thursday, March 01, 2001 5:31 PM
To: Ofer Fryman
Cc: '[EMAIL PROTECTED]'
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_RXSE
Thanks Richard,
I guess I have know choice but to try your suggestion.
Ofer
-Original Message-
From: Richard B. Johnson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 01, 2001 6:02 PM
To: [EMAIL PROTECTED]
Cc: Ofer Fryman; '[EMAIL PROTECTED]'
Subject: Re: Intel-e1000 for Linux 2.0.36
I am upgrading to 2.2.x, but mean while I need e1000 driver to run on 2.0.x,
I'm sure that others might need it too.
-Original Message-
From: Jes Sorensen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 01, 2001 7:07 PM
To: Ofer Fryman
Cc: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED
Some more info:
I compiled it with support for IANS and without, but I get the same outcome,
only setting E1000_IMS_RXSEQ will cause endless interrupts that cannot be
stopped not with int_disable and not with cli(), so I guess there must be a
bug somewhere, so I activated it on 2.2.x and
I finally managed to get the interrupt handler running successfully. The
problem was, if you run the driver in debug mode, the interrupt handler goes
crazy, this also happened to me on 2.2.x.
Now the driver appears to be running successfully, but I still cannot pass
traffic through, any clue of
Finally e1000 works on linux2.0.x kernel. If only I had the specs a couple
of days ago...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
any of my calls.
Ofer
-Original Message-
From: Matthew Jacob [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 05, 2001 7:22 PM
To: Ofer Fryman
Subject: RE: Intel-e1000 for Linux 2.0.36-pre14
I saw no 'specs' on the website.
-
To unsubscribe from this list: send the line "unsubs
Did you try looking at Becker eepro100 driver it seems to be simple, no
unnecessary spin_lock_irqsave?.
-Original Message-
From: Hen, Shmulik [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 07, 2001 11:21 AM
To: '[EMAIL PROTECTED]'; Manoj Sontakke
Cc: [EMAIL PROTECTED]
Subject: RE:
rom: Hen, Shmulik [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 07, 2001 12:47 PM
To: 'Ofer Fryman'; Hen, Shmulik
Cc: [EMAIL PROTECTED]
Subject: RE: spinlock help
e100 implements all sorts of hooks for our intermediate driver (kind of a
co-development effort), so eepro100 is out of the quest
I believe that Linux 2.2.x and 2.4.x do support it well, however I tried
using it with Linux 2.0.x and it caused me many problems with PCI drivers. I
also tried server-works chipset, which also works with 64-bit PCI bus, it
worked well under Linux 2.0.x no problems what so ever.
Any way since the
You need to use diagnostic or setup utility of that specific device, the
utility usually comes with the specific driver using the driver to receive
info about mii registers (the registers in charge of full/half 10/100 etc').
you can find many drivers and diagnostic utilities at
Has any one tested the performance of the Tulip or AMD cards (or any other
network card) on any Linux version, with any CPU and any chip-set?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
At what frame size?.
Thanks
Ofer
-Original Message-
From: Bart Trojanowski [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 4:30 PM
To: Ofer Fryman
Cc: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
Subject: Re: network cards (drivers) performance.
On Tue, 10 Apr 2001, Ofer Fryman
27 matches
Mail list logo
