-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
getting a IoError but no clue what it means or how to fix #88
Comments
switched to using the propper blocking command |
I have no clue what I am doing wrong and #os-dev is not helping |
Where is that log line coming from? Have you tried attaching a debugger to see where it is hanging? |
it is the last line from qemu stderr (before it hangs*) with
(specifically the -trace virtio_mmio*) |
[stderr.txt] |
the last
2 calls to allocate DMA pages
and then hang... |
Well the |
so you mean Uart is somehow dying? |
but still no clue why stdio stops working |
okay stdio started working again. but now i have to use PciTransport to interact with VirtIO console |
Why do you need to use the PCI transport rather than MMIO? If your bootloader doesn't allocate PCI BARs, you can see https://github.com/rcore-os/virtio-drivers/blob/master/examples/aarch64/src/main.rs#L394 for an example of how you might do it. There's nothing VirtIO-specific about it though, it's just standard PCI initialisation. |
https://github.com/walksanatora/oc2kernel/blob/master/src/main.rs#L119-L136
is the virtio code
but yet it always returns with a IO error
you can see my qemu args in run.sh
The text was updated successfully, but these errors were encountered: