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
There are a number of objects that are provided by ipgen IPs that are independent of any parameterization, and are used by generic IPs for ports types. This requires the generic IPs to use the virtual interface to ipgen IP packages, which is troublesome.
In otp_ctrl this was resolved by splitting all top specific items objects out of the otp_ctrl_pkg, and moved to a template otp_ctrl_top_specific_pkg. A solution of this sort can be used for other ipgen IPs as well.
It is equally sensible to move the declarations of the generic objects to the receiving IP's pkg, if there is a single receiver. A better solution could be to place these generic objects to a better location, perhaps under hw/common.
The text was updated successfully, but these errors were encountered:
Description
There are a number of objects that are provided by ipgen IPs that are independent of any parameterization, and are used by generic IPs for ports types. This requires the generic IPs to use the virtual interface to ipgen IP packages, which is troublesome.
In otp_ctrl this was resolved by splitting all top specific items objects out of the otp_ctrl_pkg, and moved to a template otp_ctrl_top_specific_pkg. A solution of this sort can be used for other ipgen IPs as well.
It is equally sensible to move the declarations of the generic objects to the receiving IP's pkg, if there is a single receiver. A better solution could be to place these generic objects to a better location, perhaps under hw/common.
The text was updated successfully, but these errors were encountered: