Panel-location not working with Weston 2.0.0

[Keskinarkaus, Teemu]

Hi,

I have custom i.MX6 based HW that is running Linux 4.1.x with Weston 1.11.0. I 
recently updated it to Weston 2.0.0 and the panel-location option in Weston.ini 
- file doesn't work anymore.

I have this  in Weston.ini:
[shell]
panel-location="none"
background-color=0x
background-image="/opt/etc/weston-background.jpg"

The background-color and background-image - options works, but panel-location 
does nothing. I've tried to leave it empty and left/right etc.. but nothing. 
Panel stays there. At least the top left corner terminal-button is there and 
top right corner time display.

In Weston 1.11.0 those settings worked like expected (ie. the panel disappeared 
completely).

Have that setting changed somehow for Weston 2.0.0? I didn't find any 
documentation that it would have.

-Teemu Keskinarkaus



Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

Thank you.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

RE: [EXT] Re: VNC or RDP in Weston

[Keskinarkaus, Teemu]

Hi,

> -Original Message-
> From: wayland-devel [mailto:wayland-devel-boun...@lists.freedesktop.org] On
> Behalf Of Keskinarkaus, Teemu
>
> Any news about the RDP setup-instructions?
I made some progress here.

With these commands it tries to start the rdp-backend Weston.

winpr-makecert -rdp
export XDG_RUNTIME_DIR=/run/display
weston --backend=rdp-backend.so --rdp-tls-cert=$device.crt 
--rdp-tls-key=$device.key --width=1280 --height=800 --socket=wayland-1


[05:13:34.940] Starting with no config file.
[05:13:34.941] Output repaint window is 7 ms maximum.
[05:13:34.950] Loading module '/usr/lib/weston/rdp-backend.so'
[05:13:35.072] using FreeRDP version 1.2.5
[05:13:35.072] TLS support activated
[05:13:35:616] [1452:1452] [INFO][com.freerdp.core.listener] - Listening on 
0.0.0.0:3389
[05:13:35.081] Compositor capabilities:
   arbitrary surface rotation: yes
   screen capture uses y-flip: yes
   presentation clock: CLOCK_MONOTONIC_RAW, id 4
[05:13:35.082] Loading module '/usr/lib/weston/desktop-shell.so'
[05:13:35.082] launching '/usr/libexec/weston-keyboard'
[05:13:35.084] launching '/usr/libexec/weston-desktop-shell'
[05:13:35.127] Error: /usr/libexec/weston-desktop-shell apparently cannot run 
at all.
   Quitting...[05:13:35.127] input_method disconnected, 
respawning...
[05:13:35.127] launching '/usr/libexec/weston-keyboard'
Failed to process Wayland connection: Broken pipe
failed to create display: Broken pipe


What I understood the Weston-desktop-shell is something that Weston starts 
automatically and it cannot be started manually. I was wondering that does it 
try to create another desktop for some reason and not use the existing one? I 
did try start the Weston-desktop-shell manually and got expected(?) error: 
permission to bind desktop_shell denied.

Is there still something I'm missing from RDP setup or what might be the 
problem? Weston is running fine on desktop.

-Teemu




Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

Thank you.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

RE: [EXT] Re: VNC or RDP in Weston

[Keskinarkaus, Teemu]

-Original Message-
From: Pekka Paalanen [mailto:ppaala...@gmail.com]
Sent: 21. marraskuuta 2017 9:41
To: Keskinarkaus, Teemu; Hardening
Cc: wayland-devel@lists.freedesktop.org
Subject: [EXT] Re: VNC or RDP in Weston

On Tue, 21 Nov 2017 06:37:32 +
"Keskinarkaus, Teemu"  wrote:

> Hi,
>
> Just inquiring what is the state of the Wayland VNC and/or RDP
> support?
>
> We have i.MX6 based HW and atm. it's using Weston 1.11.x which I
> assume is way too old for VNC/RDP? Or is there backport for that?
>
> We are also working on Weston 2.0, but I haven't really been able to
> find if the VNC/RDP support is there (and working) and/or how to
> configure/use it.  Is it there and is it working and how to use it
> and/or is there any documentation how to do it?
>

Hi,

Weston has never had VNC support, but the RDP backend is quite long lived by 
now.

David, another call for those instructions on how to setup and test the 
RDP-backend. ;-)

