Skip to contentSkip to conversation

sfc: Correct address of gPXE boot configuration in EEPROM

PATCH Applied Ben Hutchings 2 participants 2 messages Nov 3, 2008 – Nov 6, 2008

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

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.

---
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
index fa98af5..cd0d087 100644
@@ -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.
Applied
#1 lore raw
Quoted 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

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