[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHx5RXDzN93WaYFe2bk6m2TmMC+A9vsmhodRFmZi17cFY5CrWQ@mail.gmail.com>
Date: Tue, 14 May 2024 17:08:24 +0100
From: Stephen Langstaff <stephenlangstaff1@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: Florian Fainelli <f.fainelli@...il.com>, linux-kernel@...r.kernel.org, OlteanV@...il.com
Subject: Re: drivers/net/dsa/dsa_loop_bdinfo.c build problems
On Tue, May 14, 2024 at 1:32 PM Andrew Lunn <andrew@...n.ch> wrote:
> So try to making FIXED_PHY = m, and load it after dsa_loop_bdinfo.ko.
In my configuration FIXED_PHY is selected by several other modules:
│ Selected by [y]:
│ - FSL_DPAA_ETH [=y] && NETDEVICES [=y] && ETHERNET [=y] &&
NET_VENDOR_FREESCALE [=y] && FSL_DPAA [=y] && FSL_FMAN [=y]
│ - FWNODE_MDIO [=y] && NETDEVICES [=y] && MDIO_DEVICE [=y] &&
(ACPI [=y] || OF [=y] || COMPILE_TEST [=n])
│ - OF_MDIO [=y] && NETDEVICES [=y] && MDIO_DEVICE [=y] && OF [=y]
&& PHYLIB [=y]
..so it looks pretty tied up with the MDIO support which I guess I
will need for the real PHY!
If I sorted out building the dsa_loop_bdinfo.c code as a built-in do
you think that would solve the ordering issue?
Powered by blists - more mailing lists