On 09.09.21 08:04, Andreas Bauer wrote: > By the way, during this process a thought occured to me: this process of > manually poking different configurations, basically trial and error, does > not scale very well. > > IF we have a vendor bios that does all the magic sauce, and even know > something about the structure of that vendor bios, and usually have enough > space in the flash to fit both coreboot and vendor bios into the same chip, > why not develop a sort of debugging hypervisor that documents all the > mm/io registers modified, exacting timestamps and code flow ? > > Such a detailed boot log of all settings could be compared between different > implementations of the same platform and a new port would be much easier.
You mean something like serialice.com? ;) This is not using a hypervisor but running the firmware in an emulator. But otherwise pretty much what you describe. It's always a bit fiddly to get it running, but I guess with a hypervisor it would be about the same. Nico _______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]
