Tony Kuriakose Nadackal authored 6 years ago and Suhas Kunnath committed 6 years ago

Reference document - Vesta_fuses_v3.xls

Tony Kuriakose Nadackal authored 6 years ago and Suhas Kunnath committed 6 years ago

One of the qca6234 or qca9377 Wifi modules will be used
dynamically depends on the board type .

It will hang the system if the chip is not present.

Also move dosfstools from developer to minimal so it can be used by the minimal image.

Also add nmon to developer build. Nigel's performance Monitor for Linux.

Removed tests from bottom of CVE-2017-1000254.patch to git it to merge.

Renamed node-red-contrib-noble-connect to rigado-devkit
Update commit ids for iot-gateway-setup and rigado-devkit

Created custom network interface file.

The firmware-vesta layer is board dependent so it was moved to the machine conf files.
Added new board conf file called vesta-rad.

Added vesta-image-minimal-sc image to fit on vesta-nor boards.
Moved blacklist.conf to scripts-vesta so it is always installed.

Moved setmac to rcS.d.

Vladimir Petrigo authored 7 years ago and Pete Tucker committed 7 years ago

Due to the fact that we use node-red user for Node-RED instance it is
not possible for noble package to use BLE hardware without root
privileges. So we have to provide a cap_net_raw capability to Node.js to
allow such packages to use system hardware

Vladimir Petrigo authored 7 years ago and Pete Tucker committed 7 years ago

Now the init script uses node-red user as a Node-RED process holder.
Node-RED settings.js is modified to use 8080 port to listen

Vladimir Petrigo authored 7 years ago and Pete Tucker committed 7 years ago

- Init script for launching a Node-RED instance on the system boot
- Recipe for node-red user creation