From: "Blue Swirl" <blauwirbel@gmail.com>
To: Laurent Vivier <Laurent@lvivier.info>,
Aurelien Jarno <aurelien@aurel32.net>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH] PPC: Support flags -boot, -uuid and -kernel using fw_cfg
Date: Sun, 21 Dec 2008 21:46:10 +0200 [thread overview]
Message-ID: <f43fc5580812211146w3f55bf04ya77a8c792aebf356@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
Hi,
These two patches (Qemu/OpenBIOS) add support for giving OpenBIOS/PPC
a boot device with -boot command line flag, use a UUID (print only)
and call a preloaded kernel. These are passed from Qemu to OpenBIOS
using the firmware configuration device and NVRAM.
Using the -boot switch works, but I can't boot anything yet so it's
not very well tested. UUID works, but it's not added to the device
tree. Kernel crashes after the first instruction, maybe the memory
size probe corrupts memory.
>> =============================================================
>> OpenBIOS 1.0RC1 [Dec 21 2008 11:55]
>> Configuration device id QEMU version 1 machine id 2
>> CPUs: 1
>> UUID: 12345678-1234-abcd-7654-123456789abc
>> Initializing PCI devices...
>> 0:0.0 - 1057:2 - /pci/pci - pci
>> 0:1.0 - 1234:1111 - /pci/QEMU,VGA - QEMU,VGA
>> 0:2.0 - 10ec:8029 - /pci/NE2000 - NE2000
>> 0:3.0 - 1095:646 - /pci/pci-ata - pci-ata
>> ata-1: [io ports 0x100-0x107,0x182]
>> drive1 [ATAPI cdrom]: QEMU DVD-ROM
>> ata-2: [io ports 0x200-0x207,0x282]
>> 0:4.0 - 106b:17 - /pci/mac-io - mac-io
No disk found.
>> [ppc] Kernel already loaded (0x01000000 + 0x003cadc8)
[-- Attachment #2: q_ppc_use_fw_cfg.diff --]
[-- Type: plain/text, Size: 1238 bytes --]
[-- Attachment #3: o_ppc_use_fw_cfg.diff --]
[-- Type: plain/text, Size: 4953 bytes --]
next reply other threads:[~2008-12-21 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 19:46 Blue Swirl [this message]
2008-12-21 20:16 ` [Qemu-devel] [PATCH] PPC: Support flags -boot, -uuid and -kernel using fw_cfg Laurent Vivier
2008-12-21 20:25 ` Blue Swirl
2008-12-21 21:46 ` Laurent Vivier
2008-12-21 21:44 ` Blue Swirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f43fc5580812211146w3f55bf04ya77a8c792aebf356@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=Laurent@lvivier.info \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).