[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freedesktop-xorg
Subject:    Re: Re: Different output between xrandr and xdpyinfo
From:       "limh () sunray ! cn" <limh () sunray ! cn>
Date:       2020-11-19 9:33:39
Message-ID: 2020111917333883934231 () sunray ! cn+A640D08AD77E934B
[Download RAW message or body]

Thanks  Brother

    Yes, as you said,I used "xinput set-prop 7 --type=float "Coordinate \
Transformation Matrix" 0.348 0 0 0 0.71 0 0 0 1" to make the touchscreen fixed.  \
Because the configuration in "xorg.conf" is fixed too and have some mistakes. the \
cursor is a cross on the second screen and I can't move the windows to the second \
screen.

    I will try using this  touchscreen-transform.
    
    But I have to fix the problem that there is only one screen(DISP3 BG)：

    root@imx6qsabresd:~# xrandr                                                       \
  Screen 0: minimum 240 x 240, current 1024 x 768, maximum 8192 x 8192
    DISP3 BG connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x \
0mm  U:1024x768p-59  59.91*+    

Regards
Mihan
--------------
limh@sunray.cn
> Hi,
> 
> 2020. 11. 18. 2:47 keltezéssel, limh@sunray.cn írta:
> > Hi
> > I'm using hdmi and lvds with touch screen. But the touch screen can move the \
> > pointer between two monitors like the picture now.png.
> > But I want my touch screen to be applied on lvds like I want.png
> > So I follow arch wiki to set the configuration. But I found xrandr showed only \
> > one screen: root@imx6qsabresd:~# xrandr
> > Screen 0: minimum 240 x 240, current 1024 x 768, maximum 8192 x 8192
> > DISP3 BG connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x \
> > 0mm 1024x768_60.00  59.92*+
> > 
> > xdpyinfo showed two screens.
> > Here is xdpyinfo's output and /etc/X11/xorg.conf
> > 
> > Also, I found the HDMI screen's cursor is a cross(the same as  'X').
> > 
> > How to solve these problems?
> 
> you can run "xinput map-to-output ..." command after
> starting X but it's not persistent and if the touchscreen
> is a USB device, the setting doesn't survive hotplugging.
> 
> The way I solved it was with fixed configuration
> using a template file with "sed" substitutions and
> this utility: https://github.com/zboszor/touchscreen-transform
> 
> For example, this configuration template snippet is used
> for a specific touchscreen and a script that runs before
> starting X substitutes "@TRANSMATRIX@" with the output of
> this "touchscreen-transform" command:
> 
> Section "InputClass"
> 	Identifier "INTERNAL_TS"
> 	MatchIsTouchscreen "on"
> 	MatchProduct "eGalax Inc. eGalaxTouch P80H84 2072 v00_T3 k4.08.165"
> 	Driver "libinput"
> 	Option "TransformationMatrix" "@TRANSMATRIX@"
> EndSection
> 
> This does work if the USB touchscreen is hotplugged.
> 
> The "touchscreen-transform" program expects the list of
> screen resolutions and assumes they are located side by side.
> It doesn't care if you use separate X screens or Xinerama.
> The TransformationMatrix values are identical.
> 
> Obviously you need to know the screen resolutions in advance.
> Monitor-hotplugging is not supported, as it also need the
> touchscreen's TransformationMatrix values to be reset.
> 
> Regards,
> Zoltán Böszörményi
> 
> > 
> > Regards
> > Mihan
> > 
> > _______________________________________________
> > xorg@lists.x.org: X.Org support
> > Archives: http://lists.freedesktop.org/archives/xorg
> > Info: https://lists.x.org/mailman/listinfo/xorg
> > Your subscription address: %(user_address)s
> > 
> 
> 
_______________________________________________
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s


[prev in list] [next in list] [prev in thread] [next in thread]