Hi;
I think that you might rather have more success if you just instruct your
weston.service unit file that Weston isn't allowed to start until the DRI
device appears. E.g.,
[Unit]
...
Requires=dev-dri-card0.device # or dev-drm-card0.device as appropriate
for your board
After=dev-dri-card
Hi Daniel,
Any clue/inputs after looking at the logs?
Regards,
Vikash
On Wed, Jan 11, 2017 at 10:55 AM, Vikas Patil wrote:
> Hi Daniel,
>
> Thanks a lot for your quick reply. See comments below.
>
> On Tue, Jan 10, 2017 at 9:28 PM, Daniel Díaz Rodríguez <
> daniel.d...@linaro.org> wrote:
>
>>
Hi Daniel,
Thanks a lot for your quick reply. See comments below.
On Tue, Jan 10, 2017 at 9:28 PM, Daniel Díaz Rodríguez <
daniel.d...@linaro.org> wrote:
> Hello!
>
>
> On 10 January 2017 at 06:39, Vikas Patil wrote:
> >> We are starting weston (1.9.0) using below systemd unit file of type
> no
Hello!
On 10 January 2017 at 06:39, Vikas Patil wrote:
> We are starting weston (1.9.0) using below systemd unit file of type notify
> (backported sd_notify related changes from weston 1.11.0 to weston 1.9.0).
> It works well with i.MX6 (NXP, fbdev backend) based platform, however with
> Jacinto
Dear All,
We are starting weston (1.9.0) using below systemd unit file of type notify
(backported sd_notify related changes from weston 1.11.0 to weston 1.9.0).
It works well with i.MX6 (NXP, fbdev backend) based platform, however with
Jacinto (TI, drm backend) based platform sometimes it fails to
