On 2018-05-05 16:35, Linus Walleij wrote:
On Sat, May 5, 2018 at 11:25 AM, Linus Walleij
<linus.wall...@linaro.org> wrote:
On Fri, May 4, 2018 at 11:49 PM, Linus Walleij
<linus.wall...@linaro.org> wrote:
On Fri, May 4, 2018 at 11:37 PM, Roman Yeryomin <ro...@advem.lv>
wrote:
The GPIO LEDs does not come up though?
CONFIG_LEDS_GPIO is not in config, and
/sys/class/leds is empty.
Does it need a separate kmod?
kmod-leds-gpio is part of DEFAULT_PACKAGES now
I guess you should run menuconfig and/or clean tmp/ to refresh
profile
package set.
Hm I ran menuconfig and it doesn't work, and removing
tmp/ didn't help either, but selecting a different target
and then selecting CS351x again worked... shaky.
OK rebuilding this overnight and retesting.
It is still not working. Do you get GPIO LEDs on your
device with this?
AFAICT the problem is that there is no script in
/etc/modules-boot.d to load the GPIO LED module.
I'm digging into it to figure out more about how this
module load is supposed to work...
Sorry probably bad mechanics from my side, like replacing
the rootfs but not the kernel :(
The good news is: it works like a charm.
All vital components are running, drivers probe, modules
load correctly from the hard drive.
Yeah.. they should be, that's one of the most common modules here :)
On Raidsonic:
root@OpenWrt:/# lsmod | grep led
leds_gpio 2772 0
ledtrig_heartbeat 1570 0
_______________________________________________
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
