From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Darren Stevens <darren@stevens-zone.net>,
mad skateman <madskateman@gmail.com>,
Madalin Bucur <madalin.bucur@oss.nxp.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: FSL P5020/P5040: DPAA Ethernet issue with the latest Git kernel
Date: Tue, 7 Jul 2020 09:52:15 +0200 [thread overview]
Message-ID: <4a08422d-86aa-ebb5-40a6-4e20467f5240@xenosoft.de> (raw)
In-Reply-To: <20200625102223.GA3646@oc3871087118.ibm.com>
On 25 June 2020 at 12:22 pm, Alexander Gordeev wrote:
> On Thu, Jun 25, 2020 at 01:01:52AM +0200, Christian Zigotzky wrote:
> [...]
>> I compiled a test kernel with the option "CONFIG_TEST_BITMAP=y"
>> yesterday. After that Skateman and I booted it and looked for the
>> bitmap tests with "dmesg | grep -i bitmap".
>>
>> Results:
>>
>> FSL P5020:
>>
>> [ 0.297756] test_bitmap: loaded.
>> [ 0.298113] test_bitmap: parselist: 14: input is '0-2047:128/256'
>> OK, Time: 562
>> [ 0.298142] test_bitmap: parselist_user: 14: input is
>> '0-2047:128/256' OK, Time: 761
>> [ 0.301553] test_bitmap: all 1663 tests passed
>>
>> FSL P5040:
>>
>> [ 0.296563] test_bitmap: loaded.
>> [ 0.296894] test_bitmap: parselist: 14: input is '0-2047:128/256'
>> OK, Time: 540
>> [ 0.296920] test_bitmap: parselist_user: 14: input is
>> '0-2047:128/256' OK, Time: 680
>> [ 0.299994] test_bitmap: all 1663 tests passed
> Thanks for the test! So it works as expected.
>
> I would suggest to compare what is going on on the device probing
> with and without the bisected commit.
>
> There seems to be MAC and PHY mode initialization issue that might
> resulted from the bitmap format change.
>
> I put Madalin and Sascha on CC as they have done some works on
> this part recently.
>
> Thanks!
>
Hi All,
The issue still exists [1] so we still need the dpaa patch [2]. Could
you please check the problematic commit [3]?
Thanks,
Christian
[1] https://forum.hyperion-entertainment.com/viewtopic.php?p=50885#p50885
[2] https://forum.hyperion-entertainment.com/viewtopic.php?p=50982#p50982
[3] https://forum.hyperion-entertainment.com/viewtopic.php?p=50980#p50980
next prev parent reply other threads:[~2020-07-07 7:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 6:40 FSL P5020/P5040: DPAA Ethernet issue with the latest Git kernel Christian Zigotzky
2020-06-24 8:23 ` Alexander Gordeev
2020-06-24 23:01 ` Christian Zigotzky
2020-06-25 10:22 ` Alexander Gordeev
2020-07-07 7:52 ` Christian Zigotzky [this message]
[not found] <AM6PR04MB3976584920CFDC269D859DBBEC660@AM6PR04MB3976.eurprd04.prod.outlook.com>
2020-07-07 18:26 ` Christian Zigotzky
2020-07-08 6:03 ` Madalin Bucur (OSS)
2020-07-08 6:25 ` Christian Zigotzky
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=4a08422d-86aa-ebb5-40a6-4e20467f5240@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=agordeev@linux.ibm.com \
--cc=darren@stevens-zone.net \
--cc=info@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@oss.nxp.com \
--cc=madskateman@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rtd2@xtra.co.nz \
--cc=s.hauer@pengutronix.de \
/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).