2022-04-08

Here is a list of items in the fw directory with the .product suffix. Which ones are relevant? Knowing this will help me to get a better understanding of what will be needed for a new build environment.

KahnFusion.product  hpvr.product    nt_c0_mono.product	thor.product
armeb.product	    m385.product*   ntdroid.product*	tron.product
armulator.product   neuron.product  photonr.product	yeti.product
cosim.product	    nt.product*     rfi.product		zinc.product
fonyx.product	    nt_c0.product   tesla.product	zincsmp.product

You mentioned that "64-bit support is in the kernel." Is it in the hosttools driver code (hosttools/{asicif,mipio} and the tron kernel code or ?

Why is gcc needed for buildroot? I don't have any personal experience with buildroot, but I do have considerable past experience creating embedded root filesystems.

'some havic utils might need to change because they've never done 64-bit regarding shared structures with mipio'
'Terry fixed it (64-bit issues mentioned above) for most of his [couldn't make out] code.' What code is that?
'He didn't fix it (64-bit issues) for Havic because there was never a need for it.' When/what/where was there a need for it?

What is meant by 'the CPD side'?

Regarding the build environments in the ljlinux source, are the embedded root file systems always done using docker on HP cloud infrastructure?

Is mono used in current products?

In the ljlinux source, there is evidence of cross-building for an X86 target. Is that a cross build for a product? Is that still an active requirement?