Daniel Golle

Actually `MESON_USE_STAGING_PYTHON:=1` should make sure that OpenWrt-built Python in `hostpkg` is being used, so the real question here is why that doesn't work. Does your openwrt.git tree include commit openwrt/openwrt@41f7322853621ea14a2d057cd6322014307acc02?

Building all the recently added Mesa and Wayland packages on openwrt-24.10 will fail for a number of reasons, such as packages missing in the openwrt-24.10 branch of the packages feed....

libinput and friends come to mind as well as gstreamer stuff (if one would build `weston` and WPEWebKit's `cog`)

Afair newer version of libinput was required for wayland stuff to build, missing gstreamer modules were required for WPEWebKit... But sure, give it a try, if all works I'll happily...

Should be fixed by 2b173ab730897f53539cab39e87e2b4638cb482a Please try and report

Yes, this adapter should work. Connect only GND to GND, TX to RX and RX to TX.

`kmod-phy-aquantia` was added to the target-wide set of default packages in order to always have it included also in initramfs images. This consideration is now obsolete as also initramfs filesystem...

> patch DSA to not use label if netdev name collision (potentially up-streamable): dirty example: I think instead of `dev_net(master)` you should just point to `&init_net`, but apart from that...

Upstream suggested introducing a downstream property `openwrt,netdev-name` to keep handling this in userspace. Imho this sounds acceptable and doesn't need any kernel changes, and still allows for dropping the downstream...

Let's use another property name in device tree, such as `openwrt,netdev-name` like upstream reviewer Vladimir Oltean [has suggested](https://lore.kernel.org/netdev/20240709124503.pubki5nwjfbedhhy@skbuf/). For starters we can simply support both, renaming according to `label` as...