From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Daire.McNamara@microchip.com, linux-pci@vger.kernel.org
Subject: Re: [PATCH v17 3/3] PCI: microchip: Add host driver for Microchip PCIe controller
Date: Mon, 2 Nov 2020 11:15:25 +0000 [thread overview]
Message-ID: <2eee84c9-aa24-2587-5ced-1c2fe30a1d50@codethink.co.uk> (raw)
In-Reply-To: <MN2PR11MB426909C2B84E95AF301C404B96100@MN2PR11MB4269.namprd11.prod.outlook.com>
On 02/11/2020 10:39, Daire.McNamara@microchip.com wrote:
> Hi Ben,
>
> Yes, we've become aware of an issue that's cropped up with latest design file on Icicle with PCIe. We're working through it and we'll update once we have resolved it.
Thanks for looking at this.
We could really do with this working as we need faster storage
and graphics options for what we want to do with these boards.
I am happy to reinstall or rebuild images, i've got a v5.9 that
works to an extent on the icicles.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
https://www.codethink.co.uk/privacy.html
next prev parent reply other threads:[~2020-11-02 11:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 13:22 [PATCH v17 0/3] PCI: microchip: Add host driver for Microchip PCIe controller daire.mcnamara
2020-10-22 13:22 ` [PATCH v17 1/3] PCI: Call platform_set_drvdata earlier in devm_pci_alloc_host_bridge daire.mcnamara
2020-10-22 13:22 ` [PATCH v17 2/3] dt-bindings: PCI: microchip: Add Microchip PolarFire host binding daire.mcnamara
2020-10-23 16:41 ` Rob Herring
2020-10-22 13:22 ` [PATCH v17 3/3] PCI: microchip: Add host driver for Microchip PCIe controller daire.mcnamara
2020-10-28 17:21 ` Ben Dooks
[not found] ` <MN2PR11MB426909C2B84E95AF301C404B96100@MN2PR11MB4269.namprd11.prod.outlook.com>
2020-11-02 11:15 ` Ben Dooks [this message]
2020-11-18 16:39 ` Lorenzo Pieralisi
2020-11-18 17:04 ` Ben Dooks
[not found] ` <MN2PR11MB42693A7C10C71C327763FA8B96E00@MN2PR11MB4269.namprd11.prod.outlook.com>
2020-11-23 11:46 ` Ben Dooks
2020-11-18 16:44 ` Ben Dooks
2020-11-18 16:35 ` Lorenzo Pieralisi
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=2eee84c9-aa24-2587-5ced-1c2fe30a1d50@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=Daire.McNamara@microchip.com \
--cc=linux-pci@vger.kernel.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).