this post was submitted on 25 Oct 2024
12 points (100.0% liked)

RetroGaming

19491 readers
202 users here now

Vintage gaming community.

Rules:

  1. Be kind.
  2. No spam or soliciting for money.
  3. No racism or other bigotry allowed.
  4. Obviously nothing illegal.

If you see these please report them.

founded 1 year ago
MODERATORS
 

I remember one post from a lot of years ago, in some web I can not remember, about Nintendo 64 manufacture history. I remember that it said that Sillicom Graphics (SGI) had heavy issues during the design/manufacture of the N64 RCP coprocessor. Because of this, finally this chip was made by other company, not SGI.

Recently I looked for that post but could not find it. I read other posts about this history but none talks about this SGI issue thing.

Does somebody know anything about this? Maybe is just me remembering it wrong.

top 6 comments
sorted by: hot top controversial new old
[–] [email protected] 8 points 1 week ago (1 children)

Says here SGI demoed the coprocessor to both Nintendo and Sega. Sega bowed out after their engineers found / perceived problems with the SGI design. I do not remember any behind the scenes article about the realtionship between Nintendo and SGI but having heard a lot of stories, I suspect the read would be entertaining ...

[–] [email protected] 1 points 1 week ago
[–] [email protected] 3 points 1 week ago* (last edited 1 week ago) (1 children)

SGI only made the RCP, Reality CoProcessor.

NEC (who sold the PC Engine, PC-FX consoles and the PC-98XX series home computers at the time) licensed the MIPS R4200 CPU designs from MTI. They then created the derivative CPU the N64 used, the MIPS VR4300i.

[–] [email protected] 1 points 1 week ago

You are right about the RCP. I fixed the op. Thanks.

[–] [email protected] 3 points 1 week ago (1 children)

It's basically an NEC VR4300. Produced by NEC based on a MIPS R4300i.

https://n64brew.dev/wiki/VR4300

[–] [email protected] 2 points 1 week ago

Sorry, I was talking about the RCP, not CPU. I already fixed the OP. Thanks anyway.