Hello! I would suggest reimplementing what is in sysdep/linux, maybe partly, maybe completely. The netlink api is implemented in sysdep/linux/netlink.c, the internal api between BIRD's Unix common code and netlink is not documented; I would suggest looking for non-static functions in netlink.c to see what is happening there. The internal API may change between versions without any notification. To prevent most of the related problems, it would be best if you could upstream your code. We could then take your usage into account and at least try to update your code when the API were to be changed. Maria On September 27, 2019 6:03:40 PM GMT+02:00, "Роман Вартичан" <roman_vartichan@mail.ru> wrote:
Hello! We are going to implement BIRD on HW ASIC platform. We try to understand how to untie bird from linux kernel and route its netlink or unix socket commands to ASIC driver (we carefully studied mail list, but did not find any info about this). We see that ioctl in BIRD will be deprecated in near future. Could you kindly clarify which is the best way of connecting of BIRD with proprietary hardware driver which runs in user space? -- Roman
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.