mirror of
https://github.com/kernelkit/infix.git
synced 2026-08-04 06:43:00 +02:00
Joachim Wiberg
a9cadd7b70
The "Running config has unsaved changes" banner kept showing after a power cycle even though the device reloaded running from startup at boot. The cookie was just "1" with a 24-hour MaxAge, so the browser held on to it and the banner stayed up — but the state it referred to was long gone. Carry a unix timestamp in the cookie value (when set) and compare against a webuiStartTime captured at process start. Cookies whose timestamp predates this run are from a previous boot or webui restart; running was reloaded from startup since then, so they no longer describe reality and the banner must stay hidden. - Apply / Restore-to-running: cookie = now → banner shown. - Power cycle, page load: webuiStartTime > cookie ts → banner hidden. - Save / Apply-and-Save: cookie cleared (unchanged). - Legacy "1" / unparseable values: treated as stale. Also centre the "Device unreachable" connectivity banner past the sidebar on desktop — left:0 leaves its text drifting behind the sidebar's z-index. On ≤1024px the sidebar slides off-screen so the banner reclaims full width. Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Board Support
The board support for an architecture always starts with Qemu support,
this is what each linux_defconfig at the very least sets up. Then
each $BR2_ARCH has additional BSPs, e.g., Banana Pi BPI-R3.
The board/ directory is matched with the configs/*_defconfigs and
the only execption is board/common/, which holds all shared files for
Infix builds.
Each board/$BR2_ARCH/ can then have vendor/product sub-directories
for the BSPs which may contain "fixups" to the base kernel config and
any additional device tree files that should be included as well.
To rebuild a board-specific package, e.g. NanoPi R2S:
make friendlyarm-nanopi-r2s-rebuild all