[lkml]   [2001]   [Feb]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] eepro100.c, kernel 2.4.1
On Thu, 8 Feb 2001, Augustin Vidovic wrote:

> This suppression of thousands of lines was described as a DOS-protection
> in the docs I read.

Still, there should be something before these suppressed messages started.

> With my patch, the test becomes (eeprom[3] & 0x03), which is not null
> for every possible non-null value of the two lower bits :
> bit1 bit0 [bit1,bit0]&[1,1]
> 0 0 00
> 0 1 01
> 1 0 10
> 1 1 11
> Whereas the other test is more restrictive, because it excludes the "11"
> from the results.
> The old cards still get the workaround enabled this this wider test.

No, they don't.

It goes like this:

bit0 = 1 means the workaround may be omitted when operating at 10 Mbit
bit1 = 1 means the workaround may be omitted when operating at 100 Mbit

So the workaround needs to be activated when at least one bit is zero, and
may be omitted when both bits are 1. That's exactly what the original code

> > So your patch did not do you any good. Case closed, as far as the work-around
> > is concerned.
> To the contrary, it seems to do a lot of good, because the NET subsystem
> does not send any more panic messages to the kernel, and the cluster has
> not meltdown again so far.

"Yesterday, a brick fell upon my head while I was walking on the street.
Today, I put my hat on before leaving home, and no brick fell on my head
anymore. So the hat must have helped!"

Please read the code if you don't believe me.


It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:17    [W:0.086 / U:3.716 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site