[Teemu] Hi,

Any news about the RDP setup-instructions?

-Teemu




Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

Thank you.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

VNC or RDP in Weston

[Keskinarkaus, Teemu]

Hi,

Just inquiring what is the state of the Wayland VNC and/or RDP support?

We have i.MX6 based HW and atm. it's using Weston 1.11.x which I assume is way 
too old for VNC/RDP? Or is there backport for that?

We are also working on Weston 2.0, but I haven't really been able to find if 
the VNC/RDP support is there (and working) and/or how to configure/use it.  Is 
it there and is it working and how to use it and/or is there any documentation 
how to do it?

-Teemu Keskinarkaus



Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

Thank you.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

RE: Display rotation in Wayland/weston in imx6sx

[Keskinarkaus, Teemu]

Hi,

Okay, good news. After using the correct name (fbdev) the screen is rotated!

Yes, it's the FBDev/EGL why Weston 2.0 can't be used with iMX6.  After 
investigation I got impression that etnaviv is still quite much under 
development and that's why we choose to go with FBDev based solution. Not to 
say that later we wouldn't update to etnaviv based.

Also noticed from Weston-log that I'm using gl-renderer(egl?).

I tried building linux-fslc - based system with etnaviv, but ran problems with 
imx-gpu-viv - module still being built. There is external module for that that 
is referenced in meta-freescale files. I didn't find instructions how to build 
linux-fslc - based system, but I guess that's for another mailing list unless 
you have instructions somewhere how to do it I would appreciate link to it. I 
guess I could have started experimenting, but I don't know what kind of can of 
worms I'd have opened so decided against it.

-Teemu

-Original Message-
From: Pekka Paalanen [mailto:ppaala...@gmail.com]
Sent: 22. kesäkuuta 2017 12:05
To: Keskinarkaus, Teemu
Cc: Jomon John; wayland-devel@lists.freedesktop.org
Subject: Re: Display rotation in Wayland/weston in imx6sx

On Thu, 22 Jun 2017 07:56:15 +
"Keskinarkaus, Teemu"  wrote:

> Hi,
>
> I tried following lines in weston.ini (Also made sure weston actually
> loaded it.)
>
> [output]
> name=LCD
> mode=240x320
> transform=90
>
> I'm not sure what the name should be. Display is connected to parallel
> port (lcdif1, not LVDS). How can I check what name I should use?

Hi,

see Weston's log, the name appears there at least for the DRM backend.

For fbdev backend there is only one hardcoded name (as there can only ever be 
one output and that cannot be hotplugged): "fbdev". I suppose we have forgot to 
document that, but then again, the whole fbdev backend is undocumented...

> As I'm no Wayland/Weston expert I want to use backend/renderer that
> works. Currently the backend(I think) is FBDev since I'm using
> linux-fscl-imx - kernel. I think NXP officially doesn't support other
> atm. I'm not sure about renderer what I'm even using atm.

It will all be apparent in the Weston log, which it by default prints to 
stdout/err. Note, that if stdout/err is the same VT in which Weston will show 
up, you have to redirect to a file to see the log.

> I guess with this DRM/etnaviv I might be able to get Weston 2.0 work
> as it fixes one annoying bug. I can't do that with the official NXP
> FBdev driver.

Why do you think you cannot run Weston 2.0 fbdev backend? The fbdev backend is 
never a good idea if DRM is an option, just curious. Is it the EGL support that 
was ripped out?

I think with etnaviv you should aim for DRM-backend with the GL-renderer, which 
is what you will get by default. The issues I have heard of are with Wayland 
clients, so ensuring apps do not use hardware accelerated GL should get you 
going immediately. If that doesn't work for some reason, then DRM-backend with 
the Pixman renderer (--use-pixman command line argument) is the next best 
thing, avoiding the GPU completely. Fbdev falls far beyond in features.


Thanks,
pq



Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

Thank you.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

RE: Display rotation in Wayland/weston in imx6sx

[Keskinarkaus, Teemu]

Hi,

I tried following lines in weston.ini (Also made sure weston actually loaded 
it.)

[output]
name=LCD
mode=240x320
transform=90

I'm not sure what the name should be. Display is connected to parallel port 
(lcdif1, not LVDS). How can I check what name I should use?

As I'm no Wayland/Weston expert I want to use backend/renderer that works. 
Currently the backend(I think) is FBDev since I'm using linux-fscl-imx - 
kernel. I think NXP officially doesn't support other atm. I'm not sure about 
renderer what I'm even using atm.

I guess with this DRM/etnaviv I might be able to get Weston 2.0 work as it 
fixes one annoying bug. I can't do that with the official NXP FBdev driver.

-Teemu

-Original Message-
From: Pekka Paalanen [mailto:ppaala...@gmail.com]
Sent: 22. kesäkuuta 2017 10:45
To: Jomon John; Keskinarkaus, Teemu
Cc: wayland-devel@lists.freedesktop.org
Subject: Re: Display rotation in Wayland/weston in imx6sx

On Thu, 22 Jun 2017 06:50:11 +
Jomon John  wrote:

> Teemu,
>
> >>> There is rotate config(transform) option in Weston, but it did
> >>> nothing when tested. Is there a way to rotate the display in
> >>> Wayland that would work with iMX6 or is that something that is not
> >>> currently supported in that  combo? (Wayland + imx6).

Hi,

how exactly did you try that? I think it should work, but if you e.g.
used a wrong output name in weston.ini, it will get ignored.

Do mention which backend and renderer you want to use.

> >>
> >>Transform will work, i tried the same on i.mx6 (with DRM backend)
> >>and it was working, but you will need mainline kernel. Not sure
> >>whether you can do the same fbdev backend.

Are you sure of the kernel requirement? Weston should be using the composition 
to rotate the image. Kernel support is only necessary if one wants to hit the 
composite-bypass path if clients are not already rotating as well.

I would expect it to work for all of fbdev/pixman, DRM/pixman and DRM/GL.

> > At least quick glance to linux-fsl-imx - kernel menuconfig did show
> > DRM enabled, but that's pretty much it. No mention of NXP/Freescale
> > there. Only reason we are currently using Yocto 2.2 is that Yocto
> > 2.3 uses Weston 2.0 and at is it today the NXP does not provide
> > graphic drivers other than FBDev so I'm not sure how DRM would
> > work.
>
> The mainline got etnaviv, open source driver for vivante GPU also mesa
> got the necessary support for etnaviv. so you can use the mesa +
> etnaviv stack for DRI.
>
> > Is it accelerated?
>
> Not a graphics expert to make any comments, anyway it uses GPU :) .
> i am also trying out the DRI setup with wayland/weston.

I've asked around recently about that myself, and it seems that while Weston 
itself will be hardware accelerated ok, the support for Wayland clients is not 
complete yet. Clients will run, but even with the latest Mesa release, you will 
probably have tiling mismatch issues which cause the window to appear garbled. 
I hear the work to fix that is going on right now (support for pixel format 
modifiers).


Thanks,
pq



Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

Thank you.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

RE: Display rotation in Wayland/weston in imx6sx

[Keskinarkaus, Teemu]

Hi,

Thanks for quick answer.

So, when using Yocto it seems I need to move away from linux-fslc-imx - kernel 
and start using linux-yocto - kernel configured for iMX6 instead? Or can the 
linux-fslc-imx - kernel be configured for DRM backend or is that something 
possible only on mainline kernel? At least quick glance to linux-fsl-imx - 
kernel menuconfig did show DRM enabled, but that's pretty much it. No mention 
of NXP/Freescale there.

Only reason we are currently using Yocto 2.2 is that Yocto 2.3 uses Weston 2.0 
and at is it today the NXP does not provide graphic drivers other than FBDev so 
I'm not sure how DRM would work. Is it accelerated?

-Teemu Keskinarkaus

-Original Message-
From: Jomon John [mailto:jomon.j...@tataelxsi.co.in]
Sent: 22. kesäkuuta 2017 8:41
To: Keskinarkaus, Teemu; wayland-devel@lists.freedesktop.org
Subject: Re: Display rotation in Wayland/weston in imx6sx

Teemu,

> We have HW iMX6SoloX based HW running Yocto 2.2 and Wayland/Weston 1.11. 
> There is need to rotate the display 90 degrees. In X11 this wouldn't be a 
> problem since you could use xrandr. What I understood Wayland does not  
> support this method.

You are right, xrandr is the configuration utility for X

