linux-kernel - Re: [PATCH v2] net: bcmgenet: Fix attaching to PYH failed on RPi 4B

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7f4e15bb-feb5-b4d2-57b9-c2a9b2248d4a@gmail.com>
Date:   Wed, 23 Jun 2021 14:19:54 -0700
From:   Florian Fainelli <f.fainelli@...il.com>
To:     patchwork-bot+netdevbpf@...nel.org,
        Jian-Hong Pan <jhp@...lessos.org>
Cc:     f.fainelli@...il.com, stefan.wahren@...e.com, opendmb@...il.com,
        andrew@...n.ch, bcm-kernel-feedback-list@...adcom.com,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux@...lessos.org, linux-rpi-kernel@...ts.infradead.org
Subject: Re: [PATCH v2] net: bcmgenet: Fix attaching to PYH failed on RPi 4B

On 6/23/21 1:50 PM, patchwork-bot+netdevbpf@...nel.org wrote:
> Hello:
> 
> This patch was applied to netdev/net.git (refs/heads/master):
> 
> On Wed, 23 Jun 2021 11:28:03 +0800 you wrote:
>> The Broadcom UniMAC MDIO bus from mdio-bcm-unimac module comes too late.
>> So, GENET cannot find the ethernet PHY on UniMAC MDIO bus. This leads
>> GENET fail to attach the PHY as following log:
>>
>> bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000
>> ...
>> could not attach to PHY
>> bcmgenet fd580000.ethernet eth0: failed to connect to PHY
>> uart-pl011 fe201000.serial: no DMA platform data
>> libphy: bcmgenet MII bus: probed
>> ...
>> unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus
>>
>> [...]
> 
> Here is the summary with links:
>   - [v2] net: bcmgenet: Fix attaching to PYH failed on RPi 4B
>     https://git.kernel.org/netdev/net/c/b2ac9800cfe0

There was feedback given that could have deserved a v3, if nothing else
to fix the typo in the subject, I suppose that would do though.
-- 
Florian