-
Notifications
You must be signed in to change notification settings - Fork 110
devices/x86_64: add cmos legacy device #419
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
base: main
Are you sure you want to change the base?
Conversation
Add ram size info to ArchMemoryInfo, since we're going to need for the CMOS legacy device. Signed-off-by: Sergio Lopez <[email protected]>
0ed164d
to
866d449
Compare
u-boot uses a legacy CMOS device to obtain the ram size, so do a minimal implementation ourselves. Signed-off-by: Sergio Lopez <[email protected]>
We need to inject the firmware region just before the last one. Fix it to do it properly. Signed-off-by: Sergio Lopez <[email protected]>
866d449
to
0f7eb91
Compare
IIUC this legacy device is always enabled in x86-64, am I right? may we have a way to decide to use it or not? |
Yes, so far we've tried to always use the same set of legacy devices, only moving around the virtio ones. I think it's better to always have the cmos device (which is very small and innocuous) present. |
@MatiasVara do you need more changes to this PR? |
I have nothing to add. It LGTM. I did not try it though. |
u-boot uses a legacy CMOS device to obtain the ram size, so do a minimal implementation ourselves.
While there, also fix a bug in the recently introduced firmware support code.