> -----Original Message----- > From: linux-omap-owner@xxxxxxxxxxxxxxx > [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Premi, Sanjeev > Sent: Monday, November 08, 2010 5:37 PM > To: Rick Bronson; srinath@xxxxxxxxxxxxxxxxxxxx; > linux-omap@xxxxxxxxxxxxxxx > Subject: RE: Mistral AM37x (with AM3715) devel board networking broken > > > -----Original Message----- > > From: linux-omap-owner@xxxxxxxxxxxxxxx > > [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Rick Bronson > > Sent: Sunday, November 07, 2010 9:15 PM > > To: srinath@xxxxxxxxxxxxxxxxxxxx; linux-omap@xxxxxxxxxxxxxxx > > Subject: RE: Mistral AM37x (with AM3715) devel board > networking broken > > > > sanjeev, > > > > Thanks much for the help. > > > > > [sp] On first looks I would suspect the u-boot. 2009.11 > > seems to be quite old. > > > Can you try using version 2010.09? > > > > I had tried 2010.09 on this board originally but found that it > > wasn't stable, it was almost like the SDRAM wasn't set up correctly. > > I'd get random panic's on bad pointers in Linux. But I tried it > > anyway on this new kernel and it does set up the networking > about 1 in > > 5 boots. Here is a boot where it set up the network > > http://www.efn.org/~rick/pub/boot4.log, it still has the > > warnings though. > > [sp] If you noticed, earlier u-boot version was identifying > your board as: > > U-Boot 2009.11 (Oct 30 2010 - 13:14:45) > > > > OMAP34xx/35xx-GP ES1.0, CPU-OPP2 L3-165MHz > > OMAP3 EVM board + LPDDR/NAND > > > Now, > > U-Boot 2010.09 (Nov 07 2010 - 07:08:44) > > > > OMAP3630/3730-GP ES1.0, CPU-OPP2, L3-165MHz, Max CPU Clock 1 > Ghz > OMAP3 EVM board + LPDDR/NAND > > That's ai improvement. > > However, in your log, I see folloing: > > [ 0.000000] Total of 96 interrupts on 1 active controller > [ 0.000000] Could not get gpios_ick > [ 0.000000] Could not get gpios_fck > > Looks like there are some changes - either in your Kconfig or > elsewhere in the code that "get" gpio clocks is failing. > > The SMSC chip is "virtually" non-existent for the Linux kernel > here onwards. > > My kernel version is "Linux-2.6.36-rc8-09072-g661df74-" > > I have not yet looked at, but there is possible "break" on on > mainline for EVM due to gpio related changes. > You could be experiencing this break... > > ~sanjeev [snip] I tried building the latest on l-o master and was able to boot consistently in 4 times I tried. Didn't notice the gpio clock related error I noticed in your boot log. U-Boot 2010.09 (Nov 08 2010 - 17:11:45) OMAP3630/3730-GP ES2.0, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz OMAP3 EVM board + LPDDR/NAND ... [ 0.000000] Clocking rate (Crystal/Core/MPU): 26.0/200/600 MHz [ 0.000000] Reprogramming SDRC clock to 200000000 Hz [ 0.000000] dpll3_m2_clk rate change failed: -22 [ 0.000000] GPMC revision 5.0 [ 0.000000] IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts [ 0.000000] Total of 96 interrupts on 1 active controller [ 0.000000] OMAP GPIO hardware version 2.5 [ 0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz [ 0.000000] Console: colour dummy device 80x30 [ 0.000000] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar ... [ 2.061950] net eth0: SMSC911x/921x identified at 0xc8880000, IRQ: 336 [ 3.075561] Sending DHCP requests .., OK [ 5.169769] IP-Config: Got DHCP answer from 0.0.0.0, my address is xx.yy.zz.00(edited) ... # uname -a Linux OMAP3EVM 2.6.37-rc1-08879-g9988a6b-dirty #1 Mon Nov 8 19:50:18 IST 2010 armv7l unknown # -- 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
