sfc: Correct address of gPXE boot configuration in EEPROM
Subsystems (2)
PATCH 1/1 sfc: Correct address of gPXE boot configuration in EEPROM
Due to a hardware bug, the originally assigned range cannot reliably be used for boot configuration and must not be modifiable through ethtool.
Signed-off-by Ben Hutchings <[email protected]>
---
This is for 2.6.28. It only affects the ethtool EEPROM access code that is new in this release cycle.
Ben.
drivers/net/sfc/ethtool.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
drivers/net/sfc/ethtool.c +2 -2
@@ -174,8 +174,8 @@ static struct efx_ethtool_stat efx_ethtool_stats[] = {/* EEPROM range with gPXE configuration */ #define EFX_ETHTOOL_EEPROM_MAGIC 0xEFAB -#define EFX_ETHTOOL_EEPROM_MIN 0x100U -#define EFX_ETHTOOL_EEPROM_MAX 0x400U +#define EFX_ETHTOOL_EEPROM_MIN 0x800U +#define EFX_ETHTOOL_EEPROM_MAX 0x1800U/************************************************************************** *
Signature · 3 lines
Ben Hutchings, Senior Software Engineer, Solarflare Communications Not speaking for my employer; that's the marketing department's job. They asked us to note that Solarflare product names are trademarked.
Jeff Garzik
AppliedQuoted 4 lines · Ben Hutchings
Due to a hardware bug, the originally assigned range cannot reliably be used for boot configuration and must not be modifiable through ethtool.
Quoted 8 lines
Signed-off-by Ben Hutchings <[email protected]>---
This is for 2.6.28. It only affects the ethtool EEPROM access code that is new in this release cycle.Ben.
drivers/net/sfc/ethtool.c | 4 ++--
applied