You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I was trying to integrate the aml/acpi crates into my kernel and found out that some of the real-hardware opcodes are NYI.
I'm currently working on implementing DefIndexField myself, but there's problem that might require significant changes to the aml crate: as IndexFields require writes to their index fields even when reading, this means functions like as_integer/as_string/as_buffer/etc as well as the read_field also perform writes and thus require mutable ref to AmlContext, which breaks lots of other code. A simple workaround would be to add a separate AmlType for IndexFields, but I don't think this is correct as per specification.
So, if you can suggest which way is better, I can finish this feature and make a PR.
Thanks.
The text was updated successfully, but these errors were encountered:
Hi,
I was trying to integrate the
aml
/acpi
crates into my kernel and found out that some of the real-hardware opcodes are NYI.I'm currently working on implementing
DefIndexField
myself, but there's problem that might require significant changes to theaml
crate: asIndexField
s require writes to their index fields even when reading, this means functions likeas_integer/as_string/as_buffer
/etc as well as theread_field
also perform writes and thus require mutable ref toAmlContext
, which breaks lots of other code. A simple workaround would be to add a separateAmlType
forIndexField
s, but I don't think this is correct as per specification.So, if you can suggest which way is better, I can finish this feature and make a PR.
Thanks.
The text was updated successfully, but these errors were encountered: