Re: [PATCH] Add eeprom_bad_csum_allow module option to e1000.

On Tue, 2007-10-23 at 09:18 -0700, Kok, Auke wrote:
> Adam Jackson wrote:
> > When the EEPROM gets corrupted, you can fix it with ethtool, but only if
> > the module loads and creates a network device.  But, without this option,
> > if the EEPROM is corrupted, the driver will not create a network device.
> > 
> > Signed-off-by: Adam Jackson <[email protected]>
> 
> NAK
> 
> wrong list, not sent to me, and while for e100 I was OK with this patch, for e1000
> it really does not make sense to 'just allow' a bad checksum - if your eeprom is
> randomly messed up then you cannot just fix it like this anyway.

That's strange, I managed to recover an otherwise horked e1000 with it.
What should I have done instead?

- ajax

-
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/

---

• Follow-Ups:
  • Re: [PATCH] Add eeprom_bad_csum_allow module option to e1000.
    • From: "Kok, Auke" <[email protected]>

• References:
  • [PATCH] Add eeprom_bad_csum_allow module option to e1000.
    • From: Adam Jackson <[email protected]>
  • Re: [PATCH] Add eeprom_bad_csum_allow module option to e1000.
    • From: "Kok, Auke" <[email protected]>

• Prev by Date: Re: [PATCH 2/2] CFS CGroup: Report usage
• Next by Date: Re: [patch 1/2] oProfile: oops when profile_pc() return ~0LU
• Previous by thread: Re: [PATCH] Add eeprom_bad_csum_allow module option to e1000.
• Next by thread: Re: [PATCH] Add eeprom_bad_csum_allow module option to e1000.
• Index(es):
  • Date
  • Thread

[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]