Uniquely identifying a platform programmatically

Daniel Golle daniel at makrotopia.org
Tue May 18 01:28:15 PDT 2021


On Mon, May 17, 2021 at 04:43:24PM -0600, Philip Prindeville wrote:
> Hi,
> 
> I was wondering what the best way to map a running box back to a candidate image would be.
> 
> It seems like the tuple ($CONFIG_TARGET_BOARD, $CONFIG_TARGET_SUBTARGET, $CONFIG_TARGET_PROFILE) would provide this, since you can mangle them into a bin/targets/$CONFIG_TARGET_BOARD/$CONFIG_TARGET_SUBTARGET/openwrt-*-$CONFIG_TARGET_BOARD-$CONFIG_TARGET_SUBTARGET-$CONFIG_TARGET_PROFILE-squashfs-sysupgrade.bin (or -factory.bin) image for provisioning...
> ...
> 
> Any suggestions welcome.

ubus call system board

That's what is used also by `auc` and `luci-app-attendedsysupgrade`,
it contains all information you need to know in order to decide which
target/subtarget ImageBuilder to use and which profile (=board) to
select.
 



More information about the openwrt-devel mailing list