[PATCH weston 0/5] fix fbdev transforms
Thilo Cestonaro
thilo at cestona.ro
Wed Mar 18 02:56:55 PDT 2015
hey!
rewind to 1.7.0 and added Dereks patches and mine, to have fbdev
compositor recognize my pixman type, and FBDev (transform) with touch is
working awesome.
I'm not sure what breaks touchscreen when I forward to master HEAD +
Dereks and mine patches.
Thilo.
Am 18.03.2015 10:29, schrieb Thilo Cestonaro:
> Hey Derek!
>
> Wow that was fast! :).... and the rotation is working now with fbdev!
> Thank you!
>
> But at least here, the touch isn't working anymore, altough the touch
> was recognized as input device (Touchscreen)
>
> -----------------------------
> Date: 2015-03-18 CET
> [10:25:45.253] weston 1.7.90
> http://wayland.freedesktop.org
> Bug reports to:
> https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.7.90
> Build: 1.7.0-68-g7f5a276 compositor-fbdev: fix output
> transformations (2015-03-18 10:06:07 +0100)
> [10:25:45.254] OS: Linux, 3.14.10, #50 SMP Mon Mar 16 15:53:42 CET
> 2015, armv7l
> [10:25:45.256] Using config file '/home/leo/.config/weston.ini'
> [10:25:45.262] Loading module '/usr/lib/weston/fbdev-backend.so'
> [10:25:45.315] initializing fbdev backend
> [10:25:45.324] Creating fbdev output.
> [10:25:45.325] Opening fbdev frame buffer.
> [10:25:45.325] Calculating pixman format from:
> - type: 0 (aux: 0)
> - visual: 2
> - bpp: 24 (grayscale: 0)
> - red: offset: 0, length: 8, MSB: 0
> - green: offset: 8, length: 8, MSB: 0
> - blue: offset: 16, length: 8, MSB: 0
> - transp: offset: 0, length: 0, MSB: 0
> [10:25:45.325] Mapping fbdev frame buffer.
> [10:25:45.325] fbdev output 480×272 px
> guessing 60 Hz and 96 dpi
> [10:25:45.329] input device 'Atmel maXTouch Touchscreen',
> /dev/input/event1 is tagged by udev as: Touchscreen
> [10:25:45.329] input device 'Atmel maXTouch Touchscreen',
> /dev/input/event1 is a touch device
> [10:25:45.331] input device 'HID 1267:0103', /dev/input/event2 is
> tagged by udev as: Keyboard
> [10:25:45.331] input device 'HID 1267:0103', /dev/input/event2 is a
> keyboard
> [10:25:45.335] input device 'HID 1267:0103', /dev/input/event3 is
> tagged by udev as: Keyboard
> [10:25:45.335] input device 'HID 1267:0103', /dev/input/event3 is a
> keyboard
> [10:25:45.344] input device 'd3355_pwrbtn_input', /dev/input/event0 is
> tagged by udev as: Keyboard
> [10:25:45.344] input device 'd3355_pwrbtn_input', /dev/input/event0 is
> a keyboard
> [10:25:45.345] launching '/usr/lib/weston/weston-keyboard'
> [10:25:45.741] Compositor capabilities:
> arbitrary surface rotation: yes
> screen capture uses y-flip: yes
> presentation clock: CLOCK_MONOTONIC_RAW, id 4
> [10:25:45.748] Loading module '/usr/lib/weston/desktop-shell.so'
> [10:25:45.778] launching '/usr/lib/weston/weston-desktop-shell'
> -----------------------------
>
> I just want to compare performance of the drm backend to fbdev
> backend. So not that important.
>
> Regards,
>
> Thilo
>
>
> Am 17.03.2015 19:22, schrieb Derek Foreman:
>> fbdev transforms are currently broken, and can only be enabled by
>> changing
>> code. This series enables it in the config file (after adding an
>> output
>> name so it can be specified there).
>>
>> There's also some other output name stuff in here as well. I have a
>> second
>> keyboard and mouse configured on a different seat and that causes a
>> crash
>> at startup.
>>
>> Derek Foreman (5):
>> compositor-fbdev: give the output a name
>> input: don't assume outputs have names
>> compositor-rpi: give the output a name
>> compositor-fbdev: allow configuring transform in the ini file
>> compositor-fbdev: fix output transformations
>>
>> src/compositor-fbdev.c | 125
>> ++++++++++++++-----------------------------------
>> src/compositor-rpi.c | 1 +
>> src/libinput-seat.c | 3 +-
>> 3 files changed, 37 insertions(+), 92 deletions(-)
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/wayland-devel
More information about the wayland-devel
mailing list