From: Grant Likely <grant.likely@secretlab.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] fix for "fpga load" on spartan3 in slave parallel mode
Date: Sun, 1 Jul 2007 09:02:30 -0400 [thread overview]
Message-ID: <fa686aa40707010602p305e732ak7015d88d41586de9@mail.gmail.com> (raw)
In-Reply-To: <46865429.6030905@ccpu.com>
On 6/30/07, Bruce Adler <bruce.adler@ccpu.com> wrote:
>
> The while loop exits too soon if the "busy" function is a dummy function
> which always returns false.
But what if it isn't? Shouldn't the old behaviour be preserved, or is
this another bug?
Should the dummy function always return true instead?
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely at secretlab.ca
(403) 399-0195
prev parent reply other threads:[~2007-07-01 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 13:01 [U-Boot-Users] [PATCH] fix for "fpga load" on spartan3 in slave parallel mode Bruce Adler
2007-07-01 13:02 ` Grant Likely [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=fa686aa40707010602p305e732ak7015d88d41586de9@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--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