@magorium: the experiment looks promising. The strange thing which I see is this:
Yeah, i know :-)
I got to work with what the grub tools offers me (well, not really but since i am new to grub and its particularities with regards to hybrids i have to see/understand what grub puts to xorriso)
Well, it can stay there as long as your solution works.
I got some very strange (sometimes even unrepeatable) results, and of course the perfect solution would be that gpt and efi support is added as well (according to kiwi devs that is possible to do with grub but nobody seems to do that and use other solutions instead, so the interwebs is pretty quiet for me atm).
Unfortunately I've no expertise in that area. I've studied how EFI/UEFI works, but GRUB is a different beast. I hope that you can find some solution to add GPT & EFI, or someone that can help.
... because it's not possible to find the VendorID & DeviceID couple on the PCI devices database which I've used
I think that is something you would have to learn to live with ?
For example, the nvidia ones are not even listed on the nvidia's driver website (https://www.nv-drivers.eu/driver-by-vendev.html) or perhaps no specific drivers are needed for the device
There even might be the possibility of fake or miss-reported hardware or hardware that is/was experimental or not intended for mainstream availability (developer specific hardware for example). There are quite a bunch of fake video-cards around for example.
The only person that has the relevant information is the user who has such hardware and is able to identify it correctly (and contribute that knowledge to a pci database)
I did have a quick look around though, but was also unable to find any further hints on these unknown list of devices except for a pci database about nvidia here (https://envytools.readthedocs.io/en/latest/hw/pciid.html) which for example suggest that device 0775 (MCP77) is a memory controller ( https://envytools.readthedocs.io/en/latest/hw/pciid.html#pci-ids-mcp77 )
This week I was busy helping my daughter for a project, but at least I had the time to think about it, thanks also to your input.
IMO we shouldn't focus on and pretending to support all devices by just taking into account all vendor + device ids couples. From your above example, which value gives us knowing that we support an nVidia's memory controller? I think zero. I don't even think that AROS needs to load a specific driver to make work & use such "peripheral".
What's important is that we have a list of supported GPUs, sound cards, hard drive, ethernet controller, etc..
So, and to be short, what we need is a list of supported vendor id + device id + class id (and maybe sub-class id), taking into account only the class ids which make sense (e.g.: not a generic memory controller). Because the class id gives us the information about which kind of peripheral it is.
When I've time I'll take a look to the PCITool to see how to get the missing information, and maybe export it as well.
