From: Sascha Hauer <s.hauer@pengutronix.de>
To: Michael Tretter <m.tretter@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>,
Michael Graichen <michael.graichen@hotmail.com>
Subject: Re: [PATCH v2 7/7] added-zynq-fpga-manager
Date: Wed, 15 Apr 2020 12:27:58 +0200 [thread overview]
Message-ID: <20200415102758.GN1694@pengutronix.de> (raw)
In-Reply-To: <20200415061909.GA1078@pengutronix.de>
On Wed, Apr 15, 2020 at 08:19:09AM +0200, Michael Tretter wrote:
> Hi Michael,
>
> On Tue, Apr 14, 2020 at 09:23:53PM +0200, Michael Graichen wrote:
> > Am 14.04.20 um 12:53 schrieb Michael Tretter:
> > > On Thu, Apr 09, 2020 at 02:44:00PM +0000, Michael Graichen wrote:
> > > > This adds support to programm the PL part of the Zynq SoC,
> > > > but only the non-secure way and no partial reconfiguration. It adds the
> > > > 'zynq_fpga_manager' so we can use
> > > >
> > > > firmwareload -l
> > > > firmwareload -t zynq-fpga-manager /mnt/mmc0.0/design_1_wrapper.bit
> > > >
> > > > to programm the PL.
> > >
> > > The patch copies a lot of code from the PL programming code for the ZynqMP.
> > > The main differences are that the Zynq-7000 Bitstream header is 8 bytes
> > > shorter than for the ZynqMP and that the Zynq does not go through the
> > > firmware, but directly programs the PCAP.
> > >
> > > I think that we should extend the ZynqMP FPGA driver to be able to handle the
> > > PL programming of the Zynq-7000 as well instead of adding a new driver for
> > > that.
> > >
> > > Michael
> > >
> >
> > yes, i have learned from drivers/firmware/zynqmp-fpga.c how to deal with the
> > firmwareload command and how to validate the bitstream.
> > In generally it would be better to only have one driver but since i have no
> > access to a ZynqMP board i am kind of shy to touch these bits.
>
> I will happily test your patches on the ZynqMP:) I would really like to have
> more users of the zynqmp-fpga driver.
I dropped the patch for now in favor for the upcoming patches adding
support for the existing driver ;)
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2020-04-15 10:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 14:44 Michael Graichen
2020-04-14 10:53 ` Michael Tretter
2020-04-14 19:23 ` Michael Graichen
2020-04-15 6:19 ` Michael Tretter
2020-04-15 10:27 ` Sascha Hauer [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=20200415102758.GN1694@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.tretter@pengutronix.de \
--cc=michael.graichen@hotmail.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