From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
netdev@vger.kernel.org, linux-sh@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH v5 0/3] ARM: shmobile: lager: enable Ether
Date: Fri, 26 Jul 2013 14:33:49 +0000 [thread overview]
Message-ID: <51F288CD.60608@cogentembedded.com> (raw)
In-Reply-To: <20130726005506.GD28912@verge.net.au>
Hello.
On 26-07-2013 4:55, Simon Horman wrote:
>>> this short series enables the on-board ethernet
>>> of the r8a7790 SoC for on lager board.
>>> It has a run-time dependency on
>>> "sh_eth: add support for r8a7790 SoC"
>>> It has been built on top of renesas-next-20130724v2.
>>> Simon Horman (3):
>>> ARM: shmobile: r8a7790: clocks for Ether support
>>> ARM: shmobile: lager: enable Ether
>>> ARM: shmobile: lager: enable nfsroot in DTS
>>> arch/arm/boot/dts/r8a7790-lager.dts | 2 +-
>>> arch/arm/mach-shmobile/board-lager.c | 30 ++++++++++++++++++++++++++++++
>>> arch/arm/mach-shmobile/clock-r8a7790.c | 4 ++++
>>> 3 files changed, 35 insertions(+), 1 deletion(-)
>> With this series and "[PATCH 0/2 v4 net-next repost] sh_eth: Add support for
>> r8a7790 SoC" applied on top of renesas-devel-20130725, booting the Lager
>> board usually (about 90% of the time) results in receive FIFO overflows and
>> disabling of the sh-eth IRQ:
Looking at the trace, disabling of IRQ is probably caused by something
other than RX FIFO overflow (when it caused disabling IRQ, there were no error
messages printed because RFE interrupt went completely unhandled). Probably
there's more interrupt mask issues lurking in the driver...
> Thanks.
> Unfortunately I am having trouble with using NFS root at all
> in my test environment. I'll work with Magnus to resolve this issue.
> Sergei do you have any idea what might be causing this?
No idea. I still don't have access to Lager and on BOCK-W we have no
issues with NFS. What are your symptoms?
WBR, Sergei
next prev parent reply other threads:[~2013-07-26 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 8:56 [PATCH v5 0/3] ARM: shmobile: lager: enable Ether Simon Horman
2013-07-24 8:56 ` [PATCH v5 1/3] ARM: shmobile: r8a7790: clocks for Ether support Simon Horman
2013-07-24 8:56 ` [PATCH v5 2/3] ARM: shmobile: lager: enable Ether Simon Horman
2013-07-24 10:28 ` Magnus Damm
2013-07-25 1:30 ` Simon Horman
2013-07-24 8:56 ` [PATCH v5 3/3] ARM: shmobile: lager: enable nfsroot in DTS Simon Horman
2013-07-25 10:09 ` [PATCH v5 0/3] ARM: shmobile: lager: enable Ether Laurent Pinchart
2013-07-26 0:55 ` Simon Horman
2013-07-26 14:33 ` Sergei Shtylyov [this message]
2013-07-26 15:33 ` Laurent Pinchart
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=51F288CD.60608@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).