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 device map addresses are set as
Reserved(16).HubIdx(8).DevIdx(8)
However, it might make more sense to redefine those as HubIdx(16).DevIdx(16) even if not all implementations are able to use the full address range (for example, ONIX current implementation is limited to 8bit dev indexes).
To retain compatibility across devices, the special device IDs could be defined as such:
-Invalid device: DevIdx is all binary ones
-HUB control device: DevIdx is Invalid device - 1 (all ones except LSB)
A specific implementation able only to use a subset of the ranges would perform automatic bit expansion/trimming when translating addresses to the 32-bit interface defined by the standard.
The text was updated successfully, but these errors were encountered:
Limits on max devices per hub and max hubs per host should be informed to the software layer through the capabilities registers suggested on #6
The main issue is, this breaks compatibility with existing hardware, as it sends the map in the rsv.rsv.hub.dev format, but I believe it's worth it for future-proofing the spec. We could require a fw update to comply with the spec or we could create a "legacy" version of the onidrivers that handle this case, for existing hardware. A discussion is warranted.
Ported from jonnew/ONI#8
Original text:
The text was updated successfully, but these errors were encountered: