From: Mason <slash.tmp@free.fr>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev <netdev@vger.kernel.org>, Mans Rullgard <mans@mansr.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Timur Tabi <timur@codeaurora.org>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Zefir Kurtisi <zefir.kurtisi@neratec.com>,
Martin Blumenstingl <martin.blumenstingl@gmail.com>,
Uwe Kleine-Konig <u.kleine-koenig@pengutronix.de>,
Daniel Mack <zonque@gmail.com>,
Sebastian Frias <sf84@laposte.net>
Subject: Re: Ethernet not working on a different SoC with same eth HW
Date: Mon, 31 Oct 2016 17:28:24 +0100 [thread overview]
Message-ID: <58177128.8090403@free.fr> (raw)
In-Reply-To: <20161031155334.GF9441@lunn.ch>
On 31/10/2016 16:53, Andrew Lunn wrote:
>> I'll add a log for the request_irq call.
>
> And take a look at /proc/interrupts
You're right, there does seem to be something wrong with the interrupts.
# cat /proc/interrupts
CPU0
20: 26285 GIC-0 29 Edge twd
IPI0: 0 CPU wakeup interrupts
IPI1: 0 Timer broadcast interrupts
IPI2: 0 Rescheduling interrupts
IPI3: 0 Function call interrupts
IPI4: 0 CPU stop interrupts
IPI5: 0 IRQ work interrupts
IPI6: 0 completion interrupts
Err: 0
None of the expected platform interrupts (eth, phy, uart) are registered.
Thanks for pushing in a promising direction.
Regards.
next prev parent reply other threads:[~2016-10-31 16:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 15:29 Ethernet not working on a different SoC with same eth HW Mason
2016-10-31 15:37 ` Andrew Lunn
2016-10-31 15:48 ` Mason
2016-10-31 15:53 ` Andrew Lunn
2016-10-31 16:28 ` Mason [this message]
2016-11-04 13:01 ` Mason
2016-11-04 13:40 ` Måns Rullgård
2016-11-04 13:51 ` Mason
2016-11-04 13:57 ` Andrew Lunn
2016-11-04 14:01 ` Sebastian Frias
2016-11-04 14:04 ` Måns Rullgård
2016-11-04 14:13 ` Mason
2016-11-04 14:22 ` Andrew Lunn
2016-11-04 15:05 ` Måns Rullgård
2016-11-04 15:17 ` Andrew Lunn
2016-11-04 15:22 ` Måns Rullgård
2016-11-04 16:45 ` Florian Fainelli
2016-11-04 16:55 ` Måns Rullgård
2016-11-04 17:06 ` Mason
2016-10-31 15:39 ` Andrew Lunn
2016-11-08 15:41 ` Mason
2016-11-09 17:38 ` Mason
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=58177128.8090403@free.fr \
--to=slash.tmp@free.fr \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=mans@mansr.com \
--cc=martin.blumenstingl@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=sf84@laposte.net \
--cc=timur@codeaurora.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=zefir.kurtisi@neratec.com \
--cc=zonque@gmail.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 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.