From: Timothy Miller <miller@techsource.com>
To: pbecke <pbecke@javagear.com>
Cc: linux-os@analogic.com, Giuseppe Bilotta <bilotta78@hotpop.com>,
linux-kernel@vger.kernel.org
Subject: Re: Some discussion points open source friendly graphics [was: HARDWARE: Open-Source-Friendly Graphics Cards -- Viable?]
Date: Tue, 26 Oct 2004 15:21:31 -0400 [thread overview]
Message-ID: <417EA3BB.1090700@techsource.com> (raw)
In-Reply-To: <6.1.2.0.1.20041026110017.021ece28@mail.javagear.com>
pbecke wrote:
> In many of the FPGA designs I have done, I have always tried to use some
> kind of parallel host interface port, that are built into many FPGAs to
> program the FPGA. This allows the FPGA to be loaded as if it is a
> memory device, Yes, it does mean that some external glue logic is
> usually required to decode address lines and such, but, it means that
> you can eliminate the eeprom, and usually the loading to the devices it
> self if much faster. I have more experience with the ram based FPGAs
> from Xilinx, then the eprom based ones from Actel, so it may not be
> feasible with the eprom based ones. But I really think that in system
> configuration is an advantage, that opens some possibilities that are
> much more difficult to implement if the design relies on a serial prom
> for the source of the FPGA configuration data.
My first desire is to minimize chip count, which means one FPGA with as
much of the logic in it as possible. If we do multi-core designs, it
would be logical to be able to reprogram each of the chips separately.
I would bundle the PCI controller with the PROM reprogrammer and any
other logic which doesn't change much and put the rest into the other
chip(s). This way, you could reprogram the core without risking the
whole thing.
>
> By the way have you considered opencores.org's VGA controller as a
> starting point for a design?
I am aware of it, but I've hesitated to even look at it. I respect the
author's wish to put it under a GPL-like license, and I don't want to
"cheat". (The issue here isn't what's legal but what's ethical.
Companies do bad things all the time which are perfectly legal, and I
want to avoid that.) The author of that VGA core posted to the
kerneltrap thread. Perhaps I can make some sort of arrangement with
him. For instance, a friend of mine sold a commercial program which had
some GPL'd components, but he first asked the authors to relicense under
LGPL. I'd be happy to release my improvements to any PIECES that I got
from elsewhere, but I want to have the option of not releasing the WHOLE
thing.
next prev parent reply other threads:[~2004-10-26 19:08 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
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 [this message]
[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=417EA3BB.1090700@techsource.com \
--to=miller@techsource.com \
--cc=bilotta78@hotpop.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=pbecke@javagear.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