From: Timothy Miller <miller@techsource.com>
To: Daniel Phillips <phillips@istop.com>
Cc: 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:46:14 -0400 [thread overview]
Message-ID: <418265C6.9020308@techsource.com> (raw)
In-Reply-To: <200410271423.33380.phillips@istop.com>
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?
I think you'll have to power-cycle the whole machine.
1) You have to get the FPGA's loader logic to reload the bitstream.
While there are external signals to get the FPGA to reload, there may be
a chicken&egg problem with getting soft logic in the FPGA to tell the
FPGA to reload.
2) When you have reloaded the FPGA, registers are in an unknown state.
One important thing that is lost if the PCI config space info. That
would have to be restored by software.
Is it impossible to soft-reset it? Maybe not. But so much is lost and
broken in the process that it may be highly impractical.
Nevertheless, if there's a way to do it, and the community wants to
develop it, I'm all in favor.
next prev parent reply other threads:[~2004-10-29 15:52 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
2004-10-29 15:46 ` Timothy Miller [this message]
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=418265C6.9020308@techsource.com \
--to=miller@techsource.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--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