From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Allen Kennedy Jr." <allen@kennedystuff.com>
Cc: barebox@lists.infradead.org
Subject: Re: Porting to a new board
Date: Tue, 24 Sep 2013 09:39:28 +0200 [thread overview]
Message-ID: <20130924073928.GC30088@pengutronix.de> (raw)
In-Reply-To: <CAO-21LNqyD5-wMWC+Xy9grkxzb9bVRqw+pE7gnJJ_f0jog=izw@mail.gmail.com>
On Mon, Sep 23, 2013 at 04:47:19PM -0500, Allen Kennedy Jr. wrote:
> > What's the output of some network command, like for example 'dhcp'?
>
> This hangs the chip.
This shouldn't happen. No reaction from the board at all? Does ctrl-c
work? You could add some debug messages to the FEC driver to see where
it hangs.
One situation where a board might hang is when the clock is disabled,
but I don't see how this can happen since it's explicitly enabled in
arch/arm/mach-imx/clk-imx27.c
What's the output of 'md 0x1002b000'? Does it show the FEC registers
or does it hang the board aswell? The output of 'iomem' might also
help.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-09-24 7:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 21:47 Allen Kennedy Jr.
2013-09-24 4:24 ` Antony Pavlov
2013-09-24 7:39 ` Sascha Hauer [this message]
2013-09-24 15:00 ` Allen Kennedy Jr.
2013-09-24 16:33 ` Jean-Christophe PLAGNIOL-VILLARD
2013-09-24 17:06 ` Allen Kennedy Jr.
-- strict thread matches above, loose matches on Subject: below --
2013-09-18 21:44 Allen Kennedy Jr.
2013-09-19 7:35 ` Sascha Hauer
2013-09-20 21:02 ` Allen Kennedy Jr.
2013-09-21 7:50 ` Sascha Hauer
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=20130924073928.GC30088@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=allen@kennedystuff.com \
--cc=barebox@lists.infradead.org \
/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