public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] tulip driver
@ 2001-01-05 18:42 Peter De Schrijver
  0 siblings, 0 replies; 2+ messages in thread
From: Peter De Schrijver @ 2001-01-05 18:42 UTC (permalink / raw)
  To: linux-kernel

[-- Attachment #1: Type: text/plain, Size: 361 bytes --]

Hi,

Attached you will find a patch to the tulip driver in Linux 2.4. This patch
will interpret a bit more of 21142 extended format type 3 info blocks in a 
tulip SROM. This allows correct autonegotation of the builtin 21143 based
ethernet adapter on a digital PWS500a(u). Maybe a future version should do
a more thorough interpretation of the SROM. 

Peter.



[-- Attachment #2: patch-tulip --]
[-- Type: text/plain, Size: 617 bytes --]

diff -rc linux.orig/drivers/net/tulip/eeprom.c linux/drivers/net/tulip/eeprom.c
*** linux.orig/drivers/net/tulip/eeprom.c	Sat Dec 30 20:23:14 2000
--- linux/drivers/net/tulip/eeprom.c	Fri Jan  5 19:02:36 2001
***************
*** 207,214 ****
--- 207,219 ----
  					p += (p[0] & 0x3f) + 1;
  					continue;
  				} else if (p[1] & 1) {
+ 					int gpr_len, reset_len;
+ 
  					mtable->has_mii = 1;
  					leaf->media = 11;
+ 					gpr_len=p[3]*2;
+ 					reset_len=p[4+gpr_len]*2;
+ 					new_advertise |= get_u16(&p[7+gpr_len+reset_len]);
  				} else {
  					mtable->has_nonmii = 1;
  					leaf->media = p[2] & 0x0f;

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [patch] tulip driver
@ 2001-01-06  5:01 Donald Becker
  0 siblings, 0 replies; 2+ messages in thread
From: Donald Becker @ 2001-01-06  5:01 UTC (permalink / raw)
  To: Linux Kernel Mailing List


Peter De Schrijver (p2@mind.be) wrote:

> Attached you will find a patch to the tulip driver in Linux 2.4. This patch 
> will interpret a bit more of 21142 extended format type 3 info blocks in a 
> tulip SROM. This allows correct autonegotation of the builtin 21143 based 
> ethernet adapter on a digital PWS500a(u).

This patch isn't quite correct.

The to-advertise value in the type 3 media info block must be written
to the transceiver after each transceiver reset.  The write is done in
select_media(), not when initially reading EEPROM.

One part of the problem is that to work correctly the driver must keep the
to-advertise values separately for the SYM/serial transceiver and each MII
transceiver.

> Maybe a future version should do 
> a more thorough interpretation of the SROM. 

The tulip driver in 2.4 uses older media selection code.  See the
tulip.c driver at
   http://www.scyld.com/network/tulip.html
for a driver with the many updates needed to support recent chips and
boards.

Donald Becker				becker@scyld.com
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Second Generation Beowulf Clusters
Annapolis MD 21403			410-990-9993

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2001-01-06  5:01 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-01-05 18:42 [PATCH] tulip driver Peter De Schrijver
  -- strict thread matches above, loose matches on Subject: below --
2001-01-06  5:01 [patch] " Donald Becker

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox