linux-kernel - Re: drivers/net/dsa/dsa_loop

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: <212a9464-d52b-4730-95b9-5a0aebd38c91@gmail.com>
Date: Mon, 13 May 2024 08:50:00 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Stephen Langstaff <stephenlangstaff1@...il.com>
Cc: andrew@...n.ch, linux-kernel@...r.kernel.org,
 "OlteanV@...il.com" <OlteanV@...il.com>
Subject: Re: drivers/net/dsa/dsa_loop_bdinfo.c build problems



On 5/13/2024 8:45 AM, Stephen Langstaff wrote:
> On Mon, May 13, 2024 at 4:40 PM Florian Fainelli <f.fainelli@...il.com> wrote:
>> The Makefile has this:
>>
>> obj-$(CONFIG_FIXED_PHY)         += dsa_loop_bdinfo.o
>>
>> so it follows the value of CONFIG_FIXED_PHY, what is this configuration
>> symbol is to in your kernel configuration?
> 
> CONFIG_FIXED_PHY=y

Then dsa_loop_bdinfo is going to be built into your kernel image, and it 
will register a mdio_board_info structure which will create fixed PHY 
devices and it will assume that the DSA conduit network device name is 
"eth0". If this is not correct for your system, that needs changing.

What are you trying to achieve? Can you be a tad more verbose about what 
you have tried and what is not working?
-- 
Florian