Alexander Aring wrote:
> An another Question is, is the errno available up to userspace? I mean
> the device need to transfer this errno up to some libnl error handling code
> which figure out a error string for the specific errno, so lowpan-tools
> can print it out to stderr.

iz* uses nl_perror. The path should be as follows:

- the kernel error code is returned by netlink_ack "as is"

- libnl/lib/error.c:nl_syserr2nlerr converts errno (E*) error codes
  to netlink error codes (NLE_*)

- libnl/lib/error.c:nl_perror then prints the string, according to
  libnl/lib/error.c:errmsg

EINVAL becomes NLE_INVAL becomes
Receive failed: Invalid input data or parameter

ENOSYS becomes NLE_FAILURE (catchall) becomes
Receive failed: Unspecific failure

EOPNOTSUPP becomes NLE_OPNOTSUPP becomes
Operation not supported

The list of errors can be seen here:
https://github.com/tgraf/libnl/blob/master/lib/error.c

- Werner

------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete 
for recognition, cash, and the chance to get your game on Steam. 
$5K grand prize plus 10 genre and skill prizes. Submit your demo 
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
_______________________________________________
Linux-zigbee-devel mailing list
Linux-zigbee-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel

Reply via email to