On Fri, May 05, 2017 at 11:38:38AM +0200, Alexandre Bailon wrote:
On 04/18/2017 01:59 PM, Greg KH wrote:
On Sun, Mar 26, 2017 at 06:58:24PM +0200, Alexandre Bailon wrote:
Currently, the only hd controller supported by Greybus is the es2 controller which only support is mainly a bridge between USB and UniPro. In order to use Greybus on devices that do not support UniPro, add a the Greybus netlink hd controller.
By using Generic Netlink, userspace can act as a bridge between Greybus and any kind of bus supported by the platform (e.g. Bluetooth). In addition, this add an easy way to implement some component such as SVC which is required by Greybus though it may not be available on every platforms.
Very cool stuff, any hints on how to use this over netlink? Will the network developers get mad at this as an abuse of the transport?
Currently, I haven't documented anything. The only hint I can gives is to take a look https://github.com/anobli/gbridge/blob/master/controllers/gb_netlink.c, which is source code of gbridge that deals with generic netlink. I think I should have a least documented the data format generic netlink operations.
I'm not sure to understand your point about the abuse of the transport.
I am not familiar if the network developers like people adding new users of the transport. For some reason I didn't think they did, but I might be totally wrong and thinking of something else.
To compile this code as a module, chose M here: the modulewill be called gb-netlink.koDoesn't this need to depend on netlink to build properly?
I think so. I will check.
Thanks, I'll wait for your new versions :)
greg k-h