firmware selector for openwrt.org

[Moritz Warning]

On 7/5/20 11:34 AM, Rafał Miłecki wrote:
> On Mon, 8 Jun 2020 at 20:40, Moritz Warning <moritzwarning at web.de> wrote:
>> would it be desirable to have this for openwrt.org?
>>
>> https://mwarning.github.io/yet_another_firmware_selector/
>
> I like it and I'd happily see it as an *addition* to
> downloads.openwrt.org. I think we really should keep existing (manual)
> downloads browsing at the same time.
Agreed.

>
> One thing I'd love to see is matching OpenWrt running firmware with
> download-available firmwares. Right now I can get device id and name
> using:
Isn't the attended sysupgrade luci module already offering that?
https://github.com/openwrt/luci/tree/master/applications/luci-app-attendedsysupgrade

> # cat /etc/board.json | jsonfilter -e '@.model'
> { "id": "luxul,xap-1610-v1", "name": "Luxul XAP-1610 V1" }
>
> In profiles.json I can find something like:
> {
>     "metadata_version":1,
>     "profiles":{
>         "luxul-xap-1610":{
>             "image_prefix":"openwrt-bcm53xx-luxul-xap-1610",
>             "images":[
>                 {
>                     "name":"openwrt-bcm53xx-luxul-xap-1610-squashfs.lxl",
>
> "sha256":"c0bec512c415257addc102406b13b16cff1fa779feed2ac7757ee9122786f8d5",
>                     "type":"lxl"
>                 }
>             ],
>             "supported_devices":[
>
>             ],
>             "titles":[
>                 {
>                     "title":"Luxul XAP-1610"
>                 }
>             ]
>         }
>     },
>     "target":"bcm53xx/generic",
>     "version_code":"r11130-d46650de7c",
>     "version_number":"19.07-SNAPSHOT"
> }
>
> Any advice on how to solve that?
> 1. Match by "name" / "title"?
> 2. Add "id" to profiles.json (host)?
> 3. Add "profile" to board.json (device)?
>
>
>> The setup would need the following OpenWrt option to create the JSON data:
>>
>> "Global build settings" ---> "[*] Create JSON info files per build image"
>>
>> And a script to merge it into one file.
>
> Buildbot builds with
> CONFIG_BUILDBOT=y
> which should be enough thanks to
>
> config JSON_OVERVIEW_IMAGE_INFO
>     bool "Create JSON info file overview per target"
>     default BUILDBOT
>
> Maybe it's a problem with one of *upload steps in phase1/master.cfg?
>