From: dinguyen@opensource.altera.com (Dinh Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: socfpga ethernet problems with ethernet in 3.17 with u-boot-2013.01.01
Date: Tue, 7 Oct 2014 10:51:18 -0500 [thread overview]
Message-ID: <54340BF6.4030602@opensource.altera.com> (raw)
In-Reply-To: <20141007121017.GA20998@amd>
On 10/07/2014 07:10 AM, Pavel Machek wrote:
> Hi!
>
> After some testing:
>
> u-boot-2013.01.01 + linux-3.17 => ethernet does not work
> (unless ethernet is used in u-boot, for example
> using ping)
> u-boot-marex-20140920a + linux-3.17 => working ethernet
>
> One of our guesses is that maybe we don't pull ethernet out of reset
> in the first case?
>
v3.17 has the reset driver framework that the stmmac driver uses to
deassert the reset.
Dinh
WARNING: multiple messages have this Message-ID (diff)
From: Dinh Nguyen <dinguyen@opensource.altera.com>
To: Pavel Machek <pavel@denx.de>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <marex@denx.de>
Subject: Re: socfpga ethernet problems with ethernet in 3.17 with u-boot-2013.01.01
Date: Tue, 7 Oct 2014 10:51:18 -0500 [thread overview]
Message-ID: <54340BF6.4030602@opensource.altera.com> (raw)
In-Reply-To: <20141007121017.GA20998@amd>
On 10/07/2014 07:10 AM, Pavel Machek wrote:
> Hi!
>
> After some testing:
>
> u-boot-2013.01.01 + linux-3.17 => ethernet does not work
> (unless ethernet is used in u-boot, for example
> using ping)
> u-boot-marex-20140920a + linux-3.17 => working ethernet
>
> One of our guesses is that maybe we don't pull ethernet out of reset
> in the first case?
>
v3.17 has the reset driver framework that the stmmac driver uses to
deassert the reset.
Dinh
next prev parent reply other threads:[~2014-10-07 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 12:10 socfpga ethernet problems with ethernet in 3.17 with u-boot-2013.01.01 Pavel Machek
2014-10-07 12:10 ` Pavel Machek
2014-10-07 15:51 ` Dinh Nguyen [this message]
2014-10-07 15:51 ` Dinh Nguyen
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=54340BF6.4030602@opensource.altera.com \
--to=dinguyen@opensource.altera.com \
--cc=linux-arm-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.