Re: [greybus-dev] [PATCH 0/3] Add the Generic Netlink controller

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 03/26/2017 12:58 PM, Alexandre Bailon wrote:
Currently, only the es2 hd controller is supported, which restrict the
usage of greybus to few products.

This series intents to add a support of new hd controllers.
The driver doesn't support any hardware. Actually, the controller is just
a bridge between Greybus kernel and userspace. The real driver must be
implemented in userspace. This give the ability to support any kind of
transport layer (such as Bluetooth, WiFi, Ethernet).

The controller uses Generic Netlink. My original intent was to implement
a TCP/IP controller but it was very slow, unstable. In addition, some features
such as SVC or module discovery were to add to implement in kernel side.
With the generic netlink controller, we can easily add support of new
controller. It also helps to deal with all the project ARA legacy such as SVC.

I have started to implement an application which is able to emulate the SVC,
a module (like gbsim but only support control and loopback protcols),
TCP/IP, Bluetooth and UART. It is still under development but it was stable
enough to test this series. The application can found here:
https://github.com/anobli/gbridge

I'm not going to comment on the actual patch itself, but I do want to say that I'm very happy to see progress on making Gerybus generic to any transport.

--
Karim Yaghmour
CEO - Opersys inc. / www.opersys.com
http://twitter.com/karimyaghmour

_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel



[Index of Archives]     [Linux Driver Backports]     [DMA Engine]     [Linux GPIO]     [Linux SPI]     [Video for Linux]     [Linux USB Devel]     [Linux Coverity]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux