[Fwd: xorg Digest, Vol 36, Issue 7]
Regina
regina.apel at gmx.de
Thu Jul 3 02:37:26 PDT 2008
-------- Original-Nachricht --------
Betreff: xorg Digest, Vol 36, Issue 7
Datum: Tue, 01 Jul 2008 14:10:47 -0700
Von: xorg-request at lists.freedesktop.org
Antwort an: xorg at lists.freedesktop.org
An: xorg at lists.freedesktop.org
Send xorg mailing list submissions to
xorg at lists.freedesktop.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freedesktop.org/mailman/listinfo/xorg
or, via email, send a message with subject or body 'help' to
xorg-request at lists.freedesktop.org
You can reach the person managing the list at
xorg-owner at lists.freedesktop.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of xorg digest..."
Today's Topics:
1. Re: Further notes on 7.4 (David Gerard)
2. Re: Constant DPI regardless of resolution (Nikos Chantziaras)
3. Re: Constant DPI regardless of resolution
(David De La Harpe Golden)
4. Re: Constant DPI regardless of resolution
(David De La Harpe Golden)
5. Re: Constant DPI regardless of resolution (Nikos Chantziaras)
6. Re: Constant DPI regardless of resolution (Felix Miata)
7. Re: synaptics touchpad. reconnect not supported ( Nicol? Chieffo )
8. Re: synaptics touchpad. reconnect not supported (Steven J Newbury)
9. Re: synaptics touchpad. reconnect not supported ( Nicol? Chieffo )
10. Re: synaptics touchpad. reconnect not supported (Steven J Newbury)
----------------------------------------------------------------------
Message: 1
Date: Tue, 1 Jul 2008 20:21:03 +0100
From: "David Gerard" <dgerard at gmail.com>
Subject: Re: Further notes on 7.4
To: xorg at lists.freedesktop.org
Message-ID:
<fbad4e140807011221wf926e1bg21ea4154e4f75008 at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
2008/7/1 Adam Jackson <ajax at nwnk.net>:
> On Mon, 2008-06-30 at 15:22 -0700, Dan Nicholson wrote:
>> - twm/xdm: Certainly legacy in the window/display manager world, but
>> it seems strange to install X without one of each. Also, the default
>> xinitrc runs twm, xclock and xterm, none of which would be available
>> with the core X installation.
> That's really just tempting me to remove startx from the list as well.
Put it all in a separate tarball called "classic," for those who still
treasure their O'Reilly X books ;-)
- d.
------------------------------
Message: 2
Date: Tue, 01 Jul 2008 22:37:31 +0300
From: Nikos Chantziaras <realnc at arcor.de>
Subject: Re: Constant DPI regardless of resolution
To: xorg at freedesktop.org
Message-ID: <g4e11v$o39$1 at ger.gmane.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Nicolas Mailhot wrote:
> Le Mar 1 juillet 2008 05:10, Nikos Chantziaras a ?crit :
>> David De La Harpe Golden wrote:
>>> Nikos Chantziaras wrote:
>>>
>>>> The DPI does not change (only the resolution changes.)
>>> Terminology: DPI measures the resolution...
>> Sorry, I should have clarified; with "resolution" I mean the width and
>> height of the picture in pixels. Changing those on a DFP that always
>> operates at a fixed native resolution won't change the DPI value
>
> The DPI you see in software in the DPI it controls. Any auto-scaling
> done by the hardware behind its back is beyond the software control.
>
> What you really want with a DFP is to always operate it at native
> resolution without this kind of scaling, which requires for the
> software ot be able to adapt to this resolution (whatever it is)
> without trying to force bogus values such as 96dpi.
But this is exactly what I'm doing. The DFP always operates at its
native resolution, it's the X server's driver (I guess) that assumes it
doesn't. If I had set the DFP to scale the picture, then the current
behavior would be correct (this is the most suitable behavior for the
majority of cases; users want the picture to fill the whole area of the
monitor). But if the DFP is set to not scale, then that behavior is not
correct anymore.
It seems what is really needed is a flag somewhere to switch between the
two behaviors. I don't think this can be auto-detected; X has no way of
knowing if the DFP is configured to scale or not.
With VMs, this is also an issue with *any* display, not only DFPs,
because X runs in a window. Changing the resolution in X will simply
resize the VM's window thus keeping the DPI constant; however, X assumes
the picture is always full-screen and thus the problem arises.
My next try on this was to force the DPI in the font renderer. The most
obvious way would be to put "Xft.dpi: 86" in ~/.Xresources. Doesn't
work though, but I guess this is off-topic here.
------------------------------
Message: 3
Date: Tue, 01 Jul 2008 20:38:13 +0100
From: David De La Harpe Golden <david.delaharpe.golden at gmail.com>
Subject: Re: Constant DPI regardless of resolution
To: Nicolas Mailhot <nicolas.mailhot at laposte.net>
Cc: Nikos Chantziaras <realnc at arcor.de>, xorg at freedesktop.org
Message-ID: <486A87A5.9000105 at googlemail.com>
Content-Type: text/plain; charset=UTF-8
Nicolas Mailhot wrote:
> The DPI you see in software in the DPI it controls. Any auto-scaling
> done by the hardware behind its back is beyond the software control.
>
> What you really want with a DFP is to always operate it at native
> resolution without this kind of scaling,
I'd agree, but note that one of Nikos' use cases was e.g. using a
vmware x server, which appears as a window on a real display. In that
case, when the window is resized (by changing the _virtual_ screen
size), you do need to be able to force a particular dpi for accurate
results, assuming vmware is displaying 1 virtual pixel
: 1 physical pixel (as it usually does AFAIK), or an *in-vm* 10 point
font wouldn't be 10 point on screen anymore.
Similar concerns would presumably apply to e.g. Xnest or Xephyr.
------------------------------
Message: 4
Date: Tue, 01 Jul 2008 20:39:36 +0100
From: David De La Harpe Golden <david.delaharpe.golden at gmail.com>
Subject: Re: Constant DPI regardless of resolution
To: Nicolas Mailhot <nicolas.mailhot at laposte.net>
Cc: Nikos Chantziaras <realnc at arcor.de>, xorg at freedesktop.org
Message-ID: <486A87F8.7070101 at googlemail.com>
Content-Type: text/plain; charset=UTF-8
Nicolas Mailhot wrote:
> The DPI you see in software in the DPI it controls. Any auto-scaling
> done by the hardware behind its back is beyond the software control.
>
> What you really want with a DFP is to always operate it at native
> resolution without this kind of scaling,
I'd agree, but note that one of Nikos' use cases was e.g. using a
vmware x server, which appears as a window on a real display. In that
case, when the window is resized (by changing the _virtual_ screen
size), you do need to be able to force a particular dpi for accurate
results, assuming vmware is displaying 1 virtual pixel
: 1 physical pixel (as it does AFAIK), or you'd get behaviour that
would keep only the likes of a certain Glynn happy :-)
Similar concerns would presumably apply to e.g. Xnest or Xephyr.
------------------------------
Message: 5
Date: Tue, 01 Jul 2008 22:47:15 +0300
From: Nikos Chantziaras <realnc at arcor.de>
Subject: Re: Constant DPI regardless of resolution
To: xorg at freedesktop.org
Message-ID: <g4e1k7$q7l$1 at ger.gmane.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Keith Packard wrote:
> On Tue, 2008-07-01 at 06:10 +0300, Nikos Chantziaras wrote:
>
>> I'm on VESA for running natively and xf86-vmware for running in a VM. I
>> was hoping for a "set and forget" option either in xorg's arguments or
>> xorg.conf rather than having to open the CLI and call xrandr each time I
>> switch resolution.
>
> RandR 1.2 passes the physical screen size from the client to the X
> server whenever the pixel size is set. If you want to fix the DPI,
> you'll need to fix whatever tool you use that sets the screen size.
I'm not really sure who is responsible for fixing it. A fixed DPI means
that the physical screen dimensions are not constant. Currently the X
server assumes those dimensions are constant. With good reason; there
aren't any monitors out there made of gum (yet?) However, with DFPs
that are set not to scale, the wanted behavior is really that of a
stretchy monitor made of gum. It's like disconnecting the bigger
display and connecting a smaller one while X runs (without restarting).
The only thorough way of fixing it IMO is a setting in the X server that
basically says "trust the user; don't be smart in calculating DPI;
simply trust what the user said and keep DPI constant no matter what."
------------------------------
Message: 6
Date: Tue, 01 Jul 2008 15:48:23 -0400
From: Felix Miata <mrmazda at ij.net>
Subject: Re: Constant DPI regardless of resolution
To: xorg at freedesktop.org
Message-ID: <486A8A07.7070306 at ij.net>
Content-Type: text/plain; charset=ISO-8859-1
On 2008/07/01 22:37 (GMT+0300) Nikos Chantziaras apparently typed:
> My next try on this was to force the DPI in the font renderer. The most
> obvious way would be to put "Xft.dpi: 86" in ~/.Xresources. Doesn't
> work though
Any time I wanted to set a local Xft.dpi, I put it in ~/.Xdefaults. Probably
depends on distro. In some, /etc/X11/Xresources is a file, in others, a
directory. I wish Xorg would dictate more consistency for things like this.
--
"Where were you when I laid the earth's
foundation?" Matthew 7:12 NIV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://fm.no-ip.com/
------------------------------
Message: 7
Date: Tue, 1 Jul 2008 22:33:23 +0200
From: " Nicol? Chieffo " <84yelo3 at gmail.com>
Subject: Re: synaptics touchpad. reconnect not supported
To: "Paul Vojta" <vojta at math.berkeley.edu>
Cc: xorg at lists.freedesktop.org
Message-ID:
<641322f90807011333k7bf96ddbk82484febe98e6af1 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Originally I don't have any udev rule about the touchpad, and I think
that my touchpad is PS2 so I will try with "synaptics-ps2".
And my xorg.conf has the device line set to /dev/psaux.
I'm now configuring it as you told me, let's hope it will work!
I will let you know soon!
thanks
On Tue, Jul 1, 2008 at 8:43 PM, Paul Vojta <vojta at math.berkeley.edu> wrote:
> On Mon, Jun 30, 2008 at 04:26:25PM +0200, Nicol? Chieffo wrote:
>> I have a laptop that has a problem with the touchpad: if hitting a key
>> combination the synaptics touchpad loses the synchronization and it
>> reconnects.
>> this is the log output in kern.log:
>>
>> psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
>> psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
>> psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
>> psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
>> psmouse.c: TouchPadat isa0060/serio1/input0 lost sync at byte 1
>> psmouse.c: issuing reconnect request
>> Synaptics Touchpad, model: 1, fw: 6.3, id: 0x1a0b1, caps: 0xa04713/0x200000
>> input: SynPS/2 Synaptics TouchPad as /class/input/input19
>>
>> The windows driver is smarter, and can handle device disconnections,
>> while the synaptics xorg driver (I have version 0.14.6) once the
>> device is disconnected, it treats it as a normal mouse after the
>> reconnection (no scroll, different acceleration, no finger
>> combinations,...)
>
> The problem is that the touchpad is getting assigned a different number
> after reconnecting.
>
> This can be fixed by the following (suggested by Stefan Monnier):
>
> 1 - use a udev rule so that the touchpad is always available as
> /dev/input/touchpad:
>
> kernel=="event*", DRIVERS=="synaptics-usb", SYMLINK+="input/touchpad"
>
> 2 - Force the synaptics driver to use that special device name:
>
> Option "Device" "/dev/input/touchpad"
>
> You might need to adapt the DRIVERS line if your touchpad is not USB.
>
> --Paul Vojta, vojta at math.berkeley.edu
>
------------------------------
Message: 8
Date: Tue, 01 Jul 2008 21:45:58 +0100
From: Steven J Newbury <steve at snewbury.org.uk>
Subject: Re: synaptics touchpad. reconnect not supported
To: Nicol? Chieffo <84yelo3 at gmail.com>
Cc: xorg at lists.freedesktop.org
Message-ID:
<1214945158.15478.87.camel at infinity.southview.snewbury.org.uk>
Content-Type: text/plain; charset=ISO-8859-1
On Tue, 2008-07-01 at 22:33 +0200, Nicol? Chieffo wrote:
> Originally I don't have any udev rule about the touchpad, and I think
> that my touchpad is PS2 so I will try with "synaptics-ps2".
> And my xorg.conf has the device line set to /dev/psaux.
> I'm now configuring it as you told me, let's hope it will work!
> I will let you know soon!
> thanks
>
> On Tue, Jul 1, 2008 at 8:43 PM, Paul Vojta <vojta at math.berkeley.edu> wrote:
> > On Mon, Jun 30, 2008 at 04:26:25PM +0200, Nicol? Chieffo wrote:
> >> I have a laptop that has a problem with the touchpad: if hitting a key
> >> combination the synaptics touchpad loses the synchronization and it
> >> reconnects.
> >> this is the log output in kern.log:
> >>
> >> psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
> >> psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
> >> psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
> >> psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
> >> psmouse.c: TouchPadat isa0060/serio1/input0 lost sync at byte 1
> >> psmouse.c: issuing reconnect request
> >> Synaptics Touchpad, model: 1, fw: 6.3, id: 0x1a0b1, caps: 0xa04713/0x200000
> >> input: SynPS/2 Synaptics TouchPad as /class/input/input19
> >>
> >> The windows driver is smarter, and can handle device disconnections,
> >> while the synaptics xorg driver (I have version 0.14.6) once the
> >> device is disconnected, it treats it as a normal mouse after the
> >> reconnection (no scroll, different acceleration, no finger
> >> combinations,...)
> >
> > The problem is that the touchpad is getting assigned a different number
> > after reconnecting.
> >
> > This can be fixed by the following (suggested by Stefan Monnier):
> >
> > 1 - use a udev rule so that the touchpad is always available as
> > /dev/input/touchpad:
> >
> > kernel=="event*", DRIVERS=="synaptics-usb", SYMLINK+="input/touchpad"
> >
> > 2 - Force the synaptics driver to use that special device name:
> >
> > Option "Device" "/dev/input/touchpad"
> >
> > You might need to adapt the DRIVERS line if your touchpad is not USB.
Alternatively you could use a HAL rule in /etc/hal/fdi/policy/ to allow
the touchpad to hotplug. I've posted a suitable fdi rule to this list
before if you check the archives.
------------------------------
Message: 9
Date: Tue, 1 Jul 2008 22:49:35 +0200
From: " Nicol? Chieffo " <84yelo3 at gmail.com>
Subject: Re: synaptics touchpad. reconnect not supported
To: "Steven J Newbury" <steve at snewbury.org.uk>
Cc: xorg at lists.freedesktop.org
Message-ID:
<641322f90807011349w2724d8c5ge0cc6aa16ee601a9 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
I will check. Did you post it exactly for the same problem I have?
------------------------------
Message: 10
Date: Tue, 01 Jul 2008 22:10:32 +0100
From: Steven J Newbury <steve at snewbury.org.uk>
Subject: Re: synaptics touchpad. reconnect not supported
To: Nicol? Chieffo <84yelo3 at gmail.com>
Cc: xorg at lists.freedesktop.org
Message-ID:
<1214946632.15478.89.camel at infinity.southview.snewbury.org.uk>
Content-Type: text/plain; charset="iso-8859-1"
On Tue, 2008-07-01 at 22:49 +0200, Nicol? Chieffo wrote:
> I will check. Did you post it exactly for the same problem I have?
Pretty much, but to save you looking...
Obviously you'll need to change the options for your own setup.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 10-x11-input.fdi
Type: application/xml
Size: 1973 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/xorg/attachments/20080701/586ed7cd/attachment.wsdl
------------------------------
_______________________________________________
xorg mailing list
xorg at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
End of xorg Digest, Vol 36, Issue 7
***********************************
More information about the xorg
mailing list