freifunk-darmstadt / gluon-firmware-selector

Firmware selector for gluon router images

Home Page:https://firmware.darmstadt.freifunk.net/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Display "flashing hint"

kpanic23 opened this issue · comments

There are more and more devices which can't be flashed the "traditional" way using the stock web UI.

What about, after choosing a router, show a little hint about how this router is to be flashed.
Like:
"Use the factory image to update from the stock firmware's webinterface"
or
"use fritzfla.sh"
or
"has to be flashed via TFTP, rename image to tp_recovery.bin"
or
"copy image to device via scp and flash using mtd",
something like that.

People keep asking me how this and that router is to be flashed, giving a hint right at the firmware selection would make it much easier for people that are not as close to gluon development.

isn't this the same as #79 ? maybe at least theses issues overlap

now that you point it out: sort of.
but I suggest displaying it for every device, not only the ones in "other"

I think this falls under the category of "device meta-information". I was thinking about adding those a while back, to allow communities to e.g.

  • Filter devices based on their Flash / RAM / Radios
  • Pin recommended devices
  • Display hardware-specs next to the device
  • Show installation information

Currently, our device definition format does not allow for storing such meta-information, so someone probably has to restructure and research this information. Next we can start building features which utilize these information.

This appears to be rather important, as several of tp-links archer series have some hickups lately, when flashed via UI.
OpenWrt has the info on their page, but without adressing of this issue, more and more users will leave the project frustrated, before they've even started.

Neither me nor @blocktrron are really into web stuff. So don't expect a solution from us. We see the need for this as well, but the current interface is lacking anyway.

The best idea I encountered up until today was to use a wizard kind of guide, something along the lines of