-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HDAT documentation #264
Comments
This question was also asked here: https://lists.ozlabs.org/pipermail/openpower-firmware/2021-May/000641.html |
I'll 2nd the suggestion Stewart made in that thread and say you should generate a DTB and pass that to skiboot. The HDAT spec is less of a spec and more of a description of what the IBM proprietary firmware stack happens to be doing for each system generation. It's probably never going to become public so I think you're better off just ignoring it entirely. I don't think anyone thought having skiboot consume HDAT on OpenPower systems was a really good idea. It was just convenient at the time. |
@oohal Thank you! Are there any pointers to how this DTB should look like? How is the DTB presented by the earlier firmware to |
Look into
Hosbtoot provided DT contains only hardware details. We expand that in skiboot and add other nodes like -Vasant |
Hi,
We are working on coreboot support for POWER9.
Recently we have achieved the milestone where we could initialize the
memory on the Talos II platform and start the coreboot ramstage phase:
https://github.com/3mdeb/openpower-coreboot-docs/blob/main/releases.md
What we would like to achieve next is to start skiboot from coreboot.
We can see that there is this HDAT interface between Hostboot and skiboot
(https://open-power.github.io/skiboot/doc/overview.html#booting) which we probably
would need to reimplement.
Sadly, the documentation (https://open-power.github.io/skiboot/doc/overview.html#booting)
says that "The HDAT specification is currently not public.".
Any idea why is that? Can we get some more information about
the HDAT somewhere (apart from reading the Hostboot code)?
Thanks,
The text was updated successfully, but these errors were encountered: