> Note, ideally we would already filter them at the "kernel" netlink source
That's possible because that android driver doesn't use libudev to get these events, but sets up its own netlink socket. We really don't want to see these events anywhere else.
> Note, ideally we would already filter them at the "kernel" netlink source
That's possible because that android driver doesn't use libudev to get these events, but sets up its own netlink socket. We really don't want to see these events anywhere else.