On Sat, May 12, 2012 at 3:54 PM, Blue Swirl blauwirbel@gmail.com wrote:
On Sat, May 12, 2012 at 1:34 PM, Artyom Tarasenko atar4qemu@gmail.com wrote:
On Sat, May 12, 2012 at 1:42 PM, Blue Swirl blauwirbel@gmail.com wrote:
Based on Artyom's Sparc64 work (thanks a lot!), I added some minimal support for virtio-block and interrupt nodes.
Hey, that was fast! Does it mean your patches also allow booting from a virtio device?
No, only a warning for the unknown device is avoided and Linux can use the interrupts.
Making a simple driver does not look very difficult, here are some examples: http://fxr.watson.org/fxr/source/dev/virtio/block/virtio_blk.c http://fxr.watson.org/fxr/source/drivers/block/virtio_blk.c?v=linux-2.6 http://git.qemu.org/?p=seabios.git;a=blob;f=src/virtio-blk.c;h=194deaf98b41a...
Fair enough. On the other hand, if we implement it too soon, there will be less motivation in fixing the cmd646 emulation in qemu... ;-)
With these patches and QEMU HEAD, Linux can boot like Artyom describes in http://tyom.blogspot.de/2012_05_01_archive.html but without any manual OpenBIOS setup.
Blue Swirl (2): pci: identify virtio-scsi devices Sparc64: fix interrupt properties
drivers/ide.c | 2 ++ drivers/pc_serial.c | 3 +++ drivers/pci.c | 23 +++++++++++++++++++++++ drivers/pci_database.c | 19 ++++++++++++++++++- drivers/pci_database.h | 1 + include/drivers/pci.h | 3 +++ 6 files changed, 50 insertions(+), 1 deletion(-)
-- 1.7.10