On Wed, 21 Nov 2012, Sarah Sharp wrote:
> > The USB spec already provides for this, to some extent. Altsetting 0
> > is not supposed to contain any isochronous endpoints and should have
> > minimal bandwidth requirements. Drivers ought to switch back to
> > altsetting 0 when they are not using t
On Mon, Nov 19, 2012 at 05:31:57PM -0500, Alan Stern wrote:
> On Mon, 19 Nov 2012, Sarah Sharp wrote:
>
> > On Mon, Nov 19, 2012 at 10:50:32AM -0500, Alan Stern wrote:
> > Perhaps we should only update the schedule after the configuration or
> > alt setting is installed? We could force a driver t
On Monday 19 November 2012 17:31:57 Alan Stern wrote:
> On Mon, 19 Nov 2012, Sarah Sharp wrote:
>
> > On Mon, Nov 19, 2012 at 10:50:32AM -0500, Alan Stern wrote:
> > Your original idea of storing the state and reverting it does seem
> > feasible. However, I like the idea of doing one big fix to
On Mon, 19 Nov 2012, Sarah Sharp wrote:
> On Mon, Nov 19, 2012 at 10:50:32AM -0500, Alan Stern wrote:
> > Sarah:
> >
> > Improving the bandwidth management in ehci-hcd will require a lot of
> > changes, and some difficult issues have come up. Maybe you can suggest
> > a good way to approach th
On Mon, Nov 19, 2012 at 10:50:32AM -0500, Alan Stern wrote:
> Sarah:
>
> Improving the bandwidth management in ehci-hcd will require a lot of
> changes, and some difficult issues have come up. Maybe you can suggest
> a good way to approach them.
>
> The first problem is that when a Set-Interfa
Sarah:
Improving the bandwidth management in ehci-hcd will require a lot of
changes, and some difficult issues have come up. Maybe you can suggest
a good way to approach them.
The first problem is that when a Set-Interface request fails, the HCD
needs to revert to the previous schedule settin