From: Peter Maydell <peter.maydell@linaro.org>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
QEMU Trivial <qemu-trivial@nongnu.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH 04/10] sm501: Add emulation of chip connected via PCI
Date: Sat, 25 Feb 2017 16:14:57 +0000 [thread overview]
Message-ID: <CAFEAcA9pjHt_vx10V-+H7j2_hc8gkMmJLfbYvSR2Z8dj4cguCw@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.20.1702242123280.76443@zero.eik.bme.hu>
On 24 February 2017 at 20:25, BALATON Zoltan <balaton@eik.bme.hu> wrote:
> On Fri, 24 Feb 2017, Peter Maydell wrote:
>> Dropping the requirement for a base addr is not really the same
>> change as adding the PCI device.
>
>
> This is needed for PCI device because the base is not accessible before
> something maps the BARs of the device so I had to use something else that is
> known. So this change is part of making it a PCI device but I could make
> this a separate patch if you think that's better. Should I split it off or
> can leave it here?
I would split it off.
thanks
-- PMM
next prev parent reply other threads:[~2017-02-25 16:15 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 16:35 [Qemu-devel] [PATCH 00/10] Improvements for sm501 display controller emulation BALATON Zoltan
2017-02-19 16:35 ` [Qemu-devel] [PATCH 05/10] sm501: Add missing arbitration control register BALATON Zoltan
2017-02-19 16:35 ` [Qemu-devel] [PATCH 04/10] sm501: Add emulation of chip connected via PCI BALATON Zoltan
2017-02-24 14:43 ` Peter Maydell
2017-02-24 20:25 ` BALATON Zoltan
2017-02-25 16:14 ` Peter Maydell [this message]
2017-02-19 16:35 ` [Qemu-devel] [PATCH 10/10] ppc: Add SM501 device in config for ppc and ppcemb targets BALATON Zoltan
2017-02-24 14:55 ` Peter Maydell
2017-02-24 20:51 ` BALATON Zoltan
2017-02-25 5:43 ` Thomas Huth
2017-02-19 16:35 ` [Qemu-devel] [PATCH 03/10] sm501: QOMify BALATON Zoltan
2017-02-24 14:39 ` Peter Maydell
2017-02-24 20:23 ` BALATON Zoltan
2017-02-25 16:14 ` Peter Maydell
2017-02-26 0:39 ` BALATON Zoltan
2017-02-19 16:35 ` [Qemu-devel] [PATCH 09/10] sm501: Add some more missing registers BALATON Zoltan
2017-02-24 14:54 ` Peter Maydell
2017-02-24 20:48 ` BALATON Zoltan
2017-02-24 21:49 ` BALATON Zoltan
2017-02-25 16:31 ` Peter Maydell
2017-02-19 16:35 ` [Qemu-devel] [PATCH 01/10] sm501: Fixed code style and a few typos in comments BALATON Zoltan
2017-02-24 14:29 ` Peter Maydell
2017-02-19 16:35 ` [Qemu-devel] [PATCH 02/10] sm501: Use defines instead of constants where available BALATON Zoltan
2017-02-24 14:28 ` Peter Maydell
2017-02-24 20:18 ` BALATON Zoltan
2017-02-19 16:35 ` [Qemu-devel] [PATCH 08/10] sm501: Add support for panel layer BALATON Zoltan
2017-02-24 14:52 ` Peter Maydell
2017-02-24 20:38 ` BALATON Zoltan
2017-02-25 16:23 ` Peter Maydell
2017-02-19 16:35 ` [Qemu-devel] [PATCH 06/10] sm501: Fix device endianness BALATON Zoltan
2017-02-24 14:50 ` Peter Maydell
2017-02-24 20:35 ` BALATON Zoltan
2017-02-25 16:21 ` Peter Maydell
2017-02-26 0:49 ` BALATON Zoltan
2017-02-19 16:35 ` [Qemu-devel] [PATCH 07/10] sm501: Fix hardware cursor BALATON Zoltan
2017-02-23 17:31 ` [Qemu-devel] [PATCH 00/10] Improvements for sm501 display controller emulation BALATON Zoltan
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=CAFEAcA9pjHt_vx10V-+H7j2_hc8gkMmJLfbYvSR2Z8dj4cguCw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=aurelien@aurel32.net \
--cc=balaton@eik.bme.hu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).