nikvoid

Well, I don't see a reason to create device driver trait. I have updated rp/usb_host_hid_keyboard example with hub usage, as you can see, user can just try all drivers with...

> The main purpose is to create a common interface for drivers such that a user can easily re-use them & create a common initialization sequence. This allows (for example)...

So, if I finally understand correctly, handler trait will be something like a middleware between device driver and usb host driver (or just device driver that stands directly over bus...

> Hmm I was hoping this could be done in the Channel itself to avoid complicating the trait & implementation; e.g. give a Ref, and a it's own index, which...

RP2040 also has hardware timeouts, but they are apparently too strict for slow devices (like that usb hub I first encountered this issue with). What about adding method to bus...

What about multiple connected devices (via usb hub)? I see that now there is only method for changing current device address in user-facing UsbHost struct.

Given that there are things like low-speed preamble, host indeed needs to handle hub specially. I want host support on rp2040 to control 2 usb devices, so I probably will...

Yes. I made some of requested changes, but not sure what to do about kernel patch directory. I cannot test patches on other boards, so do I need to rename...

I just tried all kernel branches and only vendor booted. I did not check SD card so it's surprise for me that it is not working. Maybe some devicetree requires...

I missed this PR and made [similar](https://github.com/nikvoid/smoltcp/tree/ether-socket) thing, so... +1 for raw ethernet sockets