From: Alistair Francis <alistair23@gmail.com>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: Alistair Francis <Alistair.Francis@wdc.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
qemu-riscv@nongnu.org, Guenter Roeck <linux@roeck-us.net>,
Andrea Bolognani <abologna@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-3.2 v7 5/6] hw/riscv/sifive_u: Connect the Xilinx PCIe
Date: Wed, 21 Nov 2018 11:51:58 -0800 [thread overview]
Message-ID: <CAKmqyKMPHg7nGr-Ua1Cb7yvdZzWAs6HOM4eB+SinMypXQ5Ni6w@mail.gmail.com> (raw)
In-Reply-To: <6480496b-dbb5-37bb-57e2-7a4819c61511@deltatee.com>
On Wed, Nov 21, 2018 at 11:25 AM Logan Gunthorpe <logang@deltatee.com> wrote:
>
>
>
> On 2018-11-21 12:21 p.m., Alistair Francis wrote:
> > On Wed, Nov 21, 2018 at 11:19 AM Logan Gunthorpe <logang@deltatee.com> wrote:
> >> Well, I also have a kernel (one I've built myself) without microsemi
> >> support, but with Xilinx support and it also doesn't work (see my dmesg
> >> logs I sent).
> >
> > So this one should work.
>
> It does not, see the dmesgs I sent a few emails ago.
>
> >>
> >>> For people who have modified the standard bbl to edit the device tree
> >>> before passing it to Linux to add the MicroSemi PCIe node, it won't
> >>> work. That's a very small number of people who have modified the
> >>> standard boot loader. I don't think we need to document how those
> >>> people get back to the default set-up.
> >>
> >> I have not done that. And it's not working for me.
> >
> > If you haven't done this then how can Linux know to probe the
> > MicroSemi PCIe root complex?
>
> Oh, well actually, in this case I was using the bbl/kernel you sent us,
> so I'm not actually sure what's in it. The stuff I built myself doesn't
> have any of the microsemi stuff, so it sounds like all that was a red
> herring.
Ah ok. There was some confusion there then.
So now it sounds like it's not working and there is no MicroSemi
device. I will check and see what I find.
Alistair
>
> Logan
next prev parent reply other threads:[~2018-11-21 19:52 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 17:02 [Qemu-devel] [PATCH for-3.2 v7 0/6] Connect a PCIe host and graphics support to RISC-V Alistair Francis
2018-11-21 17:02 ` [Qemu-devel] [PATCH for-3.2 v7 1/6] hw/riscv/virt: Increase the number of interrupts Alistair Francis
2018-11-21 17:58 ` Logan Gunthorpe
2018-11-21 18:17 ` Alistair Francis
2018-11-21 18:45 ` Logan Gunthorpe
2018-11-21 18:49 ` Alistair Francis
2018-11-21 18:56 ` Logan Gunthorpe
2018-11-21 18:59 ` Alistair Francis
2018-11-21 19:02 ` Logan Gunthorpe
2018-11-21 17:02 ` [Qemu-devel] [PATCH for-3.2 v7 2/6] hw/riscv/virt: Adjust memory layout spacing Alistair Francis
2018-11-21 17:59 ` Logan Gunthorpe
2018-11-21 17:02 ` [Qemu-devel] [PATCH for-3.2 v7 3/6] hw/riscv/virt: Connect the gpex PCIe Alistair Francis
2018-11-21 18:01 ` Logan Gunthorpe
2018-11-21 18:21 ` Alistair Francis
2018-11-21 17:02 ` [Qemu-devel] [PATCH for-3.2 v7 4/6] riscv: Enable VGA and PCIE_VGA Alistair Francis
2018-11-21 18:01 ` Logan Gunthorpe
2018-11-21 17:02 ` [Qemu-devel] [PATCH for-3.2 v7 5/6] hw/riscv/sifive_u: Connect the Xilinx PCIe Alistair Francis
2018-11-21 18:05 ` Logan Gunthorpe
2018-11-21 18:32 ` Alistair Francis
2018-11-21 18:50 ` Logan Gunthorpe
2018-11-21 19:02 ` Alistair Francis
2018-11-21 19:08 ` Logan Gunthorpe
2018-11-21 19:16 ` Alistair Francis
2018-11-21 19:19 ` Logan Gunthorpe
2018-11-21 19:21 ` Alistair Francis
2018-11-21 19:24 ` Logan Gunthorpe
2018-11-21 19:51 ` Alistair Francis [this message]
2018-11-21 21:54 ` Alistair Francis
2018-11-21 22:01 ` Logan Gunthorpe
2018-11-21 22:09 ` Alistair Francis
2018-11-21 22:11 ` Logan Gunthorpe
2018-11-21 22:15 ` Palmer Dabbelt
2018-11-21 21:37 ` Palmer Dabbelt
2018-11-21 22:01 ` Alistair Francis
2018-11-21 22:15 ` Palmer Dabbelt
2018-11-21 19:15 ` Logan Gunthorpe
2018-11-21 19:18 ` Alistair Francis
2018-11-21 19:20 ` Logan Gunthorpe
2018-11-21 21:26 ` Palmer Dabbelt
2018-11-21 21:49 ` Alistair Francis
2018-11-21 22:15 ` Palmer Dabbelt
2018-11-21 22:23 ` Alistair Francis
2018-11-21 22:36 ` Palmer Dabbelt
2018-11-21 23:10 ` Guenter Roeck
2018-11-21 23:26 ` Logan Gunthorpe
2018-11-22 2:13 ` Palmer Dabbelt
2018-11-22 2:23 ` Alistair Francis
2018-11-26 19:15 ` Palmer Dabbelt
2018-11-21 18:36 ` Guenter Roeck
2018-11-21 18:55 ` Logan Gunthorpe
2018-11-21 17:03 ` [Qemu-devel] [PATCH for-3.2 v7 6/6] hw/riscv/virt: Connect a VirtIO net PCIe device Alistair Francis
2018-11-21 18:07 ` Logan Gunthorpe
2018-11-21 18:34 ` Alistair Francis
2018-11-21 19:11 ` Logan Gunthorpe
2018-11-21 21:55 ` Alistair Francis
2018-11-21 22:07 ` Logan Gunthorpe
2018-11-21 22:11 ` Alistair Francis
2018-11-21 22:14 ` Alistair Francis
2018-11-21 22:16 ` Logan Gunthorpe
2018-11-21 22:18 ` Logan Gunthorpe
2018-11-22 10:59 ` [Qemu-devel] [PATCH for-3.2 v7 0/6] Connect a PCIe host and graphics support to RISC-V Andrea Bolognani
2018-11-26 16:03 ` Alistair Francis
2018-11-26 19:34 ` Palmer Dabbelt
2018-11-26 21:33 ` Guenter Roeck
2018-11-27 12:40 ` Andrea Bolognani
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=CAKmqyKMPHg7nGr-Ua1Cb7yvdZzWAs6HOM4eB+SinMypXQ5Ni6w@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=Alistair.Francis@wdc.com \
--cc=abologna@redhat.com \
--cc=linux@roeck-us.net \
--cc=logang@deltatee.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@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).