John Martin wrote:
> Garrett D'Amore wrote:
>>
>> "primary-card" is a terrible name -- how about "primary-display"
>> instead? (The primary display may be on the motherboard!)
>>
>> What is the purpose of this, is it for console support?
> No. It determines which graphics device on the system should
> be used as the default device for X, especially in the case where
> there are multiple graphics devices (not displays connected to a
> graphics device).
I'm assuming that this is only used when no explicit configuration is
present?
>
> It is independent of the console as the console may be a non-graphics
> device.
Okay, thanks for the clarification. I still think "primary-card" is a
bad name... although you might argue "primary-display" is also bad.
How about "primary-controller" or "primary-display-controller" ?
>>
>> How is the decision about whether a display the primary or not made?
>> Is this user-configurable? Does it access underlying BIOS
>> structures? What about in unconventional configurations, such as
>> display mirroring or TwinView?
> This is implementation defined. On x86, the default graphics device
> is the one for which the SBIOS has enabled I/O cycles on the entire
> devices path. Which device is chosen is usually controlled by a
> BIOS probe option. On SPARC, this will be the first graphics
> device in the tree which can be controlled by the probe-list words.
>
> Display mirroring or TwinView implies multiple displays
> driven of a single graphics device. Choosing between multiple
> displays connected to a single device is not the scope of this project.
>
Okay, that makes sense. Thanks.
- Garrett
