How to implement custom isConnected logic for ports #2605
Replies: 1 comment 1 reply
-
Also note: the buffer copy is likely not what you expect. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to wrap my head around the ByteStreamDriverModel in a project that I've taken over.
Here's some background here's my setup
I have a transmitter module with some fpp like this
instances.fpp
topology.fpp
ByteStreamSendSplitter.cpp
bssOutB is connected to the transmitter interface and I would like to avoid calling into
bssOutB_out
if the transmitter has not been initialized.I know that the
isConnected_bssOutB_OutputPort
ultimately calls into something like this:which ultimately just checks whether
OutputByteStreamReadyPort::addCallPort
has been called.Since I've implemented ports ready and queue based on the ByteStreamDriverModel is there some way I can leverage this in my implementation of transmitterIF similar to the
Drv::SendStatus queue_handler
?Beta Was this translation helpful? Give feedback.
All reactions