Skip to contentSkip to conversation

85xx: Always attempt ethernet device tree fixup

PATCH New Kumar Gala 2 participants 2 messages May 21, 2009

lore
Share & tools
lore

Kumar Gala

author
#0 lore raw

PATCH 1/1 85xx: Always attempt ethernet device tree fixup

Its reasonable that we may have ethernet devices but dont have drivers or support enabled for them in u-boot and want the device tree fixed up. Unconditionally calling the ethernet fixup is fine since if we dont have ethernet nodes that match (or aliases) we will not attempt to do anything.

---
 cpu/mpc85xx/fdt.c |    3 ---
 1 files changed, 0 insertions(+), 3 deletions(-)
cpu/mpc85xx/fdt.c +0 -3
index 26a8f48..a692529 100644
@@ -278,12 +278,9 @@ void ft_cpu_setup(void *blob, bd_t *bd)
 	if (!IS_E_PROCESSOR(get_svr()))
 		fdt_fixup_crypto_node(blob, 0);
 
-#if defined(CONFIG_HAS_ETH0) || defined(CONFIG_HAS_ETH1) ||\
-    defined(CONFIG_HAS_ETH2) || defined(CONFIG_HAS_ETH3)
 	fdt_fixup_ethernet(blob);
 
 	fdt_add_enet_stashing(blob);
-#endif
 
 	do_fixup_by_prop_u32(blob, "device_type", "cpu", 4,
 		"timebase-frequency", bd->bi_busfreq / 8, 1);
Signature · 1 line
1.6.0.6
#1 lore raw

PATCH 1/1 85xx: Always attempt ethernet device tree fixup

Quoted 7 lines · Kumar Gala

Its reasonable that we may have ethernet devices but dont have drivers or support enabled for them in u-boot and want the device tree fixed up. Unconditionally calling the ethernet fixup is fine since if we dont have ethernet nodes that match (or aliases) we will not attempt to do anything.

Signature · 2 lines
Timur Tabi
Linux kernel developer at Freescale