linux-kernel - Re: [PATCH net-next] net: sfp: add quirk for OEM DFP-34X-2C2 GPON ONU SFP

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] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <AS1PR03MB8189A24B92030AA8F011C7B582442@AS1PR03MB8189.eurprd03.prod.outlook.com>
Date: Thu, 8 Feb 2024 15:00:08 +0100
From: Sergio Palumbo <palumbo.ser@...look.it>
To: "Russell King (Oracle)" <linux@...linux.org.uk>
Cc: Andrew Lunn <andrew@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>,
 "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
 Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
 netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next] net: sfp: add quirk for OEM DFP-34X-2C2 GPON ONU
 SFP

Dear Russel,
this is the first time I do such a test and kindly ask you to help me in 
preparing it.
In my openwrt environment I have found phylink.c file in two different 
directories:
/build_dir/toolchain-aarch64_cortex-a53__gcc-112.30_musl/linux-5.15.137/drivers/net/phy
/build_dir/toolchain-aarch64_cortex-a53__gcc-112.30_musllinux-mediatek_filogic/linux-5.15.137/drivers/net/phy

do I have to change both adding a line:
#define DEBUG

before the first #define line:
#define SUPPORTED_interfaces \

and then rebuild the system?

Thanks in advance for your patience in teaching me something totally new 
to me.
Best regards

Sergio Palumbo

Il 08/02/2024 10:07, Russell King (Oracle) ha scritto:
> On Thu, Feb 08, 2024 at 09:30:48AM +0100, Sergio Palumbo wrote:
>> Hello Russell,
>> I did the requested test
> I asked for it with a kernel that has #define DEBUG in phylink.c, but I
> see no debug messages from phylink in your quoted output. There's no
> mention of what's going on behind the scenes, so this gives me
> absolutely no new information.
>