All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Kimminau <eak@detroit.sgi.com>
To: dmanddmer <dmerchan@hiwaay.net>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: [Fwd: linus.linux.sgi.com]
Date: Wed, 20 Jan 1999 10:18:54 -0500	[thread overview]
Message-ID: <36A5F3DE.C94A0FA1@detroit.sgi.com> (raw)
In-Reply-To: 36A51517.A24C2BEB@hiwaay.net

Warning! Danger!

FUD. FUD. FUD.

dmanddmer wrote:
> 
> Btw, I heard a rumor that the memory in the VPC is custom or unique
> memory.  Is this true?  How much of the VPC, besides the obvious, is not
> industry standard?  If SGI is attempting solely to require customers to
> be able to buy any upgrades ONLY from SGI, then SGI has shot itself in
> the foot again.  It did not work for Apple, it didn't work for Unisys,
> it didn't work for Intergraph.  In short, it hasn't worked for anyone.
> 
> David M.

It is not a rumor. It is fact. The ram being used in the VPC is like the
memory in no other PC (that I know of) being manufactured today.

You know that SGI has pioneered several mainstream simm/dimm technologies? In
fact we hold the patents on a couple I believe. I'll leave it as an excercise
to the curious to find out which ones. When you see the size of the 40 pin
dimms we use in the VPC and then realize the density they are capable of in
less than half the space of currently available dimms, perhaps you will
reconsider your position.

Every time SGI introduces new ram technology, very shortly Kingston or some
other chip vendor starts making them and they are always cheaper than what you
can get from SGI directly. Then they start appearing in all the "standard"
generic clones.

Every new platform we have announced since the Indy has used ram technology
that noone else was really using. We use the best technology to gain the
highest levels of performance. You can buy Octane and O2 ram at WalMart now,
for chrissakes.
A quick search for "SGI O2 memory" on any search engine will show you a
hundred or so hits. VPC will take a little bit, but you can be sure there will
be 3rd party memory sources.

How much of the VPC is standard today? large portions. dual PCI bus (get that
from a clone) (and what does it cost to get it on a Sun?), the CPU's, serial
port, fire wire interfaces, parallel port, video in and out, digital audio
with all the standard ports, etc. The important parts, the parts that blow the
doors off of every other same-ol, same-ol generic clone PC isn't industry
standard, YET. 

How about you take this elsewhere, please.

EAK.

-- 
---------1---------2---------3---------4---------5---------6---------7
Eric Kimminau        eak@detroit.sgi.com      Field Technical Support
       SGI 39001 W. 12 Mile Rd.  Farmington, MI 48331-2903
      Vox:(248)848-4455  Fax:(248)848-5600  VNET:6-327-4455  

              "I speak my mind and no one else's."
 "I am a bomb technician. If you see me running, try to keep up..."
                    http://support.sgi.com

  parent reply	other threads:[~1999-01-20 16:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-19 23:28 [Fwd: linus.linux.sgi.com] dmanddmer
1999-01-19 23:28 ` dmanddmer
1999-01-20  1:29 ` Chad Carlin
1999-01-20  1:29   ` Chad Carlin
1999-01-20  2:04   ` job bogan
     [not found]     ` <job@piquin.uchicago.edu>
1999-01-20  2:28       ` Richard Offer
1999-01-20  2:36         ` Ken Klingman
1999-01-20  2:36           ` Ken Klingman
1999-01-20 21:18           ` David Watters
1999-01-20 21:18             ` David Watters
1999-01-20  3:01         ` job bogan
1999-01-20  3:01           ` job bogan
1999-01-20 21:29           ` David Watters
1999-01-20 21:29             ` David Watters
1999-01-20  3:08         ` Greg Chesson
1999-01-20  3:08           ` Greg Chesson
1999-01-20  3:32     ` Chad Carlin
1999-01-20 16:02     ` Eric Kimminau
1999-01-20 15:18 ` Eric Kimminau [this message]
1999-01-20 21:55   ` David Watters
1999-01-21  7:11   ` David S. Miller
1999-01-22 19:14     ` Jeffrey Watts

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=36A5F3DE.C94A0FA1@detroit.sgi.com \
    --to=eak@detroit.sgi.com \
    --cc=dmerchan@hiwaay.net \
    --cc=linux@cthulhu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.