From: Rick Bronson <rick@efn.org>
To: srinath@mistralsolutions.com,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: RE: Mistral AM37x (with AM3715) devel board networking broken
Date: Sun, 07 Nov 2010 07:44:40 -0800 [thread overview]
Message-ID: <E1PF7Q8-0004IQ-8y@amazonia.comcast.net> (raw)
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.
Please check my setup of u-boot, here is what I did:
wget ftp://ftp.denx.de/pub/u-boot/u-boot-2010.09.tar.bz2
tar jxf u-boot-2010.09.tar.bz2
cd u-boot-2010.09; make omap3_evm_config; make
Is this the correct config (omap3_evm_config) to use for this board?
Maybe you could tell me what exact u-boot and kernel you'd recommend
and the steps to get them for this board.
Thanks,
Rick
next reply other threads:[~2010-11-07 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-07 15:44 Rick Bronson [this message]
2010-11-08 12:06 ` Mistral AM37x (with AM3715) devel board networking broken Premi, Sanjeev
2010-11-08 15:25 ` Premi, Sanjeev
[not found] <B85A65D85D7EB246BE421B3FB0FBB5930234992A00@dbde02.ent.ti.com>
2010-11-11 20:10 ` Rick Bronson
-- strict thread matches above, loose matches on Subject: below --
2010-11-09 4:53 Rick Bronson
2010-11-09 5:02 ` Gadiyar, Anand
2010-11-10 13:04 ` Premi, Sanjeev
2010-11-10 13:03 ` Premi, Sanjeev
2010-11-06 15:20 Rick Bronson
2010-11-06 19:02 ` Premi, Sanjeev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1PF7Q8-0004IQ-8y@amazonia.comcast.net \
--to=rick@efn.org \
--cc=linux-omap@vger.kernel.org \
--cc=srinath@mistralsolutions.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox