| Summary: | power_enums.py to read SPRs from sprs.csv | ||
|---|---|---|---|
| Product: | Libre-SOC's first SoC | Reporter: | Luke Kenneth Casson Leighton <lkcl> |
| Component: | Specification | Assignee: | Luke Kenneth Casson Leighton <lkcl> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | libre-soc-bugs, mtnolan2640 |
| Priority: | --- | ||
| Version: | unspecified | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| NLnet milestone: | NLnet.2019.02.012 | total budget (EUR) for completion of task and all subtasks: | 0 |
| budget (EUR) for this task, excluding subtasks' budget: | 0 | parent task for budget allocation: | |
| child tasks for budget allocation: | The table of payments (in EUR) for this task; TOML format: | ||
| Bug Depends on: | |||
| Bug Blocks: | 186 | ||
|
Description
Luke Kenneth Casson Leighton
2020-03-18 12:11:55 GMT
Done: 474eb33c (In reply to Michael Nolan from comment #1) > Done: 474eb33c ah magic that was quick! :) oops i'd forgotten to put in the extra fields (length, priv yes/no), added them to the csv file and *then* discovered you'd learned that the key-names aren't unique. had a lovely time re-introducing the suffixes you added, michael :) (In reply to Luke Kenneth Casson Leighton from comment #3) > oops i'd forgotten to put in the extra fields (length, priv yes/no), added > them to the csv file and *then* discovered you'd learned that the key-names > aren't unique. had a lovely time re-introducing the suffixes you added, > michael :) Oh no! I'm thinking I could either make the enum value a namedstruct/SPR object that contains the length/privelages, or make a separate dict of structs/objects for that information. Thoughts on which way to go? Side note, why would they make them duplicate anyhow? That seems somewhat nutty. (In reply to Michael Nolan from comment #4) > Oh no! :) ehh it was fiiine > I'm thinking I could either make the enum value a namedstruct/SPR object > that contains the length/privelages, or make a separate dict of > structs/objects for that information. Thoughts on which way to go? hmmm... separate doesn't make a lot of sense, people might think they're somehow not related. > Side note, why would they make them duplicate anyhow? That seems somewhat > nutty. sigh i know, welcome to an "organically-grown" ISA. they should have put a prefix "H" or "S" in front of them, with "U" for "userspace". |