From: Timothy Miller <miller@techsource.com>
To: linux-os@analogic.com
Cc: Daniel Phillips <phillips@istop.com>,
Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Some discussion points open source friendly graphics [was: HARDWARE: Open-Source-Friendly Graphics Cards -- Viable?]
Date: Fri, 29 Oct 2004 11:48:56 -0400 [thread overview]
Message-ID: <41826668.50208@techsource.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0410271459130.4669@chaos.analogic.com>
linux-os wrote:
> On Wed, 27 Oct 2004, Daniel Phillips wrote:
>
>> On Monday 25 October 2004 18:45, Timothy Miller wrote:
>>
>>> My intention is to include a bit of logic in the FPGA which can be used
>>> to reprogram the prom. You would then cycle power to get the FPGA to
>>> load the new code.
>>
>>
>> Power cycle the whole machine, or software-reset the card?
>>
>> Regards,
>>
>> Daniel
>
>
> The FPGA requires a physical reset-pin toggle to load new
> bits into the gate-array. This could be software-toggled,
> but that would require at least one external gate. This
> is because the power-reset needs to reset the chip before
> its bits are loaded plus some pin, after loading, needs to
> be an output to its reset pin also. Therefore, you need
> the external gate that is always present.
Generally speaking, more chips == bad. If reprogramming the FPGA were a
regular event, I'd see the point, but I hope that MOST users would NEVER
have to reprogram it.
next prev parent reply other threads:[~2004-10-29 15:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 15:54 Some discussion points open source friendly graphics [was: HARDWARE: Open-Source-Friendly Graphics Cards -- Viable?] Timothy Miller
2004-10-25 20:31 ` Some discussion points open source friendly graphics karl.vogel
2004-10-25 20:34 ` Some discussion points open source friendly graphics [was: HARDWARE: Open-Source-Friendly Graphics Cards -- Viable?] Jeff Garzik
2004-10-25 22:45 ` Timothy Miller
2004-10-27 18:23 ` Daniel Phillips
2004-10-27 19:04 ` linux-os
2004-10-29 15:48 ` Timothy Miller [this message]
2004-10-29 15:46 ` Timothy Miller
2004-10-26 13:09 ` Giuseppe Bilotta
2004-10-26 15:27 ` Timothy Miller
2004-10-26 15:26 ` linux-os
2004-10-26 16:04 ` Timothy Miller
[not found] ` <6.1.2.0.1.20041026110017.021ece28@mail.javagear.com>
2004-10-26 19:21 ` Timothy Miller
[not found] ` <200410251535.27852.rmiller@duskglow.com>
[not found] ` <417D80B0.6080007@techsource.com>
[not found] ` <200410251734.39703.rmiller@duskglow.com>
2004-10-25 23:06 ` Need help and advice... " Timothy Miller
2004-10-27 18:38 ` Some discussion points open source friendly graphics " Daniel Phillips
2004-10-29 15:47 ` Timothy Miller
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=41826668.50208@techsource.com \
--to=miller@techsource.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=phillips@istop.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