From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: sean.anderson@seco.com, davem@davemloft.net,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
mad skateman <madskateman@gmail.com>,
Darren Stevens <darren@stevens-zone.net>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
Matthew Leaman <matthew@a-eon.biz>
Cc: Christian Zigotzky <info@xenosoft.de>
Subject: [FSL P50x0] DPAA Ethernet issue
Date: Sun, 1 Jan 2023 15:18:25 +0100 [thread overview]
Message-ID: <0bfc8f3d-cb62-25f4-2590-ff424adbe48a@xenosoft.de> (raw)
Hi All,
The DPAA Ethernet doesn’t work anymore on our FSL P5020/P5040 boards [1]
since the first updates after the final kernel 6.1 [2].
We bisected yesterday [3] and found the problematic commit [4]. I was
able to revert it. After that the DPAA Ethernet works again. I created a
patch for reverting the commit [4]. After patching and compiling, the
DPAA Ethernet also works again.
It seems, that the new driver doesn’t work with our onboard DPAA network
interfaces.
Could you please check your commit? [4]
Thanks,
Christian
[1] http://wiki.amiga.org/index.php?title=X5000
[2] https://forum.hyperion-entertainment.com/viewtopic.php?p=56326#p56326
[3] https://forum.hyperion-entertainment.com/viewtopic.php?p=56334#p56334
[4] lnet: dpaa: Convert to phylink:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.1&id=5d93cfcf7360eac9903774fe94f626c9ead2049d
next reply other threads:[~2023-01-01 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 14:18 Christian Zigotzky [this message]
2023-01-01 18:11 ` [FSL P50x0] DPAA Ethernet issue Sean Anderson
2023-01-02 3:32 ` Christian Zigotzky
2023-01-03 4:03 ` Christian Zigotzky
2023-01-03 19:59 ` Christian Zigotzky
2023-01-02 7:58 ` Linux kernel regression tracking (#info)
2023-01-03 20:17 ` Sean Anderson
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=0bfc8f3d-cb62-25f4-2590-ff424adbe48a@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=darren@stevens-zone.net \
--cc=davem@davemloft.net \
--cc=info@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madskateman@gmail.com \
--cc=matthew@a-eon.biz \
--cc=rtd2@xtra.co.nz \
--cc=sean.anderson@seco.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).