From: David Miller <davem@davemloft.net>
To: molle.bestefich@gmail.com
Cc: auke-jan.h.kok@intel.com, charlieb@budge.apana.org.au,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: e100: checksum mismatch on 82551ER rev10
Date: Fri, 04 Aug 2006 04:28:34 -0700 (PDT) [thread overview]
Message-ID: <20060804.042834.78730901.davem@davemloft.net> (raw)
In-Reply-To: <20060804.042024.63108922.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Fri, 04 Aug 2006 04:20:24 -0700 (PDT)
> I totally agree, Intel driver maintainers generally act like complete
> idiots in these kinds of situations.
>
> If the EEPROM has a broken checksum, the user should have an option
> that allows him to try and use the device anyways, end of story.
And BTW I want to remind the entire world that the last time Intel
cried wolf to all of us about vendors using broken EEPROMs with their
networking chips it turned out to be a bug in one of the patches Intel
put into the Linux driver. :-)
Intel should really humble themselves and help users instead of hinder
them. Putting the blame on other vendors does not help users, I don't
care how you spin it. It only serves to make Intel look like a bunch
of control freaks, and that pisses off users to no end.
Please put the option into the e100 driver to allow trying to use the
device even if the EEPROM checksum is wrong.
If an Intel developer doesn't do it, I will.
next prev parent reply other threads:[~2006-08-04 11:28 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
2006-08-04 11:04 ` Molle Bestefich
2006-08-04 11:20 ` David Miller
2006-08-04 11:28 ` David Miller [this message]
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=20060804.042834.78730901.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=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).