linux-kernel - Re: usb: musb: Scheduling of interrupt endpoints

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] [day] [month] [year] [list]

Message-ID: <20141223235045.GC32702@saruman>
Date:	Tue, 23 Dec 2014 17:50:45 -0600
From:	Felipe Balbi <balbi@...com>
To:	Carsten Behling <carsten.behling@...gerun.com>
CC:	<linux-usb@...r.kernel.org>, <balbi@...com>,
	<linux-kernel@...r.kernel.org>
Subject: Re: usb: musb: Scheduling of interrupt endpoints

Hi,

A: No.
Q: Should I include quotations after my reply?

On Tue, Dec 23, 2014 at 01:39:14PM -0600, Carsten Behling wrote:
> The following comment can be found in 'musb_schedule()':
> 
> '* REVISIT what we really want here is a regular schedule tree
>  * like e.g. OHCI uses.'
> 
> So I assume the best practice would be to make an implementation based
> on the code in in ohci-q.c. And it would be waste of time to port the
> old interrupt endpoint scheduling feature of TI.
> 
> Am I right?

Frankly, OHCI is a better example than TI's MUSB from 200 years ago,
that's correct :-)

cheers

-- 
balbi

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)