Arch Linux User Repository

I can also verify (as I mentioned earlier) that the UPDATE.mem from Renesas themselves has an identical checksum to the K2026090.mem file in the web archive. So that all checks out.

This PKGBUILD should NOT be flagged out-of-date since only the anyway-3rd-party location changed. @AurelienDuval6 are you able to remove that flag? And probably pin a post explaining the state of this AUR package?

According to PKGBUILD, when installed, UPDATE.mem is extracted from https://web.archive.org/web/20240316231746if_/https://codeload.github.com/denisandroid/uPD72020x-Firmware/tar.gz/refs/tags/1.0.0. To make sure this file is safe, I registered with renesas.com and downloaded the driver from https://www.renesas.com/en/products/upd720202?tab=software-tools . Renesas does not provide checksums, so no way to verify that download. But "K2026090.mem" from the manufacturer's zip is IDENTICAL to "UPDATE.mem" from archive.org. So it's OK to use the archive.org source. Considering the license note I had to acknowledge when downloading, this might be better than if the maintainer would store it here or in some public GIT repo.

And, yes, that file dates back to 2013-11-12. That does not mean that it is faulty. Searching for it revealed no indicators for bugs or even security vulnerabilities in that firmware. That does not mean it's secure either. But it's as secure as it ever was.

I just configured my Xerox WorkCentre 3045 via foo2hbpl2 https://openprinting.org/printer/Xerox/Xerox-WorkCentre_3045 cups http://localhost:631 Network Printer → AppSocket/HP JetDirec socket://192.168.2.1:9100 Xerox Phaser 3040 / WorkCentre 3045 (foo2xqx)

I didn't really notice a need for this. Apart from the missing firmware warning nothing seems to change?

Connect the chaotic-aur repo; it contains upd72020x-fw 1:1.0.0-3

Any update on this warnings? Any trick or workaround to update to the last one?

I removed this firmware packaged and replaced it with a dummy as I was only having it installed to get rid of those pesky warnings.

==> WARNING: Possibly missing firmware for module: 'module_name'

Also, it appears this package has been using the outdated/oldest version of the firmware from the original package for basically... Ever? That's probably incorrect as the tar.gz contains multiple .mem files for newer firmware versions with UPDATE.mem being the oldest of them based on my understanding. The firmware I have corresponds to the UPDATE.mem 2.0.2.6 firmware memory file with SHA-512 hash 1ea117f9a1a772013fb7509c76d731865e6c05ae3c55a304ff42b31ec8a474e9bf16dd1b05b2e5b666ec5fd301aefed54bfeb6bfd7c3f23dc23faf082cf2a9f7, same as in the original file.

I'm not sure when the firmware that was being supplied from the GitHub URL was last retrieved from Renesas but I have a copy of the latest firmware on hand from their official website. There's no cost to acquire this firmware file but you do need to sign up for an account and provide a bunch of personal information to create said account which is... Not great. I can host it but I'm not sure I can put it on GitHub because I'm 90% certain the reason it got taken down before was due to legal claims by Renesas themselves. If I had to speculate.

Any news on an updates for this package?