netdev - Re: [PATCH v2] lan743x: correctly handle chips with internal PHY

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAGngYiUVnq2BanL_JwDGVwRapO_oU0=-2xFmaPPmHB5XJft4MA@mail.gmail.com>
Date:   Sun, 8 Nov 2020 08:36:38 -0500
From:   Sven Van Asbroeck <thesven73@...il.com>
To:     Roelof Berg <rberg@...g-solutions.de>
Cc:     Andrew Lunn <andrew@...n.ch>,
        Bryan Whitehead <bryan.whitehead@...rochip.com>,
        David S Miller <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>,
        Microchip Linux Driver Support <UNGLinuxDriver@...rochip.com>,
        netdev <netdev@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] lan743x: correctly handle chips with internal PHY

Hi Roelof, great to meet another user of the lan743x !

On Sun, Nov 8, 2020 at 2:43 AM Roelof Berg <rberg@...g-solutions.de> wrote:
>
> My last customer has a fixed link setup, contact me if you need one. Maybe they let me have it and I can test all future patches on fixed link as well.

Is this a commercially available product? I could test this out if it
can be ordered
inexpensively from my location (Canada).

> I tested the current driver version on a Lan7430 EVM in a PC by the way and it seemed to be working. I have the EVM still here if needed.

Yes it will work on a PC, because the device doesn't have a devicetree
entry there.
In my case I am running on ARM, and I'm manually creating a devicetree
entry in the fdt, so that the bootloader can assign a mac address to the chip.

I must be one of the first to use this chip on ARM, because I have
encountered 2 or 3 issues with the current driver, which crash the
kernel on ARM.

I'll try to contribute those changes once this fix is accepted and merged.

Sven