In older fedora versions I can do the following:
xinput --list
find my device: "Advanced Silicon S.A. CoolTouch(TM) System"
and can simply set the props I need with:
xinput set-prop 'Advanced Silicon S.A. CoolTouch(TM) System' --type=float 'Coordinate Transformation Matrix' 0.533333333333333, 0, 0.466666666666667, 0, 1, 0, 0, 0, 1
But now, xinput list did not show my any real devices, only some mystery generic ones as this:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ xwayland-pointer:14 id=6 [slave pointer (2)]
⎜ ↳ xwayland-relative-pointer:14 id=7 [slave pointer (2)]
⎜ ↳ xwayland-touch:14 id=9 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ xwayland-keyboard:14 id=8 [slave keyboard (3)]
So I only see some mystery wayland pseudo devices.
With libinput-list-devices I can see my touch device, but I can not find any documentation how I can configure devices for libinput. All docs tell my that it can be done with xinput with is not true for wayland on fedora. Any idea?
Q: How can I configure input devices on wayland in fedora 25.
Update fedora 33:
There is still no support for touch calibration in wayland nor gnome. If we see, that some distributions are plan to drop X11 and only support wayland, we will se the loss of linux touch display support.
In Wayland, input configuration is entirely up to the compositor/desktop environment (source). If your desktop (presumably Gnome) doesn't provide a way of doing some configuration, then that configuration can not be done. There tools to configure Gnome beyond the standard Gnome settings, such at gnome-tweek-tool, which may expose the options you want. There may even be config files you can edit, I'm not sure, but you definitely need a Gnome specific solution.
Related
Please apart from the 7" LCD touch screen, which other lcd screen can work with raspberry pi using windows iot core operating system
It is recommended to use the screen device which is listed in the Hardware compatibility list. As mentioned in the document, this list is not exhaustive. There are many other peripherals not listed on this page that are compatible with Windows 10 IoT Core. You may try with other screen, maybe it is also compatible. If you just want to use a display screen without touch input, in general the screen with HDMI interface is usable.
I'm creating an Android Things device using a Raspberry Pi 3, which will be connected to monitor. The monitor should be on all of the time, but I'd like a way to "turn off" the device (turning off the HDMI output so that the monitor can go to low-power standby mode) so that I can turn the device on and off remotely or with a timer, rather than having to manually push the monitor's power button.
Is there a way to control the Raspberry Pi's HDMI output (turn the display on or off) in an Android Things project?
How do I remap or retask pins in realtek drivers ver. 6.0.1(the latest drivers) in Windows 10?
I know there is something related to registry entries and modifying them, but they just don't apply after a restart. All I wanted to do is just reassign the blue and pink jacks on the back of my computer to be a headphone out and a mic in respectively, currently I have this setup:
Rear Blue: Line-In
Rear Green: Front Speakers
Rear Pink: Mic-In
The front green and front pink are not connected to the motherboard and in the driver settings there is no option besides the BIOS to disable them
I remapped my pins using the registry on Windows 8, but after upgrading to Windows 10, the settings had no effect any more. I found a way to configure it with the Realtek software:
Open Realtek HD Audio Manager (double click icon in tray)
You should see graphics of the pins at the right
Right-click the pin to remap and select first entry in the context menu
Select the desired function
Unfortunately, all settings are lost after a reboot. Maybe it is just an issue on my machine, because I have not done a fresh installation.
https://www.overclock.net/forum/6-intel-motherboards/378475-realtek-hd-audio-manager-universal-jack-retasking-ip35-pro-xe-4.html
It can't be done, anymore, without going back an older driver. The driver simply resets the values every time it is initialized.
Cannot access webcam from browser
My aim is to access a USB webcam (video / camera) device from any web browsers on OS X. Using Flash, I cannot see the USB webcam that is plugged in, switched on and active.
Similarly, I cannot detect the webcam video source using HTML5 getUserMedia() https://www.webrtc-experiment.com/DetectRTC/. Though the Audio stream from the USB device is listed
ImageSnap (Cocoa)
To verify if the USB device is in fact accessible in OSX, I use the open source tool ImageSnap .
$ imagesnap -l
Video Devices:
FaceTime HD Camera (Built-in)
Only the built-in iSight camera is detected, not the attached USB camera.
ImageSnap uses the Cocoa framework.
wacaw (Carbon)
Next, using wacaw, I can list out the attached USB camera, and even correctly take snapshots.
$ wacaw -L
DVFreeThread - CFMachPortCreateWithPort hack = 0x116970, fPowerNotifyPort= 0x1158d0
There are 5 devices in the list.
The current selection is 0.
0 - AVer Virtual Camera [is available] [has inputs]
There are 1 inputs for this device (0).
The current selection is 0.
0 - AVer Virtual Camera [is available]
1 - DV Video [is available] [has no inputs]
2 - IIDC FireWire Video [is available] [has no inputs]
3 - USB Video Camera for AverVision Digital Presenter 2 [is available] [has no inputs]
4 - USB Video Class Video [is available] [has inputs]
There are 1 inputs for this device (4).
The current selection is 0.
0 - FaceTime HD Camera (Built-in) [is available]
wacaw uses Carbon framework.
Problem
How can I make the USB camera accessible via Cocoa, which will also make it accessible through web browsers?
Obviously that camera needs a driver to make it work. Apps on Mac are running in 64-bit nowadays, and the carbon driver (should be implemented with sequence grabber framework) is 32-bit only.
It might work if the camera producer offers driver written with cocoa, or just use a UVC camera instead.
On linux / ubuntu, the keyboard and mouse devices are found
in /dev/input/by-path/
Where is the keyboard device mounted in osx?
I added a usb keyboard, and no devices got added in /dev folder.
Is it located somewhere else, or is it totally unaccessible?
Thanks.
Edit:
I was able to get some info on the keyboard using libusb:
046d:c315 (bus 26, device 3)
and usb prober in developer tools from apple...
however none of them mention a /dev special file or another way to access it.
OS X uses its own system to manage the PNP device tree, see http://developer.apple.com/mac/library/navigation/index.html?section=Topics&topic=Drivers%2C%20Kernel%2C%20%26amp%3B%20Hardware&kind=topic to get started