-
Notifications
You must be signed in to change notification settings - Fork 51
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
Inconsistency in Parameters #171
Comments
dansmathers
added a commit
that referenced
this issue
Nov 3, 2022
pull for issue #96 #158 #171 #226 instead of defining number of bits implemented in clicintattr.mode, define parameters so that software knows valid values to program for clicintctl and any clicintattr.mode side effects. this allows for additional methods of clicintattr.mode implementations while maintaining compatibility with previously defined method Signed-off-by: Dan Smathers <[email protected]>
dansmathers
added a commit
that referenced
this issue
Feb 14, 2023
pull for issue #96 #158 #171 #226 instead of defining number of bits implemented in clicintattr.mode, define parameters so that software knows valid values to program for clicintctl and any clicintattr.mode side effects. this allows for additional methods of clicintattr.mode implementations while maintaining compatibility with previously defined method Signed-off-by: Dan Smathers <[email protected]>
Closed
dansmathers
added a commit
that referenced
this issue
Feb 2, 2024
Separated software interface from CLIC parameters that describe the number of implemented bits. As issues #158, #171, #226, implementations may wish to optimize clicintattr.mode/clicintctl behavior. This change adds a parameter that specifies the WARL values of clicintctl so implementations have more freedom in how they implement clicintattr.mode/clicintctl and do not have to depend on CLICINTCTLBITS restrictions. Signed-off-by: Dan Smathers <[email protected]>
closed bvy #369 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Chapter 6 has a parameter, CLICCFGLBITS that says it's 0-CEIL(lg2(CLICLEVELS)) and that it's the number of bits implemented for cliccfg.nlbits. This ties cliccfg.nlbits and the number of levels available. But at the Sept 14 meeting, we said that nlbits could be hardwired to 0 or 8 and that 8 allowed any number of levels, not just 256. If the Sept 14 discussion is correct, this parameter needs updating.
The text was updated successfully, but these errors were encountered: