From: Timothy Miller <miller@techsource.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: John Bradford <john@grabjohn.com>,
chakkerz@optusnet.com.au,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OT] Crazy idea: Design open-source graphics chip
Date: Mon, 02 Feb 2004 12:13:26 -0500 [thread overview]
Message-ID: <401E8536.5000805@techsource.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0402011123010.20933@waterleaf.sonytel.be>
Geert Uytterhoeven wrote:
> On Thu, 29 Jan 2004, Timothy Miller wrote:
>
>>Ok, so, how about this idea:
>>
>>- Small Xilinx FPGA, 16M of RAM, and a DAC on a board.
>>- AGP 2X
>>- Up to 2048x2048 resolution at 8, 16, and 32 bpp.
>>- Acceleration ONLY for solid fills and bitblts on-screen.
>
>
> Sounds OK to me.
To you. But if you are the only customer, that doesn't make for very
large sales volumes.
>
>
>>Given that so little is accelerated, there is no point in putting more
>>than the viewable framebuffer on the card, hense the 16 megs. It would
>>probably actually HURT performance to cache pixmaps on the card.
>>
>>
>>Oh, there's one thing I forgot. It would have to support VGA. There is
>>a VGA core on opencores.org that we could use, but its logic area would
>>probably push up the FPGA cost so that the board was in the $100 range.
>> Probably more.
>
>
> Why support legacy VGA? It makes things more complex and expensive, and doesn't
> give us much, especially for a SoC.
It's all about console support in a PC.
BTW, What is SoC?
next prev parent reply other threads:[~2004-02-02 17:08 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
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 [this message]
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=401E8536.5000805@techsource.com \
--to=miller@techsource.com \
--cc=chakkerz@optusnet.com.au \
--cc=geert@linux-m68k.org \
--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