summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKumar Gala <galak@kernel.crashing.org>2009-05-21 08:36:43 -0500
committerKumar Gala <galak@kernel.crashing.org>2009-06-12 17:16:26 -0500
commit22419d77976bbd0df9fcf45513f1b96bd73e50d1 (patch)
tree52d5652585b3debfed466016d224b8ebc7f030f0
parent52d6ad5ecfb22938441c8e3e62935fbd7b0f0920 (diff)
downloadu-boot-imx-22419d77976bbd0df9fcf45513f1b96bd73e50d1.zip
u-boot-imx-22419d77976bbd0df9fcf45513f1b96bd73e50d1.tar.gz
u-boot-imx-22419d77976bbd0df9fcf45513f1b96bd73e50d1.tar.bz2
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. Signed-off-by: Kumar Gala <galak@kernel.crashing.org> Acked-by: Timur Tabi <timur@freescale.com>
-rw-r--r--cpu/mpc85xx/fdt.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/cpu/mpc85xx/fdt.c b/cpu/mpc85xx/fdt.c
index 26a8f48..a692529 100644
--- a/cpu/mpc85xx/fdt.c
+++ b/cpu/mpc85xx/fdt.c
@@ -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);