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
Currently, the handling of DFE tap weights, as AMI parameters, is awkward.
For instance, rather than being handled as an array, which would make expansion/contraction natural, they are, currently, handled singularly. Also, their ranges are hard-coded, rather than being available for user programming. Fix this.
The text was updated successfully, but these errors were encountered:
Currently, the handling of DFE tap weights, as AMI parameters, is awkward.
For instance, rather than being handled as an array, which would make expansion/contraction natural, they are, currently, handled singularly. Also, their ranges are hard-coded, rather than being available for user programming. Fix this.
The text was updated successfully, but these errors were encountered: