From: Florian Fainelli <f.fainelli@gmail.com>
To: Stephen Langstaff <stephenlangstaff1@gmail.com>
Cc: andrew@lunn.ch, linux-kernel@vger.kernel.org,
"OlteanV@gmail.com" <OlteanV@gmail.com>
Subject: Re: drivers/net/dsa/dsa_loop_bdinfo.c build problems
Date: Mon, 13 May 2024 08:50:00 -0700 [thread overview]
Message-ID: <212a9464-d52b-4730-95b9-5a0aebd38c91@gmail.com> (raw)
In-Reply-To: <CAHx5RXD8qFmbEytrPcd40Pj0VRo7uOvZjucrMj6Xxqw73YyS1Q@mail.gmail.com>
On 5/13/2024 8:45 AM, Stephen Langstaff wrote:
> On Mon, May 13, 2024 at 4:40 PM Florian Fainelli <f.fainelli@gmail.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
next prev parent reply other threads:[~2024-05-13 15:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 15:33 drivers/net/dsa/dsa_loop_bdinfo.c build problems Stephen Langstaff
2024-05-13 15:34 ` Florian Fainelli
2024-05-13 15:36 ` Stephen Langstaff
2024-05-13 15:40 ` Florian Fainelli
2024-05-13 15:45 ` Stephen Langstaff
2024-05-13 15:50 ` Florian Fainelli [this message]
2024-05-13 16:21 ` Stephen Langstaff
2024-05-13 16:54 ` Andrew Lunn
2024-05-13 17:40 ` Stephen Langstaff
2024-05-13 17:54 ` Andrew Lunn
[not found] ` <CAHx5RXCF0=Soz_k88RGvJFGrajaxn=mVnqpb99GAQ=b7XOcWiw@mail.gmail.com>
2024-05-13 19:05 ` Florian Fainelli
2024-05-14 9:28 ` Stephen Langstaff
2024-05-14 12:32 ` Andrew Lunn
2024-05-14 16:08 ` Stephen Langstaff
2024-05-14 16:17 ` Andrew Lunn
2024-05-15 4:05 ` Florian Fainelli
2024-05-15 19:20 ` Florian Fainelli
2024-05-16 2:17 ` Masahiro Yamada
2024-05-16 3:35 ` Florian Fainelli
2024-05-16 6:39 ` Masahiro Yamada
2024-05-15 9:23 ` Stephen Langstaff
2024-05-15 19:26 ` Florian Fainelli
2024-05-16 9:27 ` Stephen Langstaff
-- strict thread matches above, loose matches on Subject: below --
2024-05-13 14:43 Stephen Langstaff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=212a9464-d52b-4730-95b9-5a0aebd38c91@gmail.com \
--to=f.fainelli@gmail.com \
--cc=OlteanV@gmail.com \
--cc=andrew@lunn.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=stephenlangstaff1@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox