From: Roland Dreier <roland@topspin.com>
To: Timothy Miller <miller@techsource.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OT] Crazy idea: Design open-source graphics chip
Date: 31 Jan 2004 10:39:27 -0800 [thread overview]
Message-ID: <52ptd07yjk.fsf@topspin.com> (raw)
In-Reply-To: <401ACB54.1060304@techsource.com>
>>>>> "Timothy" == Timothy Miller <miller@techsource.com> writes:
Timothy> Alright then, how about this: Assuming opencores has a
Timothy> PCI interface and a DDR memory controller, I could write
Timothy> a CRT controller. We can put that into an FPGA and see
Timothy> what happens.
I suggest propose the following: spend the next few months designing,
writing documents, and starting on the RTL. In that time PCI Express
(PCI over high-speed serial) motherboards and fairly cheap
next-generation Xilinx Virtex FPGAs with integrated SERDES and a free
PCI Express core from Xilinx should be available.
PCI Express 8X gives you 16 Gb/sec of bandwidth in both directions (32
Gb/sec total) which should be enough to make UMA (ie no memory
attached to the FPGA) palatable. So your proto board is looking like
it has just power supplies, FPGA, and misc. video junk (ie DAC or
digital flat panel support), so it should be reasonably cheap to
design and fab. If you really want to, you could look at putting DRAM
(RLDRAM?) down on the board but I don't think it's worth the cost and
complexity.
(By the way, the Virtex FPGAs also have embedded PowerPC 405 cores
that can run at ~400 MHz, which means a a lot of stuff -- exception
paths, etc -- can be done in firmware if you want)
It's still in the thousands of dollars for this proto stage, but the
Virtex should be fast enough to do something pretty interesting. At
that point either the project takes off and you can look at doing a
full custom chip (I don't think it's worth doing any "rapid chip" of
low-NRE design, since your unit costs will be too high for a
mass-volume graphics chip), or the project dies.
- Roland
next prev parent reply other threads:[~2004-01-31 18:39 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 17:34 [OT] Crazy idea: Design open-source graphics chip Timothy Miller
2004-01-29 1:11 ` Christian Unger
2004-01-29 15:59 ` Stephen Smoogen
2004-01-29 16:07 ` Maciej Soltysiak
2004-01-29 16:21 ` John Bradford
2004-01-29 16:13 ` Timothy Miller
2004-01-29 16:29 ` John Bradford
2004-01-29 16:52 ` Timothy Miller
2004-01-29 17:18 ` John Bradford
2004-01-29 17:47 ` Timothy Miller
2004-01-29 18:55 ` John Bradford
2004-01-29 19:11 ` Timothy Miller
2004-01-29 21:36 ` John Bradford
2004-01-29 21:36 ` Timothy Miller
2004-01-30 10:36 ` Helge Hafting
2004-01-30 17:02 ` Timothy Miller
2004-01-30 17:20 ` Maciej W. Rozycki
2004-01-30 17:40 ` Timothy Miller
2004-01-30 18:11 ` Maciej W. Rozycki
2004-01-30 18:21 ` Timothy Miller
2004-01-30 19:09 ` Maciej W. Rozycki
2004-01-30 21:09 ` Helge Hafting
2004-01-30 21:23 ` Timothy Miller
2004-01-31 17:32 ` John Bradford
2004-01-31 18:39 ` Roland Dreier [this message]
2004-01-30 17:23 ` Måns Rullgård
2004-01-30 17:44 ` Timothy Miller
2004-01-30 19:01 ` John Bradford
2004-01-30 21:19 ` Helge Hafting
2004-02-01 10:36 ` Geert Uytterhoeven
2004-02-01 11:06 ` John Bradford
2004-02-01 11:46 ` Måns Rullgård
2004-02-01 22:41 ` Christian Unger
2004-02-02 17:13 ` Timothy Miller
2004-02-02 17:11 ` Geert Uytterhoeven
2004-01-30 16:54 ` Jesse Pollard
2004-02-01 10:35 ` Geert Uytterhoeven
2004-02-02 17:03 ` Timothy Miller
2004-01-29 16:30 ` Richard B. Johnson
2004-01-29 16:58 ` Timothy Miller
2004-01-29 18:08 ` Frank Gevaerts
2004-01-30 22:35 ` Esben Stien
2004-01-29 18:06 ` Torrey Hoffman
2004-01-29 18:58 ` Timothy Miller
2004-01-31 18:41 ` Pavel Machek
2004-01-31 18:15 ` Tomas Zvala
-- strict thread matches above, loose matches on Subject: below --
2004-02-01 14:58 DaMouse Networks
2004-02-02 17:16 ` Timothy Miller
2004-02-02 17:37 ` DaMouse Networks
2004-02-02 18:45 ` Timothy Miller
2004-02-02 19:43 ` DaMouse Networks
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=52ptd07yjk.fsf@topspin.com \
--to=roland@topspin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.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