The interrupt transfer schedule is arranged in a sparse tree, just like OHCI.A key difference is that OHCI implements a "best fit" scheduling policy,while this implements "first fit" for EHCI. (There's no load balancing;it's not really needed in most users' configurations.)

There's also logic here to handle "high bandwidth" transfers, guaranteedstreaming of from 8-24 KB of data per millisecond.

Also includes some related cleanups for descheduling interrupt transfers.Those will probably be split into a separate patch.

Against 2.6.10-rc3-bk5 ... this hasn't recently been tested much, but themain old bug seems to be gone so it shouldn't make too much trouble.