Kacper Słomiński

You can check the bus and device numbers with `lsusb`, then check what controller the device belongs to with `lsusb -t`

> Were you using multiboot by any chance? We use multiboot 1/2.

`lsusb -v` output (including report descriptors): https://uwu.foundation/9qFVtZo.txt

> @qookei I presume this is (largely) superseeded by #421? If so, we can close this. As far as I can tell they are unrelated. This implements SIGSTOP/CONT, while #421...

Personally I'd prefer if we merged PCI and system bus devices into one thing in the hw protocol. We could for example used named memory regions for PCI BARs and...

#390 does not help here. As far as I can see, this is triggered due to the response for the `PT_READ_ENTRIES` request being too large.

Oh apologies, I looked at your response on my phone, but forgot to respond later. With the skeleton generated by `pelican-quickstart`, the following plugin to generate HTML5 output: https://gist.github.com/qookei/c302b95ff716257b424e877f3dceb502 (more...

See managarm/frigg#62 for the parser implementation.

> Then the driver responsible can unmask it when it's ready. For PCI devices, it makes sense to do this in `enableIrq()`, but for non-PCI devices I'm not sure. Once...

I feel like the root cause of this is actually related to #175