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  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:	Tue, 6 Jan 2015 12:39:55 +0530
From:	sundeep subbaraya <>
To:	"" <>
Cc:	Paul Zimmerman <>,
	"" <>,
	"" <>
Subject: Re: query on DWC3


On Mon, Dec 22, 2014 at 9:42 PM, Felipe Balbi <> wrote:
> Hi again,
> On Mon, Dec 22, 2014 at 10:11:23AM -0600, Felipe Balbi wrote:
>> (please don't top-post)


>> On Sun, Dec 14, 2014 at 08:39:18AM +0530, sundeep subbaraya wrote:
>> > Hi Paul,
>> >
>> > As per my understanding, for BULK OUT we do queue a request with 512
>> > bytes length since we do not
>> sometimes we _do_ know the size. In case of Mass Storage, we _know_ that
>> the first bulk out transfer will be 31-bytes (CBW), if we were to start
>> a 31-byte transfer, we would't receive anything.
>> > know the length of the transfer Host is going to send. For Control OUT
>> > we know the length in wLength of
>> > Setup packet, hence I assumed there is no difference in programming
>> > model of Control IN and OUT.
>> there is _no_ difference. It's just that it was agreed that for anything
>> other than control ep, the function drivers would take care of it. See
>> the uses of quirk_ep_out_aligned_size.

got it..:)

> btw, why are you reimplementing the driver when there's a perfectly good
> driver to use in mainline kernel ?

I am writing a bare metal driver and it didn't work without alignment
check mentioned above.

> --
> balbi

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists