From: Alistair <alistair23@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] display: add separate config option for bochs-display
Date: Fri, 5 Oct 2018 10:04:18 -0700 [thread overview]
Message-ID: <c91440d4-f8ef-7701-f280-995dd63a0988@gmail.com> (raw)
In-Reply-To: <20181005164800.klw6siygbyk2ipbx@sirius.home.kraxel.org>
On 10/05/2018 09:48 AM, Gerd Hoffmann wrote:
> On Fri, Oct 05, 2018 at 09:22:29AM -0700, Alistair Francis wrote:
>> On Fri, Oct 5, 2018 at 9:13 AM Gerd Hoffmann <kraxel@redhat.com> wrote:
>>>
>>> This allows modern architectures which don't care about vga
>>> compatibility (risc-v for example) build bochs-display without
>>> including all vga emulation too.
>>
>> For RISC-V we end up including pci.mak anyway for other things such as
>> NVMe drives. So we don't really need this, but it still seems useful.
>
> Hmm, maybe we should split pci.mak into pci-legacy.mak and pci-express.mak
> then?
That sounds like a good idea.
Alistair
>
> cheers,
> Gerd
>
next prev parent reply other threads:[~2018-10-05 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 16:01 [Qemu-devel] [PATCH 0/2] two little bochs-display patches Gerd Hoffmann
2018-10-05 16:01 ` [Qemu-devel] [PATCH 1/2] display: add separate config option for bochs-display Gerd Hoffmann
2018-10-05 16:22 ` Alistair Francis
2018-10-05 16:48 ` Gerd Hoffmann
2018-10-05 17:04 ` Alistair [this message]
2018-10-05 16:01 ` [Qemu-devel] [PATCH 2/2] bochs-display: wire up edid support Gerd Hoffmann
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=c91440d4-f8ef-7701-f280-995dd63a0988@gmail.com \
--to=alistair23@gmail.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--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).