All of lore.kernel.org
 help / color / mirror / Atom feed
From: Augustin Vidovic <vido@ldh.org>
To: Ion Badulescu <ionut@cs.columbia.edu>
Cc: Alan Cox <alan@redhat.com>, Andrey Savochkin <saw@saw.sw.com.sg>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] eepro100.c, kernel 2.4.1
Date: Thu, 8 Feb 2001 21:08:01 +0900	[thread overview]
Message-ID: <20010208210801.A19394@ldh.org> (raw)
In-Reply-To: <20010208204415.A19308@ldh.org> <Pine.LNX.4.30.0102080346150.31024-100000@age.cs.columbia.edu>
In-Reply-To: <Pine.LNX.4.30.0102080346150.31024-100000@age.cs.columbia.edu>; from ionut@cs.columbia.edu on Thu, Feb 08, 2001 at 03:53:10AM -0800

On Thu, Feb 08, 2001 at 03:53:10AM -0800, Ion Badulescu wrote:
> Still, there should be something before these suppressed messages started.

No, sorry, but absolutely nothing since the boot.

> 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 
> does.

Ah ok.

> "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!"

You're absolutely right. I still don't know if activating the workaround
helped, it just seemed to help.

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

I read it, but I don't have the Intel docs, so I miss the information you
have.

Thank you for spending time for this problem.

-- 
Augustin Vidovic                   http://www.vidovic.org/augustin/
"Nous sommes tous quelque chose de naissance, musicien ou assassin,
 mais il faut apprendre le maniement de la harpe ou du couteau."
-
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/

  reply	other threads:[~2001-02-08 12:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-08  5:53 [PATCH] eepro100.c, kernel 2.4.1 Augustin Vidovic
2001-02-08  7:23 ` Ion Badulescu
2001-02-08  7:37   ` Augustin Vidovic
2001-02-08  7:42   ` Alan Cox
2001-02-08  7:55     ` Andrey Savochkin
2001-02-08  7:59     ` [PATCH] " Ion Badulescu
2001-02-08 10:41       ` Augustin Vidovic
2001-02-08 11:00         ` Ion Badulescu
2001-02-08 11:15           ` Augustin Vidovic
2001-02-08 11:26             ` Ion Badulescu
2001-02-08 11:44               ` Augustin Vidovic
2001-02-08 11:53                 ` Ion Badulescu
2001-02-08 12:08                   ` Augustin Vidovic [this message]
2001-02-12  5:32               ` Andrey Savochkin
2001-02-12  9:00                 ` Ion Badulescu
2001-02-20  6:30                   ` Augustin Vidovic
2001-02-20  7:21                     ` Andrey Savochkin
2001-02-20  8:18                       ` Augustin Vidovic
2001-02-20 23:38                         ` Andrey Savochkin
  -- strict thread matches above, loose matches on Subject: below --
2001-02-09 14:38 [PATCH] " Peter Lund

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=20010208210801.A19394@ldh.org \
    --to=vido@ldh.org \
    --cc=alan@redhat.com \
    --cc=ionut@cs.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saw@saw.sw.com.sg \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.