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 16:36:35 -0500 [thread overview]
Message-ID: <40197CE3.2020205@techsource.com> (raw)
In-Reply-To: <200401292136.i0TLaR76000250@81-2-122-30.bradfords.org.uk>
John Bradford wrote:
>
> If we put 4 or more on each board, it could be useful for betting
> shops, stock markets, shop window displays, and other applications
> where you need to control a dozen or more screens, which basically
> contain textual information, but where 80x25 text mode just isn't
> enough. I.E. you might want the odd pie chart or different sized text
> or something.
The market for secondary heads is too small. You can get an ATI Mach 64
PCI card for pennies and add it as a second head for what you're describing.
For an open-source graphics card to be marketable, it would have to be
attractive as a primary head used in Linux workstations and servers, and
it would have to be so in a PC market.
>
>
>>Oh, there's one thing I forgot. It would have to support VGA.
>
>
> Maybe not, the primary market for this, (I.E. what makes it cost
> effective to produce, and therefore available for developers to use as
> their primary display), could be users who want to control many
> displays, and who would have a standard VGA card for the primary
> monitor. (Yeah, it would be kind of ironic if 99% of our amasing new
> graphics cards ended up in mahines with another card as the primary
> display, but then again, if it makes the open hardware available for
> developers to experiment with at a reasonable cost, it would be worth
> doing).
The irony is too much. Seriously.
>
> So, what about a PCI card with four or eight 16MB framebuffers, and
> the basic acceleration and other specs you described above. Is that
> at least slightly feasible, do you think?
Adding extra heads is relatively easy, and you can keep the memory
unified and do it all in one chip.
next prev parent reply other threads:[~2004-01-29 21:33 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 [this message]
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=40197CE3.2020205@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