> There is rotate config(transform) option in Weston, but it did nothing when 
> tested. Is there a way to rotate the display in Wayland that would work with 
> iMX6 or is that something that is not currently supported in that  combo? 
> (Wayland + imx6).

Transform will work, i tried the same on i.mx6 (with DRM backend) and it was 
working, but you will need mainline kernel. Not sure whether you can do the 
same fbdev backend.

_
Best Regards
Jomon John



Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

Thank you.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

Display rotation in Wayland/weston in imx6sx

[Keskinarkaus, Teemu]

Hi,

We have HW iMX6SoloX based HW running Yocto 2.2 and Wayland/Weston 1.11. There 
is need to rotate the display 90 degrees. In X11 this wouldn't be a problem 
since you could use xrandr. What I understood Wayland does not support this 
method.

There is rotate config(transform) option in Weston, but it did nothing when 
tested. Is there a way to rotate the display in Wayland that would work with 
iMX6 or is that something that is not currently supported in that combo? 
(Wayland + imx6).

It would be good if the screen could be rotated in Wayland so applications 
wouldn't need to do that themselves and also of course desktop would be right 
way around.

-Teemu Keskinarkaus



Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

Thank you.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

RE: Using EGL drivers in Weston without FBDev

[Keskinarkaus, Teemu]

Hi,

I'm not sure if Yocto 2.3 has new enough version of Mesa and kernel for that. 
Seems that it defaults to Weston 1.11 so I'd assume no. Also I got impression 
that NXP versions of drivers support HW better (graphics work faster etc. 
maybe?). That I don't have my own experience so just relying what I've read.

But anyway thanks. Now I have something to go forward.

-Teemu Keskinarkaus

-Original Message-
From: wayland-devel [mailto:wayland-devel-boun...@lists.freedesktop.org] On 
Behalf Of Daniel Stone
Sent: 23. toukokuuta 2017 10:04
To: Keskinarkaus, Teemu
Cc: wayland-devel@lists.freedesktop.org
Subject: Re: Using EGL drivers in Weston without FBDev

Hi Teemu,

On 23 May 2017 at 05:33, Keskinarkaus, Teemu 
 wrote:
> I just ran into this although support was dropped almost a year ago.
>
> Since FBDEV no longer has EGL ‘hackery’ support, what is then the ‘proper’
> way to use EGL drivers?  ie. What way they _should_ be used?
>
> I’m in no way expert in this whole Wayland/Weston/driver thing so
> that’s why I’m asking.
>
> We are currently using Weston in iMX6 based HW and NXP currently has
> only EGL/FBdev drivers available that’s why I ran to problems with
> Wayland/Weston when trying to upgrade to Weston 2.0.

The recommended way is to use EGL on top of KMS (kernel modesetting), the 
combination of which is called GBM. This is what's implemented by Mesa, and 
also several other drivers including ARM Mali.

The last time I saw NXP i.MX code for Weston, it was a fork of Weston using 
their own API for rendering and buffer management. I don't know if this ever 
got ported forward to newer versions, so you'd probably be needing to use their 
tree anyway. I know this isn't the advice you were hoping to get, but I would 
strongly recommend contacting NXP and asking them to support KMS and GBM like 
everyone else.

The good news is that the 'Etnaviv' and imx-drm drivers inside Mesa and the 
mainline Linux kernel work just fine, so if you use very new versions of Mesa 
and the kernel, there should be no need to run NXP's fork of Weston and their 
EGL drivers.

Cheers,
Daniel
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Fwayland-devel&data=02%7C01%7Cteemu.keskinarkaus%40crosscontrol.com%7C2954ee0ac4564fe0ab6b08d4a1a9ee21%7C1602ae82026640d6910b11680fe0f6a5%7C0%7C0%7C636311198587709141&sdata=bwzA1B1u2Bk88SdS2AJJtcqYk05ChzyETPIwAHXarvo%3D&reserved=0



Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

Thank you.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

Using EGL drivers in Weston without FBDev

[Keskinarkaus, Teemu]

Hi,

I just ran into this although support was dropped almost a year ago.

Since FBDEV no longer has EGL 'hackery' support, what is then the 'proper' way 
to use EGL drivers?  ie. What way they _should_ be used?

I'm in no way expert in this whole Wayland/Weston/driver thing so that's why 
I'm asking.

