Andrew Sharp
Kernel investigation
Kernel 5.10.84 booting on havic box using initrd.
With Landcruiser connected to Gen3, I now see this in the PCI bus scan:
03:00.0 Non-VGA unclassified device: Hewlett-Packard Company Device 1158 (rev 01) Subsystem: Hewlett-Packard Company Device 1158 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at d0000000 (32-bit, non-prefetchable) [size=256M] Memory at e4000000 (32-bit, non-prefetchable) [size=64M] Memory at e0000000 (32-bit, non-prefetchable) [size=64M] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/32 Maskable+ 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [148] Latency Tolerance Reporting Capabilities: [150] #1e
This is good news! None of the drivers automatically load, so that has to be investigated. Possibly that doesn't happen until more of the hardware is present.
Road ahead
I want to start looking at building the kernel drivers against the two new kernels.
Thoughts on userspace are still formulating. There is quite a lot going on in the ljlinux/fw directory, and I still trying to get a complete enough picture for a plan to emerge that doesn't put us in a position of big risk. In other words, at the very least a viable fallback plan has to be there, or a way to use the old tools/userspace even from within a modern 64-bit userspace.
Putting together a list of coherent questions for Lance regarding build environment that might need to be re-done if userspace is changed to 64-bit modern.