From: Auke Kok <auke-jan.h.kok@intel.com>
To: Charlie Brady <charlieb@budge.apana.org.au>
Cc: Auke Kok <auke-jan.h.kok@intel.com>,
NetDev <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
molle.bestefich@gmail.com
Subject: Re: [bug] e100: checksum mismatch on 82551ER rev10
Date: Wed, 02 Aug 2006 11:30:46 -0700 [thread overview]
Message-ID: <44D0EF56.9020905@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0608021338490.809@e-smith.charlieb.ott.istop.com>
Charlie Brady wrote:
>>> Let's assume that these things are all true, and the NIC currently
>>> does not work perfectly, just imperfectly, but acceptably. With the
>>> recent driver change, it now does not work at all. That's surely a
>>> bug in the driver.
>>
>> There is no logic in that sentence at all. You're saying that the
>> driver is broken because it doesn't fix an error in the EEPROM?
>
> I am not asking the driver to fix errors in the EEPROM. I'm asking it to
> send and receive packets, as it has done in the past.
maybe you are confusing e100 with eepro100. e100 has done this since it made
it into 2.6.4 or so.
Auke
next prev parent reply other threads:[~2006-08-02 18:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.61.0607311653360.24450@e-smith.charlieb.ott.istop.com>
2006-08-02 16:50 ` [bug] e100: checksum mismatch on 82551ER rev10 Auke Kok
2006-08-02 17:45 ` Charlie Brady
2006-08-02 18:30 ` Auke Kok [this message]
2006-08-04 11:04 ` Molle Bestefich
2006-08-04 11:20 ` David Miller
2006-08-04 11:28 ` David Miller
2006-08-05 13:28 ` Molle Bestefich
2006-08-05 17:21 ` Jason Lunz
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=44D0EF56.9020905@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=charlieb@budge.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=molle.bestefich@gmail.com \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).