From: Timothy Miller <miller@techsource.com>
To: John Bradford <john@grabjohn.com>
Cc: chakkerz@optusnet.com.au,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OT] Crazy idea: Design open-source graphics chip
Date: Thu, 29 Jan 2004 11:52:55 -0500 [thread overview]
Message-ID: <40193A67.7080308@techsource.com> (raw)
In-Reply-To: <200401291629.i0TGTN7S001406@81-2-122-30.bradfords.org.uk>
John Bradford wrote:
>>The real question we have to ask ourselves is, what would be the market
>>demand for a graphics card that is 3 generations behind the state of the
>>art and over-priced, the only advantage being that it's a 100% open
>>architecture?
>
>
> Err, well there are always the server and embedded markets, if the
> device was cheap enough.
Ah, but it won't be. Low-volume ASICs are expensive. The chip itself
would probably be around $150, not counting $100k NRE. Then you have to
pay for the board, make up for the NRE, and make some profit to make it
worth while. How much are YOU willing to pay?
>
>
>>I don't have $100k to have it fabricated, so we have to goad some
>>company into doing it for us, and given the volumes, they'll have to
>>charge way more than it's worth if you compare its capabilities against
>>ATI et al.
>>
>>I've got some great ideas for how to do this chip, but they're frankly
>>nothing revolutionary. The obvious test bed is an FPGA. That imposes
>>serious limitations on what kind of logic utilization and performance we
>>can get. The ASIC version can be clocked faster, but we dare not put in
>>untested logic. (And we can't afford the tools necessary to do the
>>proper simulation.)
>
>
> WHAT!? You are making the project out to be several orders of
> magnitude more difficult and expensive than it is.
>
> Did you know that you can generate a 625-line TV signal with little
> more hardware than a Z80 CPU? Some 8-bits actually did that.
Certainly. But when you can get perfectly good open-source drivers for
an ATI Rage 128 and the board for $15 from a Taiwanese manufacturer,
who's going to want what you're describing?
The thing you have to keep in mind is that in order for this open arch
board to get developed, someone has to be willing to invest in
fabricating it, and that means it has to be somewhat competitive and a
significant performer.
From the mouth of someone who has done a graphics ASIC and numerous
FPGA designs also in graphics and who has worked on graphics boards in
air traffic control, medical, and workstation console markets and who
has written X-server modules for Number 9 i128, Matrox G450, Permidia 2
and 3, Radeon 7500 and 9000, my own graphics chip, probably a number of
chips I've forgotten AND who has been very performance and cost
conscious the whole time: It is MORE complicated than I make it sound.
That doesn't mean it's not doable. :)
>
>
>>So, the big question: How many units a year would be sold for an
>>underpowered, over-priced graphics card that just happens to be 100%
>>open and 100% supported?
>
>
> Quite a few. Think of the TV-connected embedded appliance market, for
> example. Displaying a static menu of choices isn't exactly very
> demanding.
This sort of thing is ALREADY available with open-source drivers.
Whatever we design is going to be EXPENSIVE. So, regardless of the fact
that an ATI All-in-Wonder Radeon 9000 is over-powered for job you
describe, that board will be cheaper than what we could produce.
Because of certain invariant costs, there is a performance point below
which it is not worth it. Because of non-invariant costs, there is a
performance above which it is not worth it. There may or not be a point
where the compromize makes it worth doing.
Now, this all assumes that it's completely a hobbyist project. If we
were to design something that was, in principle, a good performer, but
we couldn't simulate, debug, and fabricate it, we MIGHT be able to
convince some companies to do that FOR us. And they might even be able
to enhance it in ways that would make it compete on performance.
But it's still going to be expensive.
next prev parent reply other threads:[~2004-01-29 16:49 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 [this message]
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
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=40193A67.7080308@techsource.com \
--to=miller@techsource.com \
--cc=chakkerz@optusnet.com.au \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
/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