From: "Daniel Glöckner" <dg@emlix.com>
To: Xu Yilun <yilun.xu@intel.com>
Cc: Ivan Bornyakov <i.bornyakov@metrotek.ru>,
mdf@kernel.org, hao.wu@intel.com, trix@redhat.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
linux-fpga@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, system@metrotek.ru
Subject: Re: [PATCH v6 1/2] fpga: ecp5-spi: add Lattice ECP5 FPGA manager
Date: Tue, 16 Aug 2022 09:42:16 +0200 [thread overview]
Message-ID: <20220816074216.GA31706@homes.emlix.com> (raw)
In-Reply-To: <Yvs0jieXsyzhn8q9@yilunxu-OptiPlex-7050>
On Tue, Aug 16, 2022 at 02:09:18PM +0800, Xu Yilun wrote:
> We don't have to make everything fine, but start with machxo2 and ecp5
> first. If the change affects machxo2, other people may help.
Programming MachXO* chips uses different sequences of commands. With ECP5
you put the chip into configuration mode and then upload the bitstream
into RAM cells. With MachXO chips you write the bitstream to non-volatile
storage and then tell the chip to go into configuration mode where it
automatically loads the bitstream from non-volatile storage. There is no
way to directly write the RAM cells.
Best regards,
Daniel
next prev parent reply other threads:[~2022-08-16 9:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 13:21 [PATCH v6 0/2] Lattice ECP5 FPGA manager Ivan Bornyakov
2022-08-15 13:21 ` [PATCH v6 1/2] fpga: ecp5-spi: add " Ivan Bornyakov
2022-08-16 2:00 ` Xu Yilun
2022-08-16 4:58 ` Ivan Bornyakov
2022-08-16 6:09 ` Xu Yilun
2022-08-16 7:42 ` Daniel Glöckner [this message]
2022-08-17 9:04 ` Ivan Bornyakov
2022-08-18 2:13 ` Xu Yilun
2022-08-15 13:21 ` [PATCH v6 2/2] dt-bindings: fpga: add binding doc for ecp5-spi fpga mgr 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=20220816074216.GA31706@homes.emlix.com \
--to=dg@emlix.com \
--cc=devicetree@vger.kernel.org \
--cc=hao.wu@intel.com \
--cc=i.bornyakov@metrotek.ru \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.