We are currently using Weston in iMX6 based HW and NXP currently has only 
EGL/FBdev drivers available that's why I ran to problems with Wayland/Weston 
when trying to upgrade to Weston 2.0.

-Teemu Keskinarkaus




Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

Thank you.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

RE: Input device to weston after start

[Keskinarkaus, Teemu]

> -Original Message-
> From: Peter Hutterer [mailto:peter.hutte...@who-t.net]
> Sent: 7. joulukuuta 2015 2:13
> To: Pekka Paalanen
> Cc: Keskinarkaus, Teemu; wayland-devel@lists.freedesktop.org
> Subject: Re: Input device to weston after start
>
> On Fri, Dec 04, 2015 at 05:25:35PM +0200, Pekka Paalanen wrote:
> > On Fri, 4 Dec 2015 08:04:55 +
> > "Keskinarkaus, Teemu"  wrote:
> >
> > > Hi,
> > >
> > > I have a HW with touchscreen that is connected to serial port. I'm
> > > using inputattach to attach the touch to Linux input system. After
> > > that I start Weston and touch works just fine.
> > >
> > > Problem now is that the inputattach takes some time to find/install
> > > the touch device and if I start Weston before that the touch won't
> > > work. This causes delay at startup that now is wanted to be
> > > eliminated. I think the delay in adding the touch device comes from
> > > kernel side so I'm not willing to touch to that if possible to avoid.
> > >
> > > Question now is that is it possible to add input devices to Weston
> > > _after_ it's been started? If so, then how to do it? Simply adding
> > > the device the kernel input system doesn't automatically make it
> > > visible in Weston. Ie. if in my case the inputattach is started
> > > after Weston is started, the touch won't start working.
> >
> > AFAIK Weston is listening on udev events and should be opening input
> > devices as they appear. Perhaps you could compare what happens when
> > hotplugging a normal keyboard or mouse vs. starting inputattach?
> >
> > I suppose one would check if there are any udev events from that, does
> > Weston see them and if so, does something in Weston reject the device,
> > or is Weston never notified about it.
>
> Weston doesn't handle this directly, libinput handles this transparently.
> But since the code is effectively the same for devices seen at startup vs 
> devices
> hotplugged it's a bit odd that there is a difference.
>
> Teemu: please file a bug against libinput and attach the udevadm info output 
> for
> the device. Run libinput-debug-events and check if the DEVICE_ADDED event
> appears after you run inputattach.
>
> Cheers,
>Peter

It seems that I'm running so old version (Yocto 1.7) that it doesn't have 
libinput as does the Yocto 1.8 so I'll see if I can update to newer version and 
if it still doesn't work then file a bug.

-Teemu



Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

Thank you.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel

Input device to weston after start

[Keskinarkaus, Teemu]

Hi,

I have a HW with touchscreen that is connected to serial port. I'm using 
inputattach to attach the touch to Linux input system. After that I start 
Weston and touch works just fine.

Problem now is that the inputattach takes some time to find/install the touch 
device and if I start Weston before that the touch won't work. This causes 
delay at startup that now is wanted to be eliminated. I think the delay in 
adding the touch device comes from kernel side so I'm not willing to touch to 
that if possible to avoid.

Question now is that is it possible to add input devices to Weston _after_ it's 
been started? If so, then how to do it? Simply adding the device the kernel 
input system doesn't automatically make it visible in Weston. Ie. if in my case 
the inputattach is started after Weston is started, the touch won't start 
working.

Teemu Keskinarkaus
Software system engineer





Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

Thank you.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel

Serial touchscreen device in Weston

[Keskinarkaus, Teemu]

Hi,

For reasons beyond me I'm forced to use serial port as a mean to connect 
touchscreen to my device. I've already verified that I get serial data out from 
it when touching the screen so that part is working.

Now next part is to get it working with the Weston.

The I'm running Weston in iMX6 with Yocto based Linux.

I did search the Weston.ini, but it doesn't seem to have any touchscreen 
configuration options. Is it possible to configure serial touch screen to 
Weston and if so how?

If it's not possible to just configure then any ideas how to do it? I remember 
vaguely that there is daemon that does the serial conversion to input-device, 
but I can't remember anymore what it is called.

Teemu Keskinarkaus
Software system engineer
Cell: +358 400 330047
Fax: +358 207 669199
www.maximatecc.com

maximatecc
making machines smart, safe and productive




Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

Thank you.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel