From: offer@sgi.com (richard offer)
To: linux@morgaine.engr.sgi.com
Subject: Re: Good news: no more begging for HW
Date: Tue, 17 Jun 1997 17:15:52 -0700 [thread overview]
Message-ID: <9706171715.ZM15632@sgi.com> (raw)
In-Reply-To: jwiede@blammo (John Wiederhirn) "Re: Good news: no more begging for HW" (Jun 17, 5:00pm)
* $ from jwiede@blammo at "17-Jun: 5:00pm" | sed "1,$s/^/* /"
*
*
* I realize this comes off as fairly negative, but I'm just trying to explain
the
* issues involved once gfx gets added to the mix. There would need to be a
* buy-in at a very high level of SGI mgmt. before we could start making the
* hardware details of our graphics subsystems available (at least the more
modern
* ones, such as O2, Impact, etc.).
I don't think this is being negitive, it might not be what we want to hear, but
at least someone who knows about our underlying hardware is making comments.
Probably the first thing to do would be to get the go ahead for a proof of
concept only (under NDA) probably using an old indy. If this proves impossible
from either the technical or political pov's then we need to re-think.
I personaly don't think we have much chance unless we go to NDA and even then
its going to be really hard to get buy-in.
*
*
* --
* John Wiederhirn (DSD, Graphics Kernel MTS) jwiede@engr.sgi.com
* "Smithers, unleash the human insight and creativity."
*
richard.
________________________________________________________________________
Dogbert: "From now on I will not try to reason with the idiots I
encounter. I will dismiss them by waving my paw and saying
'BAH'".
Dilbert: "Just because someone thinks differently from you doesn't
mean he's an idiot, Dogbert".
Dogbert: [waves paw], "BAH".
Dilbert: 27-July-96.
next prev parent reply other threads:[~1997-06-18 0:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199706170046.CAA17216@informatik.uni-koblenz.de>
1997-06-17 1:06 ` Good news: no more begging for HW Ariel Faigon
1997-06-17 1:06 ` Ariel Faigon
1997-06-17 1:53 ` Alex deVries
1997-06-17 2:01 ` David S. Miller
[not found] ` <davem@jenolan.rutgers.edu>
1997-06-17 16:23 ` richard offer
1997-06-17 17:10 ` Miguel de Icaza
1997-06-17 17:49 ` Mike Shaver
1997-06-17 17:49 ` Mike Shaver
1997-06-17 17:53 ` richard offer
1997-06-17 18:00 ` Miguel de Icaza
1997-06-17 18:30 ` Martin Knoblauch
1997-06-17 18:45 ` David S. Miller
1997-06-18 0:00 ` John Wiederhirn
1997-06-18 0:15 ` richard offer [this message]
1997-06-18 0:32 ` Ralf Baechle
1997-06-18 0:32 ` Ralf Baechle
1997-06-19 19:23 ` William J. Earl
1997-06-18 0:34 ` Getting X on Linux/SGI Ariel Faigon
1997-06-18 0:34 ` Ariel Faigon
1997-06-18 16:28 ` Christopher W. Carlson
1997-06-18 19:30 ` Nigel Gamble
1997-06-18 2:47 ` Good news: no more begging for HW Miguel de Icaza
1997-06-18 12:38 ` William J. Earl
1997-06-18 12:38 ` William J. Earl
1997-06-18 6:37 Larry McVoy
1997-06-18 6:37 ` Larry McVoy
-- strict thread matches above, loose matches on Subject: below --
1997-06-17 6:22 Larry McVoy
1997-06-17 9:46 ` Ralf Baechle
1997-06-17 9:46 ` Ralf Baechle
1997-06-17 16:08 ` Miguel de Icaza
1997-06-17 2:25 Larry McVoy
1997-06-17 2:25 ` Larry McVoy
1997-06-17 5:31 ` Alex deVries
1997-06-16 23:25 Ariel Faigon
1997-06-17 3:59 ` Christopher W. Carlson
1997-06-17 8:15 ` Martin Knoblauch
1997-06-17 16:18 ` Miguel de Icaza
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=9706171715.ZM15632@sgi.com \
--to=offer@sgi.com \
--cc=linux@morgaine.engr.sgi.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