Issue #571 has been updated by Wreg Yek.
Bill XIE wrote in #note-2: > This sp96088.exe contains an MS cabinet archive, and could be extracted with > cabextract(1) to obtain another cabinet archive Rom.CAB, which can be > extracted to obtain a 5MB Rom.bin, with the same size as the BIOS region of > the factory firmware. > > As hinted by ver.txt within Rom.CAB, a 256kB volume with type NVRAM > (recognized by [UEFITool NE](https://github.com/LongSoft/UEFITool)) at > 0x3e0000 of the BIOS region of the factory firmware could be extracted and > overwritten (via [UEFITool old > engine](https://github.com/LongSoft/UEFITool/commits/old_engine), as UEFITool > NE has not been capable of modification yet) onto the volume at the same > offset of the Rom.bin. This modified Rom.bin could be insert back into the > factory firmware as its BIOS region via ifdtool, and the latest oem firmware > (F.72 Rev.A) is obtained. > Incredible. You even found a way to update the oem firmware without using the proprietary tools provided by HP, in the form of EFI executables. ---------------------------------------- Support #571: Keyboard scan codes of HP Elitebook 2170p under coreboot are different with those under oem firmware. https://ticket.coreboot.org/issues/571#change-1978 * Author: Wreg Yek * Status: New * Priority: Normal * Target version: none * Start date: 2024-11-23 * Affected hardware: HP Elitebook 2170p * Affected OS: GNU/Linux with systemd v257-rc1 or later ---------------------------------------- HP Elitebook 2170p is weird compared with many other Elitebooks supported by coreboot, for its keyboard scan codes under coreboot is different with those under oem firmware, regardless of the same set of EC firmware blobs are used. The scan codes under oem firmware conform to the upstream [60-keyboard.hwdb](https://github.com/systemd/systemd/blob/main/hwdb.d/60-keyboard.hwdb), while after systemd v257-rc1, the `KEYBOARD_KEY_66=pickup_phone` within [upstream](https://github.com/systemd/systemd/commit/93b078c3dd40b10eed34a77d514b1db7493b17cf) 60-keyboard.hwdb starts to conflict with the scan codes of backspace key under coreboot, where it is 0x66. Besides backspace, I have collected the scan codes of all Fn-keys under coreboot into the attached 61-2170p-kb.hwdb, which is adjusted to the default SMBIOS tables of coreboot for Elitebook 2170p, and could be used to walk around the scan code conflict. ---Files-------------------------------- 61-2170p-kb.hwdb (508 Bytes) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
