Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
libtizonia: Deprecate tiz_krn_select and friends #32
'tiz_krn_select' was being used to learn which ports had buffers available to be "claimed" by the processor object. Then if buffers were available to be claimed, 'tiz_krn_claim_buffer' had to be used to actually receive them.
The dual api workflow can in practice be simplified to use one api only, that is using 'tiz_krn_claim_buffer' plus a check to see if this function returned a non-null header (previously it was guaranteed non-null pointer since 'tiz_krn_select' was being used prior to 'tiz_krn_claim_buffer' ).
'tiz_krn_select' won't be deleted just yet. Further analysis needed to understand if there is a use case for this api.