On Mon, Jun 27, 2016 at 01:38:43AM +0200, Martin Blumenstingl wrote: > On Sat, Jun 25, 2016 at 9:26 PM, Christian Lamparter > <chunk...@googlemail.com> wrote: > > I've added lede-dev and Luis since this is relevant for them. > > Maybe between the sysloadfw.sh and owl-loader, there's another > > solution we overlooked so far? I know Luis has been digging > > around in the firmware_class and added the sysdata API. But > > from what I can tell, this would ?break? LEDE/OpenWRT's > > userspace helper, since the sysfs interface in > > /sys/class/firmware which is used by procd to upload the data > > is gone with sysdata or am I wrong? > good idea to keep lede-dev in the loop, as they will be affected (in > my opinion: positively) by this change.
We cannot remove the /sys/class/firmware usermode helper, it however should be compartamentalized to only a few device drivers that we *know* definitely need it. So far there are only 2 device drivers that we've identified as needing it and as such only those drivers should implicate use of it. In the future, should the sysdata API get merged, the implications are that the further features of the firmware API will be added for sysdata users, but perhaps not for the old API as that entails silly collateral evolutions to the API or new exported symbols. I highly encourage use of the usermode helper to be reconsidered and simply abandoned. There are many reasons why it was a bad idea, for details refer to the thread [0]. [0] https://lkml.kernel.org/r/1466117661-22075-1-git-send-email-mcg...@kernel.org Luis _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
