From: Tony Lindgren <tony@atomide.com>
To: "Aguirre, Sergio" <saaguirre@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Zoom3 not booting with omap3_defconfig
Date: Tue, 10 Aug 2010 10:00:43 +0300 [thread overview]
Message-ID: <20100810070042.GG32480@atomide.com> (raw)
In-Reply-To: <A24693684029E5489D1D202277BE894456EA2F3F@dlee02.ent.ti.com>
* Aguirre, Sergio <saaguirre@ti.com> [100809 21:54]:
> Hi,
>
> I'm trying to boot from NFS with my Zoom3 board with current master branch
> (commit ID: 842849896627701e4c07441f2c7519aeec771058)
>
> But, I'm not successful so far. :(
>
> Seems that it can't detect the eth0 device. (See attached log: bad.txt)
>
> Now, If I take omap_zoom3_defconfig from just before commit:
>
> commit 80690ccc41f01df6edfb6684006824d8edff189e
> Author: Vincent Sanders <vince@simtec.co.uk>
> Date: Tue Aug 3 21:19:21 2010 +0100
>
> Remove ARM default configurations which duplicate omap3_defconfig
>
> I'm able to boot fine (see attached log: good.txt)
>
> So, somehow, current omap3_defconfig doesn't seem to be as functional as
> omap_zoom3_defconfig used to be...
Hmm looks like the smc91x does not get detected for some reason.
> Is there something that everybody knows, and I'm missing on how to make a
> usable Zoom3 .config?
Maybe try to diff your good and bad config?
> net eth0: SMSC911x/921x identified at 0xe080c000, IRQ: 318
This line seems to be missing in your bad config. Maybe check
if there's some difference in mux settings between these two
configs?
Also, can you please try using your working config, then enable
support for omap2 and omap4 and see if that breaks it somehow?
Regards,
Tony
prev parent reply other threads:[~2010-08-10 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 19:01 Zoom3 not booting with omap3_defconfig Aguirre, Sergio
[not found] ` <49EAB745-5CB7-429F-8875-9EB349DC3803@mac.com>
2010-08-09 20:09 ` Zoom3 not booting with omap3_defconfig (update: sometimes...) Aguirre, Sergio
2010-08-10 7:00 ` Tony Lindgren [this message]
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=20100810070042.GG32480@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=saaguirre@ti.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;
as well as URLs for NNTP newsgroup(s).