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
As part of discovering #339, we realized we've not been recording things like the spec revision compliance for past modules we've qualified. We put all the data we think is relevant in some tables for those qualified parts, but it's hard to keep that table up to date as we discover new fields that are now relevant. Rather than keeping it up to date, it'd be great to save the entire memory map to a file so that we can refer to it later. But to make sense of that, we probably also want to have a way to read back the memory map and interpret it from that same file.
The text was updated successfully, but these errors were encountered:
As part of discovering #339, we realized we've not been recording things like the spec revision compliance for past modules we've qualified. We put all the data we think is relevant in some tables for those qualified parts, but it's hard to keep that table up to date as we discover new fields that are now relevant. Rather than keeping it up to date, it'd be great to save the entire memory map to a file so that we can refer to it later. But to make sense of that, we probably also want to have a way to read back the memory map and interpret it from that same file.
The text was updated successfully, but these errors were encountered: