From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: G 3 <programmingkidx@gmail.com>
Cc: The OpenBIOS Mailinglist <openbios@openbios.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
"list@suse.de:PowerPC list:PowerPC" <qemu-ppc@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Add resolutions via the command-line
Date: Thu, 22 Sep 2016 07:53:54 +1000 [thread overview]
Message-ID: <1474494834.2857.145.camel@kernel.crashing.org> (raw)
In-Reply-To: <3E9DEC73-4C39-450A-9DAF-9EF17B0B0FB0@gmail.com>
On Wed, 2016-09-21 at 14:26 -0400, G 3 wrote:
>
> Nodes like chose, aliases, openprom are of class IOService. options
> is of class IODTNVRAM. It looks like this class has problems. I'm
> thinking since Alexander Graf did work in the mac_nvram.c file, he
> might know what is wrong.
What is wrong is purely that MacOS X limits how you do things on that
node. Have a look at the OS X kernel source :-) The implementation of
the support libraries to run NDRVs is all there (module
IOGraphicsFamily iirc).
> I found another way to access the options
> node in Mac OS X. Use this command: ioreg -c IODTNVRAM. It stops at
> the options node and prints this error message: "ioreg: error: can't
> obtain properties" in QEMU. On a real Power Mac the command prints
> all the properties of the options node just fine.
Correct, part of the problem is that I think we don't emulate the NVRAM
in a format that OS X understands, a problem for another day.
> I don't know about using binary. The way we do it now seems just fine.
ASCII parsing in a driver sucks.
> I just need to figure out how to write to the /chosen node from the
> QEMU command line. I found a function called OpenBIOS_set_var() in
> openbios_firmware_abi.h, but it would require an address to write to.
> So where do I find the address of the /chosen node....
No, you don't. Do as I said. Have OpenBIOS construct the list of
resolutions and put it in the node of the device itself.
Cheers,
Ben.
next prev parent reply other threads:[~2016-09-21 21:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-18 3:31 [Qemu-devel] [PATCH] Add resolutions via the command-line G 3
2016-09-19 6:24 ` Benjamin Herrenschmidt
2016-09-19 12:44 ` G 3
2016-09-19 22:44 ` Benjamin Herrenschmidt
2016-09-19 23:56 ` Alfonso Gamboa
2016-09-20 3:57 ` G 3
2016-09-20 4:01 ` G 3
2016-09-21 0:18 ` Benjamin Herrenschmidt
2016-09-21 0:35 ` G 3
2016-09-21 0:41 ` Benjamin Herrenschmidt
2016-09-21 2:54 ` G 3
2016-09-21 3:41 ` [Qemu-devel] [OpenBIOS] " Alfonso Gamboa
2016-09-21 9:01 ` [Qemu-devel] " Benjamin Herrenschmidt
2016-09-21 18:26 ` G 3
2016-09-21 21:53 ` Benjamin Herrenschmidt [this message]
2016-09-21 23:18 ` G 3
2016-09-22 0:05 ` Benjamin Herrenschmidt
2016-09-23 14:09 ` [Qemu-devel] [OpenBIOS] " Mark Cave-Ayland
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=1474494834.2857.145.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=openbios@openbios.org \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.