Re: Uniquely identifying a platform programmatically

2021-05-18 Thread Daniel Golle
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, s

Re: Uniquely identifying a platform programmatically

2021-05-17 Thread Petr Štetiar
Philip Prindeville [2021-05-17 16:43:24]: > I could grovel the target profile out of /etc/board.json, but then my > scripting needs to support 'jq', etc. $ ubus call system board | jsonfilter -e @.model -e @.board_name -- ynezz ___ openwrt-devel mai

Re: Uniquely identifying a platform programmatically

2021-05-17 Thread Philip Prindeville
Okay, I've created a PR to make this change: https://github.com/openwrt/openwrt/pull/4184 > On May 17, 2021, at 4:43 PM, 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 ($CONFI

Uniquely identifying a platform programmatically

2021-05-17 Thread Philip Prindeville
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_S