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
My idea for this is that you can define HiSpeed inputs that are assigned to memory ranges (in the FPGA HiSpeed addressing space), and then those HiSpeed links can be connected to internal gates. A set of converter gates to convert from HiSpeed to Number and back.
HiSpeed links work weird however, and I'm not sure the current "type" system can handle it. Some devices have the HiSpeed link (at least the wire port dedicated to it) on the input, and others on the output.
Maybe some special new 'pseudo' type? In theory every gate has "HiSpeed", even if they don't implement WriteCell and ReadCell, so maybe it could be a special link between 2 gates? HiSpeed functionality is already pretty advanced, so it wouldn't matter too much if using it is slightly complex.
It should be noted that wirelinks already work (HiSpeed write and read gates), but 'legacy' HiSpeed gates use different input/output conventions.
Currently gates that exclusively have HiSpeed behaviour are 'banned'/hidden (String to Memory and the reverse)
The text was updated successfully, but these errors were encountered:
My idea for this is that you can define HiSpeed inputs that are assigned to memory ranges (in the FPGA HiSpeed addressing space), and then those HiSpeed links can be connected to internal gates. A set of converter gates to convert from HiSpeed to Number and back.
HiSpeed links work weird however, and I'm not sure the current "type" system can handle it. Some devices have the HiSpeed link (at least the wire port dedicated to it) on the input, and others on the output.
Maybe some special new 'pseudo' type? In theory every gate has "HiSpeed", even if they don't implement WriteCell and ReadCell, so maybe it could be a special link between 2 gates? HiSpeed functionality is already pretty advanced, so it wouldn't matter too much if using it is slightly complex.
It should be noted that wirelinks already work (HiSpeed write and read gates), but 'legacy' HiSpeed gates use different input/output conventions.
Currently gates that exclusively have HiSpeed behaviour are 'banned'/hidden (String to Memory and the reverse)
The text was updated successfully, but these errors were encountered: