You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are multiple controllers however the one M1N1 expects is a (mostly?) standard DWC3 implementation. Luckily QEMU already supports this device and we don't have to emulate it ourselves, however it must be initialized into the emulated machine, entered into the ADT configuration, and the code in M1N1 assumes a DART is present so it won't be much use until that portion is finished.
The benefits (besides it needed to exist for completeness) are likely to be:
Faster proxy communications (although now with loading directly it's not such a huge issue, also compressed write is fairly fast)
QEMU code can take advantage of M1N1's support for multiple UART channels tunneled over USB
The above point is crucial for potentially emulating M1N1's hypervisor mode (although that's not all that useful for QEMU)
There are multiple controllers however the one M1N1 expects is a (mostly?) standard DWC3 implementation. Luckily QEMU already supports this device and we don't have to emulate it ourselves, however it must be initialized into the emulated machine, entered into the ADT configuration, and the code in M1N1 assumes a DART is present so it won't be much use until that portion is finished.
The benefits (besides it needed to exist for completeness) are likely to be:
Tracking for completion
The text was updated successfully, but these errors were encountered: