> Well, technically, you're right. A "tapeout" is any time you send the database to the fab.
> (The same physical thing happens...somebody FTPs a netlist to the fab)
At great risk of humiliating myself, I think in this case, NVidia taped out a layout-file (GDSII) instead of a gate netlist. TSMC/UMC don't offer much (or anything) in the way of layout services, and for a design of the NV30's complexity, NVidia most certainly handled all aspects of design up to the complete die layout (transistor sizing and placement, interconnect routing, etc.)
Other foundries (like TI, NEC, IBM, LSI, etc.) offer full 'back-end' services. As a customer, you would 'hand-off' a gate-netlist (a logical representation of your design, in terms of boolean functions AND/OR/XOR/NOT/etc.) Then the foundry would carry the design the rest of the way (conversion of gates into transistors layout, place/route, design-rule-check, etc.)
The trade-off for the customer is the following: In theory, customer pays higher price per fabbed die, in exchange for the foundry to handle more of the design-process's "physical issues" (layout, LVS/DRC, design-for-test and manufacturing test, etc.). In practice, many foundries fall short of this ideal. Sometimes the foundry's backend services are overbooked, and the layout-procedure ends up taking several months (instead of weeks). For *severe* physical problems (like one signal having to drive too many loads, becomes a critical path and causes the design to fail clock-frequency goal), the foundry can't resolve by itself, because they require a design-change in the original netlist. Thus, the foundry has no choice but to throw the ball back into the customer's court, and the back/forth takes time.
A coworker told me that the word 'tapeout' historically refers to the creation of a UNIX tar file, which was physically stored on a magnetic tape. Then the magnetic tape was shipped to the foundry. RussSchultz, is this explanation consistent with your experience?