Bug#1114542: linux kernel 6.x : enable all DSA feature for Radxa e54c and others switchs
Hi Jean-Marc,
On Wed, Nov 26, 2025 at 09:18:22PM +0100, Jean-Marc LACROIX wrote:
> Le 26/11/2025 à 20:14, Salvatore Bonaccorso a écrit :
> > Hi,
> >
> > On Sat, Sep 06, 2025 at 08:48:51PM +0200, Salvatore Bonaccorso wrote:
> > > Control: tags -1 + moreinfo
> > >
> > > Hi,
> > >
> > > On Sat, Sep 06, 2025 at 08:22:21PM +0200, Jean-Marc LACROIX wrote:
> > > > Package: linux-image-6.12.30+bpo-arm64
> > > > Version: 6.12.30-1~bpo12+1
> > > >
> > > > I am looking to use Radxa board e54c on armv8 architecture
> > > >
> > > > https://radxa.com/products/network-computer/e54c
> > > >
> > > > One of the major intéressant feature is there is on internal Gigabit switch.
> > > >
> > > > In order to use it, Linux kernel DSA must be set, and good news is that
> > > > CONFIG_NET_S_DSA is set.
> > > >
> > > > The bad news is ...
> > > >
> > > > ansible@hn-rock64-130:~$ grep CONFIG_NET_DSA_ /boot/config-6.12.30+bpo-arm64
> > > > |grep "#"
> > > > # CONFIG_NET_DSA_TAG_NONE is not set
> > > > # CONFIG_NET_DSA_TAG_AR9331 is not set
> > > > # CONFIG_NET_DSA_TAG_BRCM is not set
> > > > # CONFIG_NET_DSA_TAG_BRCM_LEGACY is not set
> > > > # CONFIG_NET_DSA_TAG_BRCM_PREPEND is not set
> > > > # CONFIG_NET_DSA_TAG_HELLCREEK is not set
> > > > # CONFIG_NET_DSA_TAG_GSWIP is not set
> > > > # CONFIG_NET_DSA_TAG_KSZ is not set
> > > > # CONFIG_NET_DSA_TAG_QCA is not set
> > > > # CONFIG_NET_DSA_TAG_RTL4_A is not set
> > > > # CONFIG_NET_DSA_TAG_RTL8_4 is not set
> > > > # CONFIG_NET_DSA_TAG_RZN1_A5PSW is not set
> > > > # CONFIG_NET_DSA_TAG_LAN9303 is not set
> > > > # CONFIG_NET_DSA_TAG_SJA1105 is not set
> > > > # CONFIG_NET_DSA_TAG_VSC73XX_8021Q is not set
> > > > # CONFIG_NET_DSA_TAG_XRS700X is not set
> > > > # CONFIG_NET_DSA_BCM_SF2 is not set
> > > > # CONFIG_NET_DSA_LOOP is not set
> > > > # CONFIG_NET_DSA_HIRSCHMANN_HELLCREEK is not set
> > > > # CONFIG_NET_DSA_LANTIQ_GSWIP is not set
> > > > # CONFIG_NET_DSA_MICROCHIP_KSZ_COMMON is not set
> > > > # CONFIG_NET_DSA_MV88E6XXX_PTP is not set
> > > > # CONFIG_NET_DSA_MSCC_OCELOT_EXT is not set
> > > > # CONFIG_NET_DSA_MSCC_SEVILLE is not set
> > > > # CONFIG_NET_DSA_AR9331 is not set
> > > > # CONFIG_NET_DSA_QCA8K is not set
> > > > # CONFIG_NET_DSA_SJA1105 is not set
> > > > # CONFIG_NET_DSA_XRS700X_I2C is not set
> > > > # CONFIG_NET_DSA_XRS700X_MDIO is not set
> > > > # CONFIG_NET_DSA_REALTEK is not set
> > > > # CONFIG_NET_DSA_SMSC_LAN9303_I2C is not set
> > > > # CONFIG_NET_DSA_SMSC_LAN9303_MDIO is not set
> > > > # CONFIG_NET_DSA_VITESSE_VSC73XX_SPI is not set
> > > > # CONFIG_NET_DSA_VITESSE_VSC73XX_PLATFORM is not set
> > > > ansible@hn-rock64-130:~$
> > >
> > > Which one is the required one for this device and is it confirmed to
> > > work?
> >
> > Friendly ping?
> >
> > Regards,
> > Salvatore
>
> Hi,
>
> I think the best option is to configure (when available and integrated as a
> module) the appropriate module so the user can test and use it later.
>
> I'm also keeping an eye on the NxP T1040RDDP and the banapiR2… There are
> also switches…
This is not how things work :). Basically: We cannot enable just
blindly all modules, this impacts build space and time, and image deb
images sizes (I'm not talking about kernel image size per so, though
some options might impact as well).
So this is why we ask for specifically tested and needed ones. We do
not necessarily want to enable moduels which "nobody" uses.
So tell us which one is impacting you with a confirmed set of options
to make it work. Then we really can have a look.
Regards,
Salvatore
Reply to: