Someone working on kernel 5.9?

Thu Oct 29 18:35:20 EDT 2020

Felix Fietkau <nbd at nbd.name> wrote:
> On 2020-10-29 13:11, Koen Vandeputte wrote:
> > 
> > On 29.10.20 11:37, Andrey Jr. Melnikov wrote:
> >> Koen Vandeputte <koen.vandeputte at ncentric.com> wrote:
> >>
> >>> On 03.10.20 17:11, Vincent Wiemann wrote:
> >>>> Hi folks,
> >>>>
> >>>> is anybody working on 5.9, already?
> >>>> I'd like to do some testing with io_uring on ath79 devices,
> >>>> but the features needed require a version > 5.7.
> >>>> Please let me know!
> >>> Not yet currently as I'm pretty occupied with AI stuff, but I might give
> >>> it a try within 1 .. 2 weeks.
> >> before you start - in 5.8 kernel build process slightly changed, so openwrt
> >> "build module first, kernel last" not working, vmlinux must be build before
> >> modules now.
> >> mtd subsystem partition code massive changed - mtdsplit drivers need rewrite.
> > 
> > Thanks,
> > 
> > I'll take a look at it.
> > I did encounter the mtdsplit stuff you mention.
> > 
> > Just swapped to 5.10-rc1 as it will be the next LTS.
> I have 5.9 working on the mediatek target in my staging tree:
> https://git.openwrt.org/?p=openwrt/staging/nbd.git;a=summary

patch target/linux/generic/pending-5.9/306-mips_mem_functions_performance.patch
cause this:

--- cut ---
In file included from ./include/linux/string.h:20,
                 from ./include/linux/uuid.h:12,
                 from ./include/linux/mod_devicetable.h:13,
                 from scripts/mod/devicetable-offsets.c:3:
./arch/mips/include/asm/string.h:24:2: error: expected identifier or '(' before '{' token
   24 | ({        \
      |  ^
./include/linux/string.h:384:24: note: in expansion of macro 'memset'
  384 | __FORTIFY_INLINE void *memset(void *p, int c, __kernel_size_t size)
      |                        ^~~~~~
./arch/mips/include/asm/string.h:35:2: error: expected identifier or '(' before '{' token
   35 | ({        \
      |  ^
./include/linux/string.h:394:24: note: in expansion of macro 'memcpy'
  394 | __FORTIFY_INLINE void *memcpy(void *p, const void *q, __kernel_size_t size)
      |                        ^~~~~~
./arch/mips/include/asm/string.h:46:2: error: expected identifier or '(' before '{' token
   46 | ({        \
      |  ^
./include/linux/string.h:409:24: note: in expansion of macro 'memmove'
  409 | __FORTIFY_INLINE void *memmove(void *p, const void *q, __kernel_size_t size)
      |                        ^~~~~~~
./arch/mips/include/asm/string.h:57:50: error: expected declaration specifiers or '...' before '(' token
   57 | #define memcmp(src1, src2, len) __builtin_memcmp((src1), (src2), (len))
      |                                                  ^
./include/linux/string.h:435:22: note: in expansion of macro 'memcmp'
  435 | __FORTIFY_INLINE int memcmp(const void *p, const void *q, __kernel_size_t size)
      |                      ^~~~~~
./arch/mips/include/asm/string.h:57:58: error: expected declaration specifiers or '...' before '(' token
   57 | #define memcmp(src1, src2, len) __builtin_memcmp((src1), (src2), (len))
      |                                                          ^
./include/linux/string.h:435:22: note: in expansion of macro 'memcmp'
  435 | __FORTIFY_INLINE int memcmp(const void *p, const void *q, __kernel_size_t size)
      |                      ^~~~~~
./arch/mips/include/asm/string.h:57:66: error: expected declaration specifiers or '...' before '(' token
   57 | #define memcmp(src1, src2, len) __builtin_memcmp((src1), (src2), (len))
      |                                                                  ^
./include/linux/string.h:435:22: note: in expansion of macro 'memcmp'
  435 | __FORTIFY_INLINE int memcmp(const void *p, const void *q, __kernel_size_t size)
      |                      ^~~~~~

--- cut ---

Dropping this patch, adjusting mtk7621 nand driver and it success boot on mt7621.

And yes, DSA interfaces come up faster:

--- 5.8.16 ---
[   23.378250] mtk_soc_eth 1e100000.ethernet eth0: Link is Down
[   23.394552] mtk_soc_eth 1e100000.ethernet eth0: configuring for fixed/rgmii link mode
[   23.403086] mtk_soc_eth 1e100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[   23.412139] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   23.423265] device eth0 entered promiscuous mode
[   23.600168] mt7530 mdio-bus:1f lan1: configuring for phy/gmii link mode
[   23.650656] 8021q: adding VLAN 0 to HW filter on device lan1
[   24.460634] br-lan: port 1(lan1) entered blocking state
[   24.465865] br-lan: port 1(lan1) entered disabled state
[   24.530026] device lan1 entered promiscuous mode
[   25.670004] mt7530 mdio-bus:1f lan2: configuring for phy/gmii link mode
[   25.740319] 8021q: adding VLAN 0 to HW filter on device lan2
[   26.610853] br-lan: port 2(lan2) entered blocking state
[   26.616128] br-lan: port 2(lan2) entered disabled state
[   26.740081] device lan2 entered promiscuous mode
[   27.750001] mt7530 mdio-bus:1f lan3: configuring for phy/gmii link mode
[   27.860316] 8021q: adding VLAN 0 to HW filter on device lan3
[   28.870141] br-lan: port 3(lan3) entered blocking state
[   28.875367] br-lan: port 3(lan3) entered disabled state
[   29.060023] device lan3 entered promiscuous mode
[   30.289991] mt7530 mdio-bus:1f lan4: configuring for phy/gmii link mode
[   30.380314] 8021q: adding VLAN 0 to HW filter on device lan4
[   31.300600] br-lan: port 4(lan4) entered blocking state
[   31.305821] br-lan: port 4(lan4) entered disabled state
[   31.580013] device lan4 entered promiscuous mode
[   32.820014] mt7530 mdio-bus:1f lan0: configuring for phy/gmii link mode
[   32.950310] 8021q: adding VLAN 0 to HW filter on device lan0
[   35.820007] mt7530 mdio-bus:1f lan0: Link is Up - 1Gbps/Full - flow control off
[   35.827350] IPv6: ADDRCONF(NETDEV_CHANGE): lan0: link becomes ready

--- 5.9.1 ---
[   36.410583] mtk_soc_eth 1e100000.ethernet eth0: Link is Down
[   36.417543] mtk_soc_eth 1e100000.ethernet: PPE table busy
[   36.442444] mtk_soc_eth 1e100000.ethernet eth0: configuring for fixed/rgmii link mode
[   36.450958] mtk_soc_eth 1e100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[   36.459831] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   36.469886] device eth0 entered promiscuous mode
[   36.475362] mt7530 mdio-bus:1f lan1: configuring for phy/gmii link mode
[   36.482770] 8021q: adding VLAN 0 to HW filter on device lan1
[   36.492117] br-lan: port 1(lan1) entered blocking state
[   36.497483] br-lan: port 1(lan1) entered disabled state
[   36.504203] device lan1 entered promiscuous mode
[   36.538089] mt7530 mdio-bus:1f lan2: configuring for phy/gmii link mode
[   36.545568] 8021q: adding VLAN 0 to HW filter on device lan2
[   36.554971] br-lan: port 2(lan2) entered blocking state
[   36.560304] br-lan: port 2(lan2) entered disabled state
[   36.567270] device lan2 entered promiscuous mode
[   36.583029] mt7530 mdio-bus:1f lan3: configuring for phy/gmii link mode
[   36.590376] 8021q: adding VLAN 0 to HW filter on device lan3
[   36.599536] br-lan: port 3(lan3) entered blocking state
[   36.604799] br-lan: port 3(lan3) entered disabled state
[   36.611677] device lan3 entered promiscuous mode
[   36.629413] mt7530 mdio-bus:1f lan4: configuring for phy/gmii link mode
[   36.637127] 8021q: adding VLAN 0 to HW filter on device lan4
[   36.647103] br-lan: port 4(lan4) entered blocking state
[   36.652481] br-lan: port 4(lan4) entered disabled state
[   36.659662] device lan4 entered promiscuous mode
[   36.687630] mt7530 mdio-bus:1f lan0: configuring for phy/gmii link mode
[   36.695271] 8021q: adding VLAN 0 to HW filter on device lan0
[   39.782183] mt7530 mdio-bus:1f lan0: Link is Up - 1Gbps/Full - flow control off
[   39.789556] IPv6: ADDRCONF(NETDEV_CHANGE): lan0: link becomes ready