From: Ivan Bornyakov <i.bornyakov@metrotek.ru>
To: Conor.Dooley@microchip.com
Cc: mdf@kernel.org, hao.wu@intel.com, yilun.xu@intel.com,
trix@redhat.com, linux-kernel@vger.kernel.org,
linux-fpga@vger.kernel.org, system@metrotek.ru
Subject: Re: [PATCH v4] fpga: microchip-spi: add Microchip FPGA manager
Date: Sat, 19 Feb 2022 08:45:57 +0300 [thread overview]
Message-ID: <20220219054557.5jb2om2ydy4ivhd5@x260> (raw)
In-Reply-To: <e86d4a9e-79d8-706b-aea5-153e2efcdfc3@microchip.com>
Hi, Conor
On Fri, Feb 18, 2022 at 03:22:57PM +0000, Conor.Dooley@microchip.com wrote:
> Hey Ivan,
> Finally got my hands on a board with a non SoC PolarFire today & started
> trying to test. Ran into problems with my SPI setup - would be nice to
> know if youre currently doing the reprogramming on one of our devkits
> etc or on a custom board of your own?
> Will be Monday before I can have look at it again, will have another
> board I can try then in the odd chance this one isnt actually capable of
> reprogramming.
> Thanks,
> Conor.
>
I'm working with a custom board.
next prev parent reply other threads:[~2022-02-19 6:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 13:38 [PATCH] fpga: microsemi-spi: add Microsemi " Ivan Bornyakov
2022-02-14 19:22 ` kernel test robot
2022-02-14 20:34 ` kernel test robot
2022-02-15 11:58 ` [PATCH v2] " Ivan Bornyakov
2022-02-15 17:37 ` Conor Dooley
2022-02-15 17:52 ` Moritz Fischer
2022-02-15 18:05 ` Ivan Bornyakov
2022-02-16 12:55 ` Conor.Dooley
2022-02-16 15:56 ` [PATCH v3] fpga: microchip-spi: add Microchip " Ivan Bornyakov
2022-02-17 19:18 ` [PATCH v4] " Ivan Bornyakov
2022-02-18 15:22 ` Conor.Dooley
2022-02-19 5:45 ` Ivan Bornyakov [this message]
2022-02-18 16:05 ` Xu Yilun
2022-02-19 6:16 ` Ivan Bornyakov
2022-02-19 10:42 ` Ivan Bornyakov
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=20220219054557.5jb2om2ydy4ivhd5@x260 \
--to=i.bornyakov@metrotek.ru \
--cc=Conor.Dooley@microchip.com \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=system@metrotek.ru \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.com \
/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
all inboxes | Powered by JetHome®