diff options
| author | Christian Lamparter <chunkeey@gmail.com> | 2023-05-17 22:33:36 +0200 |
|---|---|---|
| committer | Christian Lamparter <chunkeey@gmail.com> | 2023-05-18 16:17:52 +0200 |
| commit | ec4d63ffb34337761ccecb4c6f1fc91a4409a95e (patch) | |
| tree | 29062b04793c582470c9c36613dddd2b6df03760 /toolchain/fortify-headers | |
| parent | 4b950bc5f440d389baaed3918d43efcd0a750f7f (diff) | |
| download | upstream-ec4d63ffb34337761ccecb4c6f1fc91a4409a95e.tar.gz upstream-ec4d63ffb34337761ccecb4c6f1fc91a4409a95e.tar.bz2 upstream-ec4d63ffb34337761ccecb4c6f1fc91a4409a95e.zip | |
nu801: add kmod-leds-uleds to MR26 + MR18
support for MR18 and MR26 was developped before
the userspace nu801 was integrated with x86's
MX100 into OpenWrt. The initial nu801 + kmod-leds-uleds
caused build-bot errors.
The solution that worked for the MX100 was to include
the kmod-leds-uleds to the device platform module.
Thankfully, the MR26 and MR18 can just add the uleds
package to the DEVICE_PACKAGES variable.
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
Diffstat (limited to 'toolchain/fortify-headers')
0 files changed, 0 insertions, 0 deletions