linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Lübbe" <jlu@pengutronix.de>
To: Igor Grinberg <grinberg@compulab.co.il>
Cc: Paul Walmsley <paul@pwsan.com>, linux-omap@vger.kernel.org
Subject: Re: AM3517 boot failure
Date: Thu, 19 Apr 2012 20:12:45 +0200	[thread overview]
Message-ID: <1334859165.9998.43.camel@polaris.local> (raw)
In-Reply-To: <4F8FC572.80406@compulab.co.il>

On Thu, 2012-04-19 at 10:57 +0300, Igor Grinberg wrote: 
> On 04/19/12 05:07, Paul Walmsley wrote:
> > Is anyone else seeing this?
> 
> I've tried various configurations and can confirm this hang.
> I still haven't got my hands on bisecting this.
> There is nothing special about CM-T3517,
> IMO this can be seen on any AM35xx based board with EMAC, or am I mistaken?
> Anyway, can anybody try nfsroot on other AM35xx based board with EMAC supported?

I have a board with the AM3505 and NFS root works fine here. I'm using
3.4-rc3, Mark A. Greer's patch series on this list (2012-04-11) and Paul
Walmsley's fixes-for-v3.4-rc3 tag. A possible difference is that I'm
using the fixed PHY driver.

Best regards,
Jan Lübbe
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2012-04-19 19:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19  2:07 AM3517 boot failure Paul Walmsley
2012-04-19  7:57 ` Igor Grinberg
2012-04-19 15:04   ` Måns Rullgård
2012-04-19 16:53     ` Tony Lindgren
2012-04-19 17:52       ` Måns Rullgård
2012-04-19 18:05     ` Mark A. Greer
2012-04-19 19:43       ` Måns Rullgård
2012-04-19 18:12   ` Jan Lübbe [this message]
2012-05-08  5:50   ` Paul Walmsley
2012-05-08 13:50     ` Kevin Hilman
2012-05-08 15:49       ` Paul Walmsley
2012-05-08 16:24         ` Måns Rullgård
2012-05-08 19:08         ` Mark A. Greer

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=1334859165.9998.43.camel@polaris.local \
    --to=jlu@pengutronix.de \
    --cc=grinberg@compulab.co.il \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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).