On 13.06.2016 12:52, Martin Pieuchot wrote:
On 10/06/16(Fri) 21:09, Mark Kettenis wrote:
Date: Fri, 10 Jun 2016 17:20:18 +0100
From: Stuart Henderson <s...@spacehopper.org>
On 2016/06/10 16:05, Mark Kettenis wrote:
In any case this is something we can figure out once the code hits the
tree. Unless mpi@ is still unhappy with the way the driver performs
ioctls, I think we should get the driver bits into the tree such that
we can work on fixing the remaining issues with it.
Agreed.
Did people notice the uhub.c part? Any concerns with that?
Yes, that is a separate issue as well. And should therefore be a
separate commit. It doesn't seem unreasonable to me to retry once
before giving up. But this is another area where mpi@ should have the
final say.
The printf doesn't trigger on my Sierra Wireless EM7345 (which really
is an Intel XMM 7160 in disguise).
I'm worried that this hack alone won't help us improve the currently
outdated code to initialize USB devices as it will work around other
bugs.
That said I think it's a good starting point to improve things, so I
gave Gerhard my ok.
Thanks for the ok, the umb(4) driver has been committed now.
But because of the controversy, I did exclude the uhub.c part.
I would suggest to wait and see what other users of umb(4) experience.
If I'm the only one seeing this strange behavior, we might just forget
about it. But if others suffer from it, too, then I'll submit a separate
patch for it.
Gerhard
