linux-kernel - RE: [PATCH/RFC 5/5] usb: Add support for streams alloc/dealloc to devio.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 30 Jun 2011 21:41:40 +0300
From:	"Tanya Brokhman" <tlinder@...eaurora.org>
To:	"'Sarah Sharp'" <sarah.a.sharp@...ux.intel.com>
Cc:	<greg@...ah.com>, <linux-usb@...r.kernel.org>,
	<linux-arm-msm@...r.kernel.org>, <balbi@...com>,
	<ablay@...eaurora.org>,
	"'open list'" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH/RFC 5/5] usb: Add support for streams alloc/dealloc to devio.c

Hi Sarah,

> Will this patch be used to create a userspace UAS driver, or are you
> envisioning other ways userspace might use streams?  I ask because I
> can't think of another usage of streams in currently available devices.
> 

No, this patch isn't used for UAS driver. It's used by us only for several
tests that we implemented in the user space unittests framework we released
with this patch. We used this FW to test our superspeed support
implementation and the UAS gadget driver. It's a userspace application that
uses Google test and libusb.
That's the only reason we need this patch at the moment.
But in any case, due to the comments we got on it from Greg/Alan/Felipe this
patch is rewritten at the moment by its original author Amit Blay
(ablay@...eaurora.org). He'll post a new version of it once he's done.

Thanks,
Tanya Brokhman
---
Sent by an consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/