qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alistair <alistair23@gmail.com>
To: Palmer Dabbelt <palmer@sifive.com>,
	"alistair.francis@wdc.com" <alistair.francis@wdc.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Michael Clark <mjc@sifive.com>
Subject: Re: [Qemu-devel] [PATCH v1 0/5] Connect a PCIe host and graphics support toRISC-V
Date: Thu, 2 Aug 2018 12:18:58 -0700	[thread overview]
Message-ID: <5b63594d.1c69fb81.60370.1c46@mx.google.com> (raw)
In-Reply-To: <mhng-df1b106f-72bb-4857-9acc-4095019307e4@palmer-si-x1c4>

Hey,

Sorry for the top post. I’m on holidays at the moment and will be back next week.

I have sent a V2 to the list, I don’t think I CCed you as I know your busy. Once the 3.1 merge window opens I’ll send a new version with all the comments I have received.

Alistair

From: Palmer Dabbelt
Sent: Thursday, 2 August 2018 10:44 AM
To: alistair.francis@wdc.com
Cc: qemu-devel@nongnu.org; alistair.francis@wdc.com; alistair23@gmail.com; Michael Clark
Subject: Re: [PATCH v1 0/5] Connect a PCIe host and graphics support toRISC-V

On Fri, 22 Jun 2018 12:28:14 PDT (-0700), alistair.francis@wdc.com wrote:
> Alistair Francis (5):
>   hw/riscv/virtio: Set the soc device tree node as a simple-bus
>   hw/riscv/virt: Increase the number of interrupts
>   hw/riscv/virt: Connect the Xilinx PCIe
>   hw/riscv/virt: Connect a VGA PCIe device
>   riscv64-softmmu.mak: Build Virtio Block support
>
>  default-configs/riscv32-softmmu.mak |  6 +++
>  default-configs/riscv64-softmmu.mak |  8 ++++
>  hw/riscv/virt.c                     | 73 ++++++++++++++++++++++++++++-
>  include/hw/riscv/virt.h             |  6 ++-
>  4 files changed, 90 insertions(+), 3 deletions(-)

Sorry I'm so slow here, I'm still chewing through my patch backlog.  It looks 
like this hasn't made it upstream yet.  I rebased it on top of master but have 
yet to figure out how to make it work, though I think that's on the Linux side.

I haven't yet looked at the code, but I like the functionality so I don't want 
to lose this.  Can you submit a v2 that applies cleanly to master, or do you 
want me to deal with it?

      reply	other threads:[~2018-08-02 19:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 19:28 [Qemu-devel] [PATCH v1 0/5] Connect a PCIe host and graphics support to RISC-V Alistair Francis
2018-06-22 19:29 ` [Qemu-devel] [PATCH v1 1/5] hw/riscv/virtio: Set the soc device tree node as a simple-bus Alistair Francis
2018-06-22 19:29 ` [Qemu-devel] [PATCH v1 2/5] hw/riscv/virt: Increase the number of interrupts Alistair Francis
2018-06-22 19:30 ` [Qemu-devel] [PATCH v1 3/5] hw/riscv/virt: Connect the Xilinx PCIe Alistair Francis
2018-06-23 20:07   ` Peter Maydell
2018-06-23 20:17     ` Michael Clark
2018-06-22 19:30 ` [Qemu-devel] [PATCH v1 4/5] hw/riscv/virt: Connect a VGA PCIe device Alistair Francis
2018-06-22 19:31 ` [Qemu-devel] [PATCH v1 5/5] riscv64-softmmu.mak: Build Virtio Block support Alistair Francis
2018-08-02 17:44 ` [Qemu-devel] [PATCH v1 0/5] Connect a PCIe host and graphics support to RISC-V Palmer Dabbelt
2018-08-02 19:18   ` Alistair [this message]

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=5b63594d.1c69fb81.60370.1c46@mx.google.com \
    --to=alistair23@gmail.com \
    --cc=alistair.francis@wdc.com \
    --cc=mjc@sifive.com \
    --cc=palmer@sifive.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).