Bug 113344 - Possible future extensions for SaX2 multiple monitor handling
Summary: Possible future extensions for SaX2 multiple monitor handling
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: SaX2 (show other bugs)
Version: unspecified
Hardware: Other All
: P5 - None : Enhancement
Target Milestone: ---
Assignee: Marcus Schaefer
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-26 15:11 UTC by Matthias Hopf
Modified: 2005-09-29 15:02 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Hopf 2005-08-26 15:11:09 UTC
1) For Xinerama configurations the display number should be shown in the
   tooltips of the monitors in the monitor layout scheme.
   An even better version would use different icons for the displays, but this
   is not really necessary, as Xinerama configurations are sort-of depricated.

2) The standard profile path /usr/share/sax/profile should be optional when
   specifying profiles with -b. It should be prepended whenever a profile name
   is given that does not contain any slashes.

3) When selecting a mergedfb profile with -b the external display cannot be
   configured because sax still doesn't know that it should actually display
   the according configuration options. It is unclear right now how this can
   be solved, but it would be great if the user could do that manually in case
   the card database is not up-to-date or he has a nonstandard modell.

4) For ease of configuration Meta profiles like 'xinerama.sh' and 'mergedfb.sh'
   should be created that automatically select and load the correct profile.
   E.g. sax2 -r -b xinerama on a GeForce card should load NVidia_Dualhead.
   Without 3) the use of mergedfb would be reduced to clone mode alone, but
   that is still better than nothing.
Comment 1 Marcus Schaefer 2005-09-15 10:25:26 UTC
- fixed 1) display number included to tooltip text 
- fixed 2) for example sax2 -b NVidia_DualHead is possible now 
Comment 2 Marcus Schaefer 2005-09-19 15:12:12 UTC
- 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 
Comment 3 Marcus Schaefer 2005-09-20 09:39:14 UTC
- 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 
Comment 4 Matthias Hopf 2005-09-29 15:02:53 UTC
Thanks Marcus :)))