In the NuBus environment, the driver's primary initialization routine trims the supported display resolutions (functional sResources) to those that are available on the display that is sensed. This makes it difficult to support new displays, as possible supported resolutions might have been deleted by the card's primary initialization routine. The Display Manager now takes care of verifying that a particular resolution is supported by the current display, using GetModeConnection and GetTimingInfo.
The following sections detail what the different routines should do to implement the reporting of all possible display resolutions. See the previous section, Display Timing Modes, for background information on timing modes.