Skip to content
Snippets Groups Projects
Commit 79ca44d8 authored by Eric Kooistra's avatar Eric Kooistra
Browse files

The in_siso.xon for upstream can remain on, because flush will handle out_siso.xon.

parent 41c7f396
Branches
No related tags found
No related merge requests found
...@@ -21,6 +21,11 @@ ...@@ -21,6 +21,11 @@
-- Purpose: Add flow XON-XOFF control by flushing frames -- Purpose: Add flow XON-XOFF control by flushing frames
-- Description: -- Description:
-- The in_siso.ready = out_siso.ready so passed on unchanged, to support
-- detailed output to input flow control per cycle. The in_siso.xon is
-- always '1', because the out_siso.xon is taken care of in this
-- dp_xonoff.vhd by flushing any in_sosi data when out_siso.xon = '0'.
--
-- When g_bypass=TRUE then the in and out are wired and the component is void. -- When g_bypass=TRUE then the in and out are wired and the component is void.
-- When g_bypass=FALSE then: -- When g_bypass=FALSE then:
-- The output is ON when flush='0'. -- The output is ON when flush='0'.
...@@ -70,7 +75,8 @@ BEGIN ...@@ -70,7 +75,8 @@ BEGIN
END GENERATE; END GENERATE;
no_bypass : IF g_bypass=FALSE GENERATE no_bypass : IF g_bypass=FALSE GENERATE
in_siso <= out_siso; -- pass on ready for detailed flow control per cycle in_siso.ready <= out_siso.ready; -- pass on ready for detailed flow control per cycle
in_siso.xon <= '1'; -- upstream can remain on, because flush will handle out_siso.xon
nxt_flush <= NOT out_siso.xon; -- use xon for flow control at frame level nxt_flush <= NOT out_siso.xon; -- use xon for flow control at frame level
p_clk: PROCESS(clk, rst) p_clk: PROCESS(clk, rst)
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment