Replies: 1 comment 3 replies
-
My understanding that it is implemented with a FIFO. This means that the application does not need to be aware of packet-level transfers. In other words, an application cannot handle packet-level transfers. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What is the correct way to acknowledge a bulk IN request with a zero length response (to signal that no data is available)?
Right now, this seems to be prevented by
vendor_device.c::maybe_transmit()
, which only starts the transfer if there is data in the FIFO (count > 0
):tinyusb/src/class/vendor/vendor_device.c
Lines 109 to 120 in 81fa996
I came up with thierer@dfb2ecc, which seems to do what I want, but maybe there's a better way to achieve this - without modifying tinusb or reimplementing most of
vendor_device
?Beta Was this translation helpful? Give feedback.
All reactions