During the 80s, I ran a design company that was designing PCBs for a group
of engineers at Lawrence Livermore Labs for a super computer for the US
Navy. The team that eventually formed Rambus was on that project and
wanted us to design a transmission line whose impedance was 28 ohms, not
impossible, but not very practical.
The navy cancelled the project and that team went on to form Rambus.
We wondered at the time how practical the idea was. Time showed us.
-----Original Message-----
From: si-list-bounce@xxxxxxxxxxxxx [mailto:si-list-bounce@xxxxxxxxxxxxx] On
Behalf Of heyfitch (Redacted sender "heyfitch" for DMARC)
Sent: Tuesday, October 3, 2017 2:34 PM
To: si-list@xxxxxxxxxxxxx
Subject: [SI-LIST] Re: Keynote Speeches from EDICon Last month
Sent from my phone
On Oct 3, 2017, at 13:47, Lyndell Asbenson <Lyndell.Asbenson@xxxxxxxxxxx>
wrote:
Chris,
Regarding RAMBUS, it too had a lot of daemons. I have a wonderful plaque
celebrating our achievement in the Intel Chipset 820, and 840. The 840 was
the 1st Intel Workstation utilizing high speed RAMBUS memory. What we were
attempting to do is figure out how to test the chipsets with RAMBUS
interface in very high volume manufacturing. This brought us fact to face
with all kinds of SI challenges we had never before seen. And had a very
short time to figure out. We know we had to test it at speed, yet there was
no production tester fast enough to do the job. This required a new
technology in testing call flyby channel multiplexing.
Regards,
Lyndell Lee Asbenson
-----Original Message-----
From: si-list-bounce@xxxxxxxxxxxxx [mailto:si-list-bounce@xxxxxxxxxxxxx] On
Behalf Of Cheng, Chris
Sent: Monday, October 2, 2017 11:07 PM
To: si-list@freelists.
Subject: [SI-LIST] Re: Keynote Speeches from EDICon Last month
Funny you mention Merced while Scott was talking about RAMBUS. 460GX chipset
was using PC100 SDRAM, not RAMBUS.
Merced had a lot of daemons, RAMBUS was not one of it.
And I sat through the decision process in the other processor company when
Bill Joy and Andy Bechtolsheim overrule the engineers recommendation to use
RAMBUS.
They correctly realized that bandwidth per pin could not justified the
degraded performance due to increase in memory latency imposed by RAMBUS.
Speed and signal integrity was never a concern and I know both the engineer
responsible to make that happen in RAMBUS and the engineer in that
workstation company tasked to make sure it worked.
RAMBUS exist to address a simple problem at that time, highest bandwidth per
pin for cost sensitive application. And it had plenty of examples in
Nintando64 and PlayStation. And Intel always had an alternative as backup,
it's called ServerWorks.
Chris Cheng
Distinguished Technologist , Electrical
Hewlett-Packard Enterprise Company
+1 510 344 4439/ Tel
chris.cheng@xxxxxxx / Email
4209 Technology Dr
Fremont, CA 94538
USA
-----Original Message-----
From: si-list-bounce@xxxxxxxxxxxxx [mailto:si-list-bounce@xxxxxxxxxxxxx] On
Behalf Of Lee Ritchey
Sent: Monday, October 02, 2017 11:40 AM
To: Scott@xxxxxxxxxxxxx; si-list@xxxxxxxxxxxxx
Subject: [SI-LIST] Re: Keynote Speeches from EDICon Last month
Scott,
Almost makes me want to go out and become an engineer! Nice work!
Didn't know you lived through the Intel Merced disaster! Only time I ever
heard a CEO admit publicly that Intel had made that mistake. Craig Barret
did that.
I watched the Apollo landing because I had a radio on board. That design
was my first job out of college. Couldn't believe they gave such important
jobs to beginners! But, then, everyone on that project was a beginner at
designing those things!
Lee
-----Original Message-----
From: si-list-bounce@xxxxxxxxxxxxx [mailto:si-list-bounce@xxxxxxxxxxxxx] On
Behalf Of Scott McMorrow
Sent: Monday, October 2, 2017 10:02 AM
To: si-list@xxxxxxxxxxxxx
Subject: [SI-LIST] Keynote Speeches from EDICon Last month
https://www.signalintegrityjournal.com/articles/567-edi-con-usa-keynote-talk
s---bet-your-job-5g-in-5-years-and-tm-value
Scott McMorrow, CTO Signal Integrity Group Samtec Office 401-284-1827 |
+1-800-726-8329 www.samtec.com<http://www.samtec.com/>
This email and any appended documents are only for the intended
person/entity and may contain information of Samtec, Inc., that is
PRIVILEGED, PROPRIETARY, CONFIDENTIAL, AND/OR PROTECTED BY LAW. If you are
not the intended recipient you are hereby notified that any dissemination,
disclosure, use or copying of this email or its contents is prohibited. If
you received this message in error, please notify Samtec immediately and
delete the email, attachments and all copies. The intended recipient should
not disclose the content to third parties or reproduce the content without
Samtec's written consent.
------------------------------------------------------------------
To unsubscribe from si-list:
si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field
or to administer your membership from a web page, go to:
//www.freelists.org/webpage/si-list
For help:
si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field
List forum is accessible at:
http://tech.groups.yahoo.com/group/si-list
List archives are viewable at:
//www.freelists.org/archives/si-list
Old (prior to June 6, 2001) list archives are viewable at:
http://www.qsl.net/wb6tpu
------------------------------------------------------------------
To unsubscribe from si-list:
si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field
or to administer your membership from a web page, go to:
//www.freelists.org/webpage/si-list
For help:
si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field
List forum is accessible at:
http://tech.groups.yahoo.com/group/si-list
List archives are viewable at:
//www.freelists.org/archives/si-list
Old (prior to June 6, 2001) list archives are viewable at:
http://www.qsl.net/wb6tpu
------------------------------------------------------------------
To unsubscribe from si-list:
si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field
or to administer your membership from a web page, go to:
//www.freelists.org/webpage/si-list
For help:
si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field
List forum is accessible at:
http://tech.groups.yahoo.com/group/si-list
List archives are viewable at:
//www.freelists.org/archives/si-list
Old (prior to June 6, 2001) list archives are viewable at:
http://www.qsl.net/wb6tpu
------------------------------------------------------------------
To unsubscribe from si-list:
si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field
or to administer your membership from a web page, go to:
//www.freelists.org/webpage/si-list
For help:
si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field
List forum is accessible at:
http://tech.groups.yahoo.com/group/si-list
List archives are viewable at:
//www.freelists.org/archives/si-list
Old (prior to June 6, 2001) list archives are viewable at:
http://www.qsl.net/wb6tpu
.
------------------------------------------------------------------
To unsubscribe from si-list:
si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field
or to administer your membership from a web page, go to:
//www.freelists.org/webpage/si-list
For help:
si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field
List forum is accessible at:
http://tech.groups.yahoo.com/group/si-list
List archives are viewable at:
//www.freelists.org/archives/si-list
Old (prior to June 6, 2001) list archives are viewable at:
http://www.qsl.net/wb6tpu
------------------------------------------------------------------
To unsubscribe from si-list:
si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field
or to administer your membership from a web page, go to:
//www.freelists.org/webpage/si-list
For help:
si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field
List forum is accessible at:
http://tech.groups.yahoo.com/group/si-list
List archives are viewable at:
//www.freelists.org/archives/si-list
Old (prior to June 6, 2001) list archives are viewable at:
http://www.qsl.net/wb6tpu
