Shabtay’s take 04/28 - Bring up mode not resolved and some areas in the spec need to be enhanced.

Committee agrees still active

5. Automatic flush-on-eom

    Cadence suggested that, on a pipe-by-pipe basis, that
    there be a means to enable automatic flush when eom is
    specified. The committee agreed that this would be
    useful.

    A new call is added  to specify automatic flush-on-eom
    mode for a pipe designated by a given handle. This mode
    configuration call is always initiated only on the C side
    (at initialization) for both input and output pipes:

    void dpi_pipe_set_eom_auto_flush(
      void *pipe_handle,  // input: pipe handle
svBit enabled );    // input: enable/disable

[Shabtay] Your suggestion using the handle is in line with our thinking and specifically it simplifies things quite a bit (hopefully addressing Duain’s concern expressed at the meeting).

We need to settle several issues:

1. The default setting during bring up. My recommendation is for eom_auto_flush to be enabled by default to insure correct functionality.

2. We need to provide control to the test to set this mode w/o relying on the proxy model. It can yet be done using handles that should be obtained by the test. This coincides with my comment embedded in 3.

3. Need to define: what are the synchronization semantics in eom_auto_flush mode wrt to buffer size? I would expect that HW side buffer full/empty will not yield an implicit flush in this mode. Only explicit call of flush will be honored in this mode. Is this how you see it?