-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Intel/Amazon Rusty AML parser #215
Comments
I've not heard about this - do you have a link? Realistically, if somewhere like Intel or AWS invest time into a Rust AML parser, it would likely speed past us in terms of completeness and usage, especially as they would likely have a production use for it. To me, that wouldn't change the goals of the project (to have a community-maintained Rust AML parser that is aimed at (semi-)hobbyist OSs), but depending on how quickly it matures projects may feel that another solution suits them better, not sure. |
This is the only version I could track down. They seem to have a goal of using S5 in firecracker, but they are not there yet. |
Ahh - this is for producing the ACPI tables that are passed to guests running inside a Firecracker VM I guess? If the guest is Linux or whatever, it's still going to use it's AML parser to parse those tables. We could make sure we can successfully parse their tables (I imagine they'll be simple given Firecracker's aims), but other than that our goals are mostly orthogonal I think. |
My concern was that there is a "Copyright Intel" at the top, but I don't know what the source of the copyright claim is, and I haven't been able to find any Intel project that is moving this forward. As long as it stays a Firecracker thing, I think we are on a different path. |
Any thoughts on the Intel and Amazon work on Rusty AML? Do you think they will catch up to this project in the medium-term future? Will this project have an advantage over them long term or will Intel Rusty AML become more widely accepted?
The text was updated successfully, but these errors were encountered: