Jan Kiszka wrote:
...
I just noticed that the user API (rtnet.h) is unfortunately lacking some
macro to build a socket priority value from both parameter, will fix
this before the next release.


For the files and as preliminary documentation:

I just tried to clarify the user API (see latest SVN version). To set custom values for the so-called transmission parameters, use the following scheme in your applications from now on:

        unsigned int params;
        ...
        params = SOCK_XMIT_PARAMS(<priority>, <channel>);
        ioctl_rt(socket, RTNET_RTIOC_XMITPARAMS, &params);

Hope this improves the comprehensibility a bit. Legacy code can still use RTNET_RTIOC_PRIORITY as it maps directly on RTNET_RTIOC_XMITPARAMS (internal argument encoding hasn't changed in any way).

Jan


------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users

Reply via email to