You should be able to just compile the driver(s) from aircrack-ng on device and modprobe it, this used to work (with usb attached wifi dongle), but maybe now needs some extra kernel_config tweaks, getting those in base config would make sense if itās no longer working (including drivers for devices not included on phone by default is a bit harder sell)
Is that an issue really, pretty much all devices stay on the initial kernel afaik? So it should be once and done exercise (on the upstream kernel C2 like projects this could be tedious, but again doubt)
How do you plan to distribute a package for each device? Not OBS afaik, that only covers x.y.z versioning not hw adaptation, maybe add instructions and .sh file so people can run it on whatever device they are? (there are some legacy/outdated ā(for jolla C/xperia X only)ā rpms on openrepos but that also sucks)
But then another person with xyz dongle will ask for inclusion of its driver too and it opens a whole pandoraās box, instead maybe host a website with rpms for each device youāre willing to support and everyone there can click a single rpm (called something like [device]-atheros-driverā¦rpm, [device]-broadcom⦠(and a bunch others for all other dongles you plan to support)), these should be once per device unless for upstreamed kernel ones but thatās still hypothethical mostly, if kernel_configs are blocking that, sure a valid concern tho
But thatās just you, you can bring it to a community meeting, but if that floodgate opens there will be more people like you for whom xyz123 is actually crucial and needs to be included and over and over again, shipping drivers for all possible 100k dongles is pretty bad idea, but who knows if you can present a good reasoning during the community meeting maybe jolla will⦠Just doubtful, but worth a try?