CB: It's not an arm's length relationship. We are close. We don't just
throw Apple a little package of binaries at the end of each day. Rather, we see 50% of their source code and they see 80% of ours. We sync up with each other's source depot every day or two. Sometimes it gets to several times a day. There are probably about 50 conversations a week with Apple engineers. Working with Apple is different than working with any other computer manufacturer. Basically we function as an extended part of their team. The only way to write drivers for the Mac is to work this way with Apple.
...
AFR: So what is specific today on the hardware side for the cards in the Mac Pros? They have industry standard connectors now.
CB: Not a lot on the hardware side. But EFI is a big difference on the
ROM side. Apple's early adoption of this Intel standard has also caused hardware vendors to create special boards just for that.
AFR: So there's not much unique on the hardware side today? EFI is also an Intel standard, should that mean that when Microsoft adopts EFI with Windows Vista and post-Vista, there will be even less of a difference remaining on hardware uniqueness?
CB: It is not clear when or if other PC vendors will adopt EFI, which I
think stands for "extensible firmware infrastructure". Virtually all
other PC graphics cards require a video BIOS, a different kind of
firmware than EFI and different again from OpenFirmware, the type
required by the Power Mac G5 and other PowerPC based Macs. This
distinction between the firmware, the control code typically programmed into a ROM on what otherwise might be identical hardware, determines the system compatibility and operating characteristics of each individual graphics card. It makes them unique from one another and unfortunately prevents the individual cards from being interoperable between one type of system and another--for example from a Power Mac G5 to a Mac Pro or from a Mac Pro to a typical Windows based PC.