(no subject)

Hello Srinivas,

I am writing to report hardware verification findings regarding the Intel
Integrated Sensor Hub (ISH) on the HP OmniBook X Flip 14-fm0xxx series
(Intel Lunar Lake) running Linux.

Hardware details:
- Model: HP OmniBook X Flip Laptop 14-fm0xxx (14-fm0023dx, SKU: B5UJ2UA#ABA)
- Platform: Intel Core Ultra 7 256V (Lunar Lake LNL-M)
- BIOS Revision: F.10 (2025-10-22)
- PCI Device: 0000:00:12.0 [8086:a845] (rev 10), Subsystem: [103c:8d9f]

Observed behavior:
With current upstream linux-firmware (including ish_lnlm.bin and
ish_lnlm_12128606_f9751b71.bin.zst / v58.0.7720), the kernel driver
(intel_ish_ipc) fails during boot with:

  intel_ish_ipc 0000:00:12.0: ISH loader: load firmware:
intel/ish/ish_lnlm_12128606.bin
  intel_ish_ipc 0000:00:12.0: ISH loader: cmd 2 failed 10

Testing other newer OEM builds (such as 5.8.0.7726 and 5.8.0.7729) also
fails with status 10 on LOADER_CMD_START due to signature/version
enforcement in the F.10 BIOS CSME enclave.

Resolution:
Inspecting the factory Windows installation DriverStore
(ishheciextensiontemplate.inf_amd64_*) shows that HP configured this
platform with:
- Firmware: ishS_SI_5.8.0.7718.bin
- Size: 645,632 bytes
- ISHG Version: 5.8.0.7718
- MD5: cde0b12d3a68f240c6423a7e93f29409
- SHA-256: 2d9f9bd732bfc80208b50645ff9fc6fdc1b046be71f7d4780ea6858d1676c759

When this binary is provided at the calculated DMI paths:
- Exact: intel/ish/ish_lnlm_12128606_604fc7b4_e4cc03e5_ed8665c2.bin
- Fallback: intel/ish/ish_lnlm_12128606.bin

The ISH coprocessor boots cleanly without error:
- Base Version: 5.8.0.7718
- Project Version: 1.0.0.12584
- Registered IIO devices: gyro_3d, accel_3d, and hinge
- iio-sensor-proxy operates correctly and auto-rotation functions.

DMI fields on this system:
- sys_vendor: "HP" (CRC32: 12128606)
- product_family: "103C_5335M8 HP OmniBook X" (CRC32: 604fc7b4)
- product_name: "HP OmniBook X Flip Laptop 14-fm0xxx" (CRC32: e4cc03e5)
- product_sku: "B5UJ2UA#ABA" (CRC32: ed8665c2)

Would it be possible to include this 5.8.0.7718 firmware release in
upstream linux-firmware for HP systems with this DMI/subsys signature, or
coordinate with HP for an updated upstream submission that avoids the
authentication failure?

Thank you for your time and continued maintenance of the ISH subsystem.

Best regards,
Rayr