Hi,
Right now there's no way for user of osmo_a5(..)
to understand if particular cipher
(a5/3 for example) is supported or not.
Indeed ..
Attached patch adds simple return value to osmo_a5 to
fix that.
Of course I would rather see a5/3 included into mainline but in a meantime this patch
might be useful too :)
mmm, the "osmocom" usual way is to return 0 for success and a negative
error, in this case -ENOTSUP would be perfect.
true/false is more a C++ thing :p
Cheers,
Sylvain