Auke Kok wrote:
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?
It's broken because it bails completely instead of just emitting a
warning message.
You wouldn't believe the number of hours people spend out there trying
to get a Linux box up when there's no network access. Bailing out and
completely disabling the hardware on checksum errors is shooting those
people in the foot, because they'll need to try and debug the driver,
or the hardware, or do something completely else, perhaps on an
embedded device, and you're basically telling them "We at Intel do not
want to allow you to even attempt to make this your hardware work.".
By refusing to add an option to NOT bail, you're adding "And we're
happy to handicap any attempts you might make at it.".
We're trying extremely hard to fix real errors here
You're not fixing anything, you're creating a problem for the user, sorry.
(especially when we find that hardware resellers send out
hardware with EEPROM problems) and you are asking for
a workaround that will (likely) introduce random errors
and failure into your kernel.
You've established yourself that the most likely cause of the error is
that the vendor forgot to run a checksumming tool. That's hardly
random errors and failure. You're trying to pull Linux end users into
a war between Intel and it's vendors, so you can make end users scream
at the vendors when they forget to run the checksum tool. Well,
perhaps you should drop that and instead make it so that the *tools*
bail when the checksum is wrong, not the end user's driver.
If you want to recalculate the checksum yourself and
put it in the EEPROM then I am also fine with that.
Could you please provide a method and/or tool to do that?
But we can't support an option that allows all users to willingly enable
a piece of non-properly-working hardware.
The tactful thing to do would be to put out a big fat error message
during boot, but not bailing.
If you're worried that the end user might not see the message, then
bail, but provide an option to load anyway.
This is the only constructive and meaningful way forward. There's no
point in holding the end user hostage.
The bottom line is that your problem is that a specific hardware vendor
is/was selling badly configured hardware, and you buy it from them, even
after it's End Of Lifed for that vendor. Even though that vendor did buy the units
properly configured and had all the tools needed to configure them properly.
There's no way for me to make Nokia do anything about this problem.
Please don't try to drag me into a Intel vs vendors war just for the
purpose of making me a number in their statistics.
(Maybe you could improve your tools so they'll want to fix the checksum.)
I can maybe fix your problem by seeing if we can get you an eeprom update
Any chance you could get one of those for me?
(Yeah, I do realize that I'm critizicing and then asking for help. Cocky :-D.)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
