From: Timothy Miller <miller@techsource.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Need help and advice... [was: HARDWARE: Open-Source-Friendly Graphics Cards -- Viable?]
Date: Mon, 25 Oct 2004 19:06:41 -0400 [thread overview]
Message-ID: <417D8701.8020905@techsource.com> (raw)
In-Reply-To: <200410251734.39703.rmiller@duskglow.com>
I'm probably doing this too early, but it's been pointed out in so many
words that I won't scale. I've spent two full work days digesting all
of the discussions on LKML, kerneltrap, and slashdot. That's been as
fun as you can imagine, but when the time comes for me to start working
on the design, I can't do that at all anymore.
What I'll need are representatives of the community who work with me to
make sure that my design does what everyone needs it to do, and I need
representatives who engage in mailing lists and extract for me
information that I should see.
I'm sure there are lots of people who would love to have that kind of
influence over a company whose hardware they want to buy. I need the
subset of those people who have expertise in 3D graphics, most of whom
I'm sure are on OpenGL and X.org mailing lists right now. If there's
anyone here who can get me connected with those people, I would
appreciate it very much.
I feel like I'm being presumptuous. Although everyone at Tech Source is
excited by the idea, and there seems to be a ground-swell of interest,
the economic feasibility of this is still in the air. I don't want to
waste anyone's time. However, a lot of excellent ideas have been put
forth, and I'd like discussion to continue, but in a way that I can handle.
I humbly request advice on how I might go about handling all of this in
the best way.
I also think the discussion should transition off LKML and onto its own
forum.
Also, I want to thank everyone for talking to me about this. Members of
this list and people posting to kerneltrap and slashdot have been very
informative and helpful. I also want to mention Jeremy Andrews of
kerneltrap.org who first turned my posting into news. I've wanted to do
a project like this for a long time, but the past few days of online
discussion have really helped push it towards becoming reality.
next prev parent reply other threads:[~2004-10-26 2:42 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
[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 ` Timothy Miller [this message]
2004-10-27 18:38 ` 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=417D8701.8020905@techsource.com \
--to=miller@techsource.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