9 Commits

Author SHA1 Message Date
tabris
5eb8bd0584 kernel config BPI-R4 / Modulize NFSD, CIFS, SMB_SERVER 2025-08-25 01:35:56 +08:00
tabris
02ac21609f kernel config BPI-R4 / modulize XFS, BTRFS, F2FS, UDF, ISO9660, NTFS3, NTFS, and FUSE 2025-08-25 01:35:56 +08:00
tabris
f8e0908f7f kernel config BPI-R4 / modulize REALTEK_PHY, ICPLUS_PHY, MAXLINEAR_GPHY 2025-08-25 01:35:56 +08:00
tabris
2b623ad5eb kernel config BPI-R4 / add WIREGUARD, IFB, NETCONSOLE and TUN as modules 2025-08-25 01:35:56 +08:00
tabris
76f99581f9 kernel config BPI-R4 / modulize SCSI, SATA/PATA, LOOP, NBD, and ramdisk 2025-08-25 01:35:56 +08:00
tabris
25f00b3aa9 kernel config BPI-R4 / modulize BT & RFKILL 2025-08-25 01:35:56 +08:00
tabris
63ef82d227 move CONFIG_PCS_MTK_USXGMII near CONFIG_NET_MEDIATEK_SOC; I2C_SLAVE probably irrelevant 2025-08-21 17:10:11 +08:00
tabris
eb512c1b40 So I'm not completely convinced about CONFIG_ARM64_ERRATUM_858921, but
when doing my initial changes [enabled a bunch of PHYs, made NFS/SMB
etc modules... random stuff], I somehow enabled some errata fixes, and
this one showed up in dmesg.

The real star of the show I'm pretty sure is CONFIG_PCS_MTK_USXGMII.
Note, it cannot be a module, but on this platform we probably wouldn't
want it to be anyway. When I say "it can't", I'm saying it breaks the
build during the linker phase for vmlinux. Probably worth fixing, but
I'm unclear where to start, other than it's probably a Kconfig
dependency problem.

CONFIG_I2C_SLAVE_EEPROM came along for the ride b/c it possibly made
sense with SFPs. But I haven't tried a test build without it yet.

For the record: this works with both my AQS-107-B0C2-CX [an 802.3bz
SFP+] and my FS.com SFP-10GSR-85 "generic" SFP+.
2025-08-21 17:10:11 +08:00
Hsun Lai
2576cd1d8e add community support for MediaTek Filogic device (BananaPi R4 Router) 2025-07-26 08:49:45 +02:00