[patch] tulip driver

2001-01-05 Thread Donald Becker
Peter De Schrijver ([EMAIL PROTECTED]) 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

[PATCH] tulip driver

2001-01-05 Thread Peter De Schrijver
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

[PATCH] tulip driver

2001-01-05 Thread Peter De Schrijver
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

[patch] tulip driver

2001-01-05 Thread Donald Becker
Peter De Schrijver ([EMAIL PROTECTED]) 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

[PATCH] tulip driver, 2.4.0-test11 kernel, media type

2000-12-06 Thread Jesper Dangaard Brouer
Error/bug in the "tulip" network driver from the 2.4.0-test11 kernel, when detecting media type. The bug is quite simple. When detecting the media type, it's possible to access data outside/beyond the array "medianame[]". This leads to an kernel panic Oops. I detected the bug, when using

[PATCH] tulip driver, 2.4.0-test11 kernel, media type

2000-12-06 Thread Jesper Dangaard Brouer
Error/bug in the "tulip" network driver from the 2.4.0-test11 kernel, when detecting media type. The bug is quite simple. When detecting the media type, it's possible to access data outside/beyond the array "medianame[]". This leads to an kernel panic Oops. I detected the bug, when using