From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: G 3 <programmingkidx@gmail.com>,
The OpenBIOS Mailinglist <openbios@openbios.org>
Cc: 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: Wed, 21 Sep 2016 19:01:45 +1000 [thread overview]
Message-ID: <1474448505.2857.116.camel@kernel.crashing.org> (raw)
In-Reply-To: <BACE3833-EEA7-4D95-94E3-BC1447D5B0AB@gmail.com>
On Tue, 2016-09-20 at 22:54 -0400, G 3 wrote:
> You really want to remove the included list of resolutions? I was
> thinking about adding a lot more built-in resolutions in another
> patch. A built-in list is very convenient.
I mean remove it from the driver and put it in OpenBIOS instead.
Ie. have openbios build the resolution list from the combination of what you put
in the options node and its own built-in list.
> As for the options node problem. We need a way to add resolutions
> from the command-line for a Mac OS X guest. Using "-prom-env" isn't
> an option because of some unknown bug.
Maybe, I can look into it later, but the above would fix it nicely.
> I suppose it is possible to
> fix this bug - if it is a bug. Another idea I have is to add a
> completely different command-line option to QEMU just for
> resolutions. The user could specify resolutions like this: -video-
> resolutions 640x480,1024x768,1280x700.... This feature could place
> the list of resolutions inside a property of the VGA device node. I
> am betting the VGA driver could access this node and parse the list
> of resolutions. So this: qemu -video-resolutions ---> OpenBIOS VGA
> device node ---> VGA driver
>
> Would anyone have another idea they would like to share?
As I said. Have OpenBIOS build the list of resolutions and put it in a
property (in binary, not ASCII form so the driver doesn't have to do
the mess it does now) in the DT node of the device itself.
Cheers,
Ben.
next prev parent reply other threads:[~2016-09-21 9:02 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 ` Benjamin Herrenschmidt [this message]
2016-09-21 18:26 ` [Qemu-devel] " G 3
2016-09-21 21:53 ` Benjamin Herrenschmidt
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=1474448505.2857.116.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.