Re: [PATCH 00/10] MA USB drivers cover letter
[added linux-...@vger.kernel.org Cc] Stephanie Wallick stephanie.s.wall...@intel.com writes: Media Agnostic (MA) USB enables the USB protocol to be used over a wide range of physical media. MA USB is a relatively new protocol and is currently unsupported in the Linux kernel. This patch set adds the following drivers with the following capabilities: 1) MA USB Host: - provides functionality of a USB Host Controller. - implements MA USB protocol for a MA USB host. - provides MA USB packet transport over TCP 2) MA USB Device: - provides functionality of a USB Device Controller. - implements MA USB protocol for a MA USB device. - provides MA USB packet transport over TCP Nice. But don't you think this deserves the attention of the linux-usb mailing list? Yes, Greg's attention is of course good to have too :-) But I believe this is of interest to more people, who might not read everything on linux-kernel. Has there been any thought/discussion about the relationship to the existing usbip drivers, which just moved out of staging? Is a usbip userspace compatibility layer feasible sometime in the future? Bjørn ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH 00/10] MA USB drivers cover letter
On Tue, Nov 04, 2014 at 10:00:32AM +0100, Bjørn Mork wrote: [added linux-...@vger.kernel.org Cc] Nice. But don't you think this deserves the attention of the linux-usb mailing list? Yes, Greg's attention is of course good to have too :-) But I believe this is of interest to more people, who might not read everything on linux-kernel. This is probably more relevant/interesting to the people on linux-usb. Since we were trying to get this driver into staging, we thought linux-kernel was the right place to send the patches. We can send the next set out to linux-usb as well. Has there been any thought/discussion about the relationship to the existing usbip drivers, which just moved out of staging? Is a usbip userspace compatibility layer feasible sometime in the future? That discussion hasn't happened. usbip has a different protocol than MA USB, so much of the code cannot be reused. I just briefly looked into the userspace code for usbip. It looks like the userspace compatibility layer is just a utility for establishing the TCP connection between the host and device choosing what devices to connect, correct? We have a similar utility (see patch 9/10) which could probably be replaced by the usbip userspace utilities. Bjørn -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH 00/10] MA USB drivers cover letter
On Tue, Nov 04, 2014 at 10:00:32AM +0100, Bjørn Mork wrote: [added linux-...@vger.kernel.org Cc] Nice. But don't you think this deserves the attention of the linux-usb mailing list? Yes, Greg's attention is of course good to have too :-) But I believe this is of interest to more people, who might not read everything on linux-kernel. This is probably more relevant/interesting to the people on linux-usb. Since we were trying to get this driver into staging, we thought linux-kernel was the right place to send the patches. We can send the next set out to linux-usb as well. Has there been any thought/discussion about the relationship to the existing usbip drivers, which just moved out of staging? Is a usbip userspace compatibility layer feasible sometime in the future? That discussion hasn't happened. usbip has a different protocol than MA USB, so much of the code cannot be reused. I just briefly looked into the userspace code for usbip. It looks like the userspace compatibility layer is just a utility for establishing the TCP connection between the host and device choosing what devices to connect, correct? We have a similar utility (see patch 9/10) which could probably be replaced by the usbip userspace utilities. Bjørn -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH 00/10] MA USB drivers cover letter
[with a valid Message-ID] On Tue, Nov 04, 2014 at 10:00:32AM +0100, Bjørn Mork wrote: [added linux-...@vger.kernel.org Cc] Stephanie Wallick stephanie.s.wall...@intel.com writes: Media Agnostic (MA) USB enables the USB protocol to be used over a wide range of physical media. MA USB is a relatively new protocol and is currently unsupported in the Linux kernel. This patch set adds the following drivers with the following capabilities: 1) MA USB Host: - provides functionality of a USB Host Controller. - implements MA USB protocol for a MA USB host. - provides MA USB packet transport over TCP 2) MA USB Device: - provides functionality of a USB Device Controller. - implements MA USB protocol for a MA USB device. - provides MA USB packet transport over TCP Nice. But don't you think this deserves the attention of the linux-usb mailing list? Yes, Greg's attention is of course good to have too :-) But I believe this is of interest to more people, who might not read everything on linux-kernel. This is probably more relevant/interesting to the people on linux-usb. Since we were trying to get this driver into staging, we thought linux-kernel was the right place to send the patches. We can send the next set out to linux-usb as well. Has there been any thought/discussion about the relationship to the existing usbip drivers, which just moved out of staging? Is a usbip userspace compatibility layer feasible sometime in the future? That discussion hasn't happened. usbip has a different protocol than MA USB, so much of the code cannot be reused. I just briefly looked into the userspace code for usbip. It looks like the userspace compatibility layer is just a utility for establishing the TCP connection between the host and device choosing what devices to connect, correct? We have a similar utility (see patch 9/10) which could probably be replaced by the usbip userspace utilities. Thanks, Sean ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
[PATCH 00/10] MA USB drivers cover letter
Media Agnostic (MA) USB enables the USB protocol to be used over a wide range of physical media. MA USB is a relatively new protocol and is currently unsupported in the Linux kernel. This patch set adds the following drivers with the following capabilities: 1) MA USB Host: - provides functionality of a USB Host Controller. - implements MA USB protocol for a MA USB host. - provides MA USB packet transport over TCP 2) MA USB Device: - provides functionality of a USB Device Controller. - implements MA USB protocol for a MA USB device. - provides MA USB packet transport over TCP Driver overview: The MA USB Host and Device stacks each consists of two drivers. The first driver is the Media Agnostic (MA) layer, which interfaces with the existing USB stack and implements the MA USB protocol as defined in the MA USB Specification Release 1.0. The second driver is the Media Specific (MS) layer. The MS layer interfaces with the network stack to send and receive MA USB packets via TCP. When an MA USB driver is loaded, the MA layer loads first and registers itself as a USB host controller with the USB Core. The MS layer then loads and registers itself with the MA layer. Once the MS layer is registered, the MA layer initiates creation of a communication channel for managment/control packets. In the case of the MA USB host, the driver the opens a TCP socket and polls periodically for a device. In the case of the MA USB device, the driver identifies the MA USB host by IP address, then looks for and binds to the open TCP socket of the MA USB host. When a connection event is initiated, the MA USB host notifies the USB core and normal USB enumeration and configuration results with each respective USB packet translated into its MA USB equivalent. Tools: 1) various scripts are included to help load and unload the MA USB host and device drivers. 2) a utility is included to help connect, disconnect, and test the MA USB host and device drivers. References: MA USB Specification v1.0 available at www.usb.org/developers/docs/devclass_docs/ Stephanie Wallick (10): added media agnostic (MA) USB HCD driver added media agnostic (MA) USB HCD roothubs added media agnostic (MA) data structures and handling added media agnostic (MA) USB packet handling added media specific (MS) TCP drivers added media agnostic (MA) UDC added media agnostic (MA) USB management packet handling added media agnostic (MA) USB data packet handling added tools for building/loading media agnostic (MA) USB drivers added kernel build, configuration, and TODO files drivers/staging/Kconfig|2 + drivers/staging/Makefile |1 + drivers/staging/mausb/Kconfig | 16 + drivers/staging/mausb/Makefile |3 + drivers/staging/mausb/TODO | 14 + drivers/staging/mausb/drivers/Kconfig | 34 + drivers/staging/mausb/drivers/Makefile | 20 + drivers/staging/mausb/drivers/mausb_const.h| 109 ++ drivers/staging/mausb/drivers/mausb_hcd.c | 970 + drivers/staging/mausb/drivers/mausb_hcd.h | 171 +++ drivers/staging/mausb/drivers/mausb_hub.c | 851 +++ drivers/staging/mausb/drivers/mausb_hub.h | 128 ++ drivers/staging/mausb/drivers/mausb_ioctl.c| 373 + drivers/staging/mausb/drivers/mausb_ioctl.h| 99 ++ drivers/staging/mausb/drivers/mausb_mem-host.c | 404 ++ drivers/staging/mausb/drivers/mausb_mem-host.h | 74 + drivers/staging/mausb/drivers/mausb_mem.c | 844 +++ drivers/staging/mausb/drivers/mausb_mem.h | 509 +++ drivers/staging/mausb/drivers/mausb_mgmt.c | 888 drivers/staging/mausb/drivers/mausb_mgmt.h | 90 ++ drivers/staging/mausb/drivers/mausb_msapi.c| 110 ++ drivers/staging/mausb/drivers/mausb_msapi.h| 232 +++ drivers/staging/mausb/drivers/mausb_pkt.c | 1038 ++ drivers/staging/mausb/drivers/mausb_pkt.h | 914 drivers/staging/mausb/drivers/mausb_state.h| 184 +++ drivers/staging/mausb/drivers/mausb_tcp-device.c | 147 ++ drivers/staging/mausb/drivers/mausb_tcp-host.c | 144 ++ drivers/staging/mausb/drivers/mausb_tcp.c | 446 ++ drivers/staging/mausb/drivers/mausb_tcp.h | 129 ++ drivers/staging/mausb/drivers/mausb_tx-device.c| 847 +++ drivers/staging/mausb/drivers/mausb_tx-host.c | 1211 drivers/staging/mausb/drivers/mausb_tx.c | 318 + drivers/staging/mausb/drivers/mausb_tx.h | 129 ++ drivers/staging/mausb/drivers/mausb_udc.c | 1488 drivers/staging/mausb/drivers/mausb_udc.h | 147 ++ .../staging/mausb/scripts/build_load_connect.sh| 69 +
