Long shot: Does anyone have any PGD51 firmware files (as in, ending in `.PGD51`) they can send me? They'll be from a keyboard firmware updater program, from various OEMs. Any model is fine, I'm just testing a firmware parser with real world data. Thanks!
@mntmn I want this to succeed so hard. From someone in the trenches of a closed hardware ecosystem this is exactly what the world needs.
If anyone needs convincing, I've seen first-hand how the MNT team do the right thing and how much they care. I'm sure they'll hit the funding goal, but please boost and share to your networks to make sure they smash it.
I'd purchase one myself, but I already have dozens (literally...) of laptops, and my wife would kill me if another turned up.
@nixCraft I'm always very humbled to see posts like this. My special obsession has been firmware for the last 7 or so years and it's nice to see LVFS and fwupd is useful for so many people.
@mntmn literal flames? I've only had one board with actual *fire*, and that was with a low voltage supercap that leaked when a programmable vreg went crazy.
@mntmn absolutely -- ideally using a custom VID/PID and then using the bcdREV as the version number. If you can do that then I can do all the other bits.
@mntmn I tried flashing the sysctl.uf2 onto a random RP2 I had here (which worked) -- but the million dollar question -- how do I get firmware version of the RPi device when in "runtime" not UF2 mode? i.e. how does fwupd know that the update needs to be deployed?