@Whitterquick My machine died of the infamous power plain issue common on this series a few months back, and I've since moved to 12th gen Core for AVX512 developement.
what may be best moving forward would be to use gits patch application mechanism directly, or otherwise provide notes on how...
Apologies for the slow reply.
Beyond the script itself, best way is to look at the actual lines being modified in the source driver instead of using the script, which may or may not continue to work on up stream
I've pulled source for 5.15 and will be compiling in the next day or so.
My...
the modifications had to do with other parts of the kernel, not with the patch itself- specifically they had to do with the binder kernel module.
In other words, this patch is portable to other custom kernels.
I never mentioned it here, but I'm running the 5.11 main kernel branch with the patch and other modifications.
still knee deep in other projects involving the kernel (working on GPGPU accels on NVIDIA jetson nanos and on porting the googles changes to QEMU to the main branch of QEMU)
it may be possible to do so assuming you mean via something like DKMS.
until then:
Quite busy ATM, but if you want to test yourself:
download source for kernel 5.8+. untar/zip etc.
cd linux
make clean
make oldconfig
scripts/config --enable CONFIG_HP_ILO=Y
make prepare
make -j35...
not a package, it's a kernel configuration option when building from source
I've yet to test this, but came across it while compiling a custom kernel for a work thing
in your kernel source folder run
scripts/config --enable CONFIG_HP_ILO=Y
to enable the ilo2+ interface.
then run nano...
News on alternative method: turns out there's a built in kernel module that's rarely if ever enabled for hp ilo2+ support.
This may mean we can remove the Rmrr for certain slots as proposed previously
Sorry, not sure I understand your question.
If the question is can you compile a kernel from a VM, then yes absolutely. a Kernel is just a very advanced/complex program. If you wanted to you could compile the same Kernel IBM uses for PowerPC from a raspberry pi etc.
if you're asking can you...
So that's pointing to a memory mapping error of some sort. Are you passing through the entire device? otherwise it looks like you're not alone in this per https://forum.level1techs.com/t/looking-for-vfio-wizards-to-troubleshoot-error-vfio-dma-map-22/153539
from the second line of qemu...
Mind sharing the error you received? I've been trying to get conrep working on g6/g7 which ate both officially supported, but haven't had success with it. if the errors aline it may point to conrep to correctly writing data or our input parameters not being parsed correctly