Wip_write(), blocking/non-blocking?


This might be an obvious question, but i am not sure whether the wip_write() function blocks? I would think not, but i have never sent more then a max 20 bytes of data at one time so i would not have noticed any problems.

What i need to do is schedule packetized data from different places of my code, that i am assuming is runnign while the wip lib is doing its thing. Again, with a callback that the wip lib offers should mean a threaded kernel, but the events could be purely hardware driven?

Any info would be appreciated,


The function is non-blocking. You will receive WIP_CEV_WRITE event, when the WIP_COPT_SND_LOWAT level is reached.