"Mark A. Greer" <mgreer@xxxxxxxxxxxxxxx> writes: > On Thu, Apr 19, 2012 at 04:04:42PM +0100, Måns Rullgård wrote: >> Igor Grinberg <grinberg@xxxxxxxxxxxxxx> writes: >> >> > On 04/19/12 05:07, Paul Walmsley wrote: >> >> >> >> Hi, >> >> >> >> just wanted to mention this on the list to see if anyone else was seeing >> >> it. I'm using a Compulab CM-T3517 and attempting to use nfsroot, and the >> >> boot hangs. Here are the last few lines when booting with >> >> initcall_debug: > >> I did a little digging... > >> Secondly, the clock configuration for davinci_emac on am35xx is broken. >> omap3xxx_clk_init() registers two clocks for dev_id "davinci_emac", one >> with con_id "emac_clk", one with "phy_clk". When davinci_emac_probe() >> then does a clk_get(dev, NULL), this fails since there is no matching >> con_id. Likewise for davinci_mdio_probe(). > > This is fixed by 59269b94483eabeacbc9a535944b3dafac92a303 > (ARM: OMAP AM3517/3505: clock data: change EMAC clocks aliases) from > Ilya Yanok <yanok@xxxxxxxxxxx>. Its in the current mainline kernel. Yeah, I noticed after I'd already figured out why it was failing. Oh well, it was a good exercise. >> With a little hacking, I got the platform device registered and the >> clocks matching as (I think) they should. It now detects the correct >> PHY, so that's something. >> >> However, the IP config is still getting stuck. For reasons I don't >> know, the msleep(1) call in ic_open_devs() never returns. >> >> That's as far as I got. > > I tried the current mainline on my am3517 evm and it hangs as well. > I'm not surprised, the am35xx has some serious issues ATM. I submitted > a set of patches to fix a lot of them but they need to be reworked. > I'm working on that now. > > Until then, don't expect much to work well. If it does seem to work well, > you got lucky. If you want to get running quickly, try the ***HACK*** > below. Current mainline boot with it applied, CONFIG_TI_DAVINCI_EMAC=y, > boots on my am3517 evm with both an MMC-mounted & NFS-mounted rootfs. > > Mark > -- > > diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c > index 703bd10..187f5cb 100644 > --- a/arch/arm/mach-omap2/pm34xx.c > +++ b/arch/arm/mach-omap2/pm34xx.c > @@ -705,7 +705,6 @@ static int __init omap3_pm_init(void) > struct clockdomain *neon_clkdm, *per_clkdm, *mpu_clkdm, *core_clkdm; > int ret; > > - if (!cpu_is_omap34xx()) > return -ENODEV; > > if (!omap3_has_io_chain_ctrl()) That does indeed make it boot. -- Måns Rullgård mans@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
