From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] FPGA: Cyclon II: Correctly reset the FPGA before configuration
Date: Mon, 29 Oct 2012 15:56:00 -0700 [thread overview]
Message-ID: <20121029225600.GI11581@bill-the-cat> (raw)
In-Reply-To: <1350983501-30673-1-git-send-email-sr@denx.de>
On Tue, Oct 23, 2012 at 11:11:41AM +0200, Stefan Roese wrote:
> From: Stephan Gatzka <stephan.gatzka@hbm.com>
>
> Deassert the CONFIG pin before asserting it again. This assures that the
> FPGA will be resetted and therefore configuration will be correctly
> enabled.
>
> This is also already done on other FPGA's, e.g. Stratix.
>
> Signed-off-by: Stephan Gatzka <stephan.gatzka@hbm.com>
> Signed-off-by: Stefan Roese <sr@denx.de>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20121029/349a6066/attachment-0001.pgp>
prev parent reply other threads:[~2012-10-29 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 9:11 [U-Boot] [PATCH] FPGA: Cyclon II: Correctly reset the FPGA before configuration Stefan Roese
2012-10-29 22:56 ` Tom Rini [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=20121029225600.GI11581@bill-the-cat \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/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