Cheap composite tbc recommendation for O2 capture

Video, software tools and techniques on SGI systems.
Forum rules
Any posts concerning pirated software or offering to buy/sell/trade commercial software are subject to removal.
User avatar
jodys
Donor
Donor
Posts: 129
Joined: Tue Feb 06, 2007 1:33 am
Location: Denver, CO

Re: Cheap composite tbc recommendation for O2 capture

Unread postby jodys » Sat Jul 05, 2014 8:09 pm

robespierre wrote:the Crime chip (CRM) is like the "northbridge" of the O2. it accepts requests from the CPU and the other I/O chips and buffers them to the memory. It also contains the OpenGL accelerator component, unimaginatively called the "Rendering Engine", which is like the Indy's XL graphics (no geometry engine).
the VICE chip sits on the same bus as the CPU (SysAD bus), which limits its usefulness somewhat, since they both share the same path to main memory. Furthermore, they are not cache-coherent with one another.


I wouldn't class the O2 graphics as just another XL. Clearly it doesn't have a fully accelerated 3D pipeline, but there are compelling differences from the XL. MRE being able to do color space conversions is one of them. The VICE is available to perform some pretty substantial imaging calculations is another. I think that really the O2 is a memory controller with some coprocessors, just look at the diagram in the technical report. This is great when you are using VICE or fully utilizing the rendering engine, but not so great when you want maximum CPU speed. Hence the well documented underperformance of the R10/12k in the O2.

The VICE and the CPU are not cache coherent but I don't think that is really necessary for their purposes. If your MSP is processing GBs of data sequentially do you really want to keep a cache coherent?

I think what limits the VICE is not a shared bus but the sheer complexity of making it work. A driver and library would already handle loading ucode and allocating buffers, but you'd be writing two different bits of assembly, both of which need to be less than 4k and both of which are different dialects of MIPS. Furthermore, each chip has loads of quirks and probably bugs.
:Octane2: :Indy: :O2: :O2: :O3x0: :Indigo2IMP:

robespierre
Posts: 1579
Joined: Mon Sep 12, 2011 2:28 pm
Location: Boston

Re: Cheap composite tbc recommendation for O2 capture

Unread postby robespierre » Sun Jul 06, 2014 6:13 pm

I agree the VICE is neat, but it is also quite slow (I think that both versions use a 66MHz clock). And accommodating the VICE makes the R12k's interface to the system slow as well.
One thing that is intriguing about the O2 architecture is its similarity to the Ultra64 and its RCP. I wouldn't be shocked if there was unexplored potential there for graphical (or audio) emulation.
:PI: :O2: :Indigo2IMP: :Indigo2IMP:

User avatar
vishnu
Donor
Donor
Posts: 3189
Joined: Sun Mar 18, 2007 3:25 pm
Location: Minneapolis, Minnesota USA

Re: Cheap composite tbc recommendation for O2 capture

Unread postby vishnu » Mon Jul 21, 2014 3:27 pm

hamei wrote:
vishnu wrote:I remember there was a guy on ebay selling Octane Personal Video Option boards with instructions for getting them to work on Octane2s ...

I thought the Personal Video only worked on Mardi Gras graphics ? I know it has those three ribbon cable connections to the MXE, which don't exist on VPro ... the Octane Compression card supposedly does work with VPro, tho. Have one but never installed it so I can't say from personal experience ...

Yeah I remember the instructions for getting those ribbon cables to talk to the VPro were decidely non-trivial. :shock:
Project:
Temporarily lost at sea...
Plan:
World domination! Or something...

:Tezro: :Octane2:


Return to “SGI: Video”

Who is online

Users browsing this forum: No registered users and 1 guest