From: Mason <slash.tmp@free.fr>
To: netdev <netdev@vger.kernel.org>
Cc: 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>,
Andrew Lunn <andrew@lunn.ch>,
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: Wed, 9 Nov 2016 18:38:12 +0100 [thread overview]
Message-ID: <58235F04.1060604@free.fr> (raw)
In-Reply-To: <5821F223.5090508@free.fr>
On 08/11/2016 16:41, Mason wrote:
> On 31/10/2016 16:29, Mason wrote:
>
>> I'm using these net drivers:
>>
>> drivers/net/ethernet/aurora/nb8800.c
>> drivers/net/phy/at803x.c
>>
>> With a smp8758 board, they work great.
>> I've been trying to use them on a different board:
>>
>> same eth PHY (Atheros AR8035)
>> same eth MAC (Aurora SSN8800)
>> different SoC (same base address for MAC block)
>>
>> It doesn't work, and I'm not sure where to look first...
>
> After oh-so-many days making increasingly random changes,
> hoping something would magically un-break, we did find a
> *local* commit for an exotic platform (chip emulator) that
> was causing the issue.
However... all is not well yet :-(
A) When the board is connected to a Gigabit switch, it is able to
complete the DHCP dance. But this takes around 5 seconds,
(with several requests timing out).
Whereas the same board running an ugly 3.4 kernel (which Mans called
"quite hideous even by evil vendor standards") completes the DHCP
dance in under a second.
B) When the board is connected to a Fast Ethernet switch, the DHCP
dance times out forever. (Whereas this works on the 3.4 kernel.)
C) When the board is connected to a Gigabit switch, then plugged
into the Fast Ethernet switch, then back into the Gigabit switch,
network connectivity is lost forever.
We've started examining the differences in phy and net frameworks
between 3.4 and 4.9 but that's an atom in a haystack.
To be continued...
Regards.
prev parent reply other threads:[~2016-11-09 17:38 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
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 [this message]
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=58235F04.1060604@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.