|
Bugzilla – Full Text Bug Listing |
| Summary: | Possible future extensions for SaX2 multiple monitor handling | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Matthias Hopf <mhopf> |
| Component: | SaX2 | Assignee: | Marcus Schaefer <ms> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Matthias Hopf
2005-08-26 15:11:09 UTC
- fixed 1) display number included to tooltip text - fixed 2) for example sax2 -b NVidia_DualHead is possible now - fixed 3) I added a new cache section named SaXMeta. This section
may contain information about the multihead capabilities for different
situations. currently two keys are checked from within libsax:
1) SAX_NO_CDB_CHECK
2) SAX_NO_DUAL_MODE
----
the first on will prevent libsax from checking the CDB information and
simply use a driver -> DualHead_DriverOptions mapping. This one has been
made the default in init.pl which means every card using an appropriate
driver can be setup as dualhead card using the SaX GUI
Additionally each DualHead_DriverOptions profile has to set that value
for the sake of completeness
SaXMeta -> [X] -> SAX_NO_CDB_CHECK = 1
----
The second one will tell libsax that this card is not capable of dualhead
and can be used to fake a situation where one dualhead card should be handle
as two separate graphics cards. This is done in the old style DualHead
profiles. So each of these profiles have to include
SaXMeta -> [X] -> SAX_NO_DUAL_MODE = 1
This will cause the GUI not to display the dual mode checkbox because the
card is handled as Xinerama device
- fixed 4) you can call sax using the following command:
sax2 -b Xinerama
sax2 -b MergedFB
the first one will automatically select a standard DualHead profile if
possible the second will select a DualHead_DriverOptions profile if
possible
Thanks Marcus :))) |