[cc'ed xwin-discuss, since that's where you can find the people who work
 on Xorg & talk to the people at nvidia who work on nvidia-settings.  Not
 sure why you asked install-discuss, since neither of these configuration
 programs are part of OS install.]

dick hoogendijk wrote:
> The xorg.conf file generated by Xorg (snv_99) has some important
> differences from the one generated by nvidia-settings.
> 
> <xorg>
> Section "Module"
>       Load  "record"
>       Load  "glx"
>       Load  "xtsol"
>       Load  "dbe"
>       Load  "dri"
>       Load  "IA"
>       Load  "GLcore"
>       Load  "xtrap"
>       Load  "extmod"
>       Load  "freetype"
> EndSection
> </xorg>
> 
> <nvidia>
> # nvidia-settings:
> Section "Module"
>     Load           "dbe"
>     Load           "extmod"
>     Load           "type1"
>     Load           "IA"
>     Load           "bitstream"
>     Load           "xtsol"
>     Load           "glx"
> EndSection
> </nvidia>


Other than the ordering, the difference seems to be these modules:
 - record, xtrap
        Not sure why we load these by default or nvidia doesn't, few things
        outside of test harnesses use them.

 - dri
        Only works with intel & radeon graphics, so nvidia's config file
        just doesn't bother loading a module that will fail to init and
        unload itself.

 - GLcore
        Part of the Mesa version of OpenGL, nvidia uses its own OpenGL instead.

 - freetype vs bitstream
        Solaris 10 & earlier Nevada builds used the bitstream font engine.
        Current Nevada/Indiana switched to freetype and Xorg automatically
        translates bitstream to freetype when reading config files so that
        users who upgrade from older releases don't break.   nvidia still
        uses bitstream so that they can ship something that works on all
        supported Solaris 10 & Nevada releases.

> Why are those modules so different? And who is correct?

Except for the first two, it seems like both are correct for the given hardware.

> Some other differences that strike me are:
> 
> <xorg>
> Section "InputDevice"
>       Identifier  "Mouse0"
>       Option      "ZAxisMapping" "4 5 6 7"
> EndSection

> <nvidia>
> Section "InputDevice"
>     Option         "Emulate3Buttons" "no"
>     Option         "ZAxisMapping" "4 5"
> EndSection

Looks like nvidia needs to fix their config file.
ZAxisMapping handles scroll wheels on mice.  "4 5" maps
to the vertical scroll wheel found on most mice, "6 7"
adds horizontal scroll found on some mice (by tilting
the wheel or a second wheel), so nvidia isn't enabling
horizontal scroll on mice that have it.

Also, they're forcing 3rd button emulation off (i.e.
press both buttons on a two button mice to simulate
button 3 - since most mice these days have the wheel
as a third button, this will mainly affect users with
laptops with only two buttons on the trackpad/joystick),
while Xorg leaves it in auto-detect mode, disabling when
a third button is detected.

> <xorg>
> Section "Device"
>       Identifier  "Card0"
>       Driver      "nvidia"
>       VendorName  "nVidia Corporation"
>       BoardName   "G70 [GeForce 7300 GT]"
>       BusID       "PCI:6:0:0"
> EndSection
> </xorg>
> 
> <nvidia>
> Section "ServerFlags"
>     Option         "Xinerama" "0"
> EndSection
> 
> 
> Section "Device"
>     BoardName      "GeForce 7300 GT"
> EndSection
> </nvidia>

I don't know why nvidia has different contents there.
It especially seems strange to have a device section
without Identifier or Driver.

-- 
        -Alan Coopersmith-           alan.coopersmith at sun.com
         Sun Microsystems, Inc. - X Window System Engineering


Reply via email to