RE: Mistral AM37x (with AM3715) devel board networking broken

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: linux-omap-owner@xxxxxxxxxxxxxxx 
> [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Gadiyar, Anand
> Sent: Tuesday, November 09, 2010 10:32 AM
> To: Rick Bronson
> Cc: linux-omap@xxxxxxxxxxxxxxx; Premi, Sanjeev
> Subject: Re: Mistral AM37x (with AM3715) devel board networking broken
> 
> On Tue, Nov 9, 2010 at 10:23 AM, Rick Bronson <rick@xxxxxxx> wrote:
> > Hi Sanjeev,
> >
> >  Thanks much for the help.
> >
> >> 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
> >
> >  Note that mine is ES1.0 (yours is ES2.0):
> >
> > OMAP3630/3730-GP ES1.0, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
> >
> >  Not sure if that's any clue.
> >
> 
> That's interesting - there shouldn't b e an ES2.0 of the 
> 3630/3730. The highest
> revision is an ES1.2.
> 

Now, I notice it too. Checking the u-boot sources now.

[snip]...[snip]

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


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux