Re: [meta-ti] Weston Desktop Shell
Adam, We just switched from Morty to Rocko as our LTS branch couple months ago and some features are still missing, while teams are ramping up. This particular issue requires Weston patching in meta-arago, but Weston 2.0 changed some APIs and those patches no longer apply. Hopefully we'll be able to resolve this in the near future. Since this is specific to meta-arago, please direct any further questions to the corresponding mailing list at meta-ar...@arago-project.org -- Denys On Mon, Feb 12, 2018 at 04:03:54PM +, Adam Lee wrote: > I spent a bit of time getting the logs: > > Any insight as to why this is happening, it would be much appreciated. > > Adam > > On Fri, Feb 9, 2018 at 3:26 PM Adam Lee wrote: > > > Has anyone successfully brought up Weston desktop shell on the current > > master on Beagleboard X15 or AM57xx-EVM? I am having EGL initialization > > error. I don't know if it is something I have mis-configured. > > > > BR, > > > > Adam > > > -- > ___ > meta-ti mailing list > meta-ti@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-ti -- ___ meta-ti mailing list meta-ti@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-ti
Re: [meta-ti] [EXTERNAL] Re: Weston Desktop Shell
Hi, Adam: The problem shows as the following line. [19:24:55.055] initializing drm backend [19:24:55.091] using /dev/dri/card1 The SGX DDK creates another dri-like device as card1, but it should not be used as DRM device. Please apply the following patch to the Weston build. 0001-udev-seat-restrict-udev-enumeration-to-card0.patch. You may need other patches under meta-arago.meta-arago-distro/recipes-graphics/wayland/weston including 0002-Weston-Allow-visual_id-to-be-0.patch Best regards, Eric From: meta-ti-boun...@yoctoproject.org [mailto:meta-ti-boun...@yoctoproject.org] On Behalf Of Adam Lee Sent: Monday, February 12, 2018 11:04 AM To: meta-ti@yoctoproject.org Subject: [EXTERNAL] Re: [meta-ti] Weston Desktop Shell I spent a bit of time getting the logs: root@am57xx-evm:~# weston --backend=drm-backend.so --tty=4 Date: 2018-01-08 UTC [19:24:55.053] weston 2.0.0 http://wayland.freedesktop.org Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=2.0.0 Build: c26dbf3-dirty weston-launch: Provide a default version that doesn't require PAM (2018-02-09 11:58:14 -0500) [19:24:55.053] Command line: weston --backend=drm-backend.so --tty=4 [19:24:55.053] OS: Linux, 4.9.69-g89d085d1a4, #10 SMP PREEMPT Thu Feb 8 12:11:21 EST 2018, armv7l [19:24:55.053] Using config file '/etc//weston.ini' [19:24:55.054] Output repaint window is 7 ms maximum. [19:24:55.054] Loading module '/usr/lib/libweston-2/drm-backend.so' [19:24:55.055] initializing drm backend [19:24:55.091] using /dev/dri/card1 [19:24:55.091] Loading module '/usr/lib/libweston-2/gl-renderer.so' failed to load module: /usr/lib/gbm/gbm_dri.so: cannot open shared object file: No such file or directory failed to load module: /usr/lib/gbm/gbm_gallium_drm.so: cannot open shared object file: No such file or directory loaded module : gbm_pvr.so found valid GBM backend : gbm_pvr.so PVR:(Error): [ 1157-> 1157] < gbm_pvr_create_device():592|ERROR> Failed to create DBM device: No such device [0, ] [19:24:55.095] failed to initialize egl [19:24:55.120] fatal: failed to create compositor backend Any insight as to why this is happening, it would be much appreciated. Adam On Fri, Feb 9, 2018 at 3:26 PM Adam Lee mailto:adam.yh@gmail.com>> wrote: Has anyone successfully brought up Weston desktop shell on the current master on Beagleboard X15 or AM57xx-EVM? I am having EGL initialization error. I don't know if it is something I have mis-configured. BR, Adam 0001-udev-seat-restrict-udev-enumeration-to-card0.patch Description: 0001-udev-seat-restrict-udev-enumeration-to-card0.patch 0002-Weston-Allow-visual_id-to-be-0.patch Description: 0002-Weston-Allow-visual_id-to-be-0.patch -- ___ meta-ti mailing list meta-ti@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-ti
Re: [meta-ti] Weston Desktop Shell
I spent a bit of time getting the logs: root@am57xx-evm:~# weston --backend=drm-backend.so --tty=4 Date: 2018-01-08 UTC [19:24:55.053] weston 2.0.0 http://wayland.freedesktop.org Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=2.0.0 Build: c26dbf3-dirty weston-launch: Provide a default version that doesn't require PAM (2018-02-09 11:58:14 -0500) [19:24:55.053] Command line: weston --backend=drm-backend.so --tty=4 [19:24:55.053] OS: Linux, 4.9.69-g89d085d1a4, #10 SMP PREEMPT Thu Feb 8 12:11:21 EST 2018, armv7l [19:24:55.053] Using config file '/etc//weston.ini' [19:24:55.054] Output repaint window is 7 ms maximum. [19:24:55.054] Loading module '/usr/lib/libweston-2/drm-backend.so' [19:24:55.055] initializing drm backend [19:24:55.091] using /dev/dri/card1 [19:24:55.091] Loading module '/usr/lib/libweston-2/gl-renderer.so' failed to load module: /usr/lib/gbm/gbm_dri.so: cannot open shared object file: No such file or directory failed to load module: /usr/lib/gbm/gbm_gallium_drm.so: cannot open shared object file: No such file or directory loaded module : gbm_pvr.so found valid GBM backend : gbm_pvr.so PVR:(Error): [ 1157-> 1157] < gbm_pvr_create_device():592|ERROR> Failed to create DBM device: No such device [0, ] [19:24:55.095] failed to initialize egl [19:24:55.120] fatal: failed to create compositor backend Any insight as to why this is happening, it would be much appreciated. Adam On Fri, Feb 9, 2018 at 3:26 PM Adam Lee wrote: > Has anyone successfully brought up Weston desktop shell on the current > master on Beagleboard X15 or AM57xx-EVM? I am having EGL initialization > error. I don't know if it is something I have mis-configured. > > BR, > > Adam > -- ___ meta-ti mailing list meta-ti@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-ti
[meta-ti] Accessing Analog Inputs
I followed the steps to create a beaglebone found here:
http://www.jumpnowtek.com/beaglebone/BeagleBone-Systems-with-Yocto.html
They worked like a charm, thanksyou junponowtek.
And then followed this doc to try and get the ADC available:
http://processors.wiki.ti.com/index.php/Linux_Core_ADC_Users_Guide
I loaded the module and it shows up in lsmod along with other modules it
brings in:
# lsmod
Module Size Used by
ti_am335x_adc 16384 0
kfifo_buf 16384 1 ti_am335x_adc
industrialio 57344 2 ti_am335x_adc,kfifo_buf
ti_am335x_tscadc 16384 1 ti_am335x_adc
My arch/arm/boot/dts/am335x-evm.dts file shows
&tscadc {
status = "okay";
tsc {
ti,wires = <4>;
ti,x-plate-resistance = <200>;
ti,coordinate-readouts = <5>;
ti,wire-config = <0x00 0x11 0x22 0x33>;
ti,charge-delay = <0x400>;
};
adc {
ti,adc-channels = <4 5 6 7>;
};
};
According to the doc above loading the module should create the following:
>On loading the module you would see the IIO device created
root@arago-armv7:~# ls -al /sys/bus/iio/devices/iio\:device0/
drwxr-xr-x 5 root root 0 Nov 1 22:06 .
drwxr-xr-x 4 root root 0 Nov 1 22:06 ..
drwxr-xr-x 2 root root 0 Nov 1 22:06 buffer
-r--r--r-- 1 root root 4096 Nov 1 22:06 dev
-rw-r--r-- 1 root root 4096 Nov 1 22:06 in_voltage4_raw
-rw-r--r-- 1 root root 4096 Nov 1 22:06 in_voltage5_raw
-rw-r--r-- 1 root root 4096 Nov 1 22:06 in_voltage6_raw
-rw-r--r-- 1 root root 4096 Nov 1 22:06 in_voltage7_raw
-r--r--r-- 1 root root 4096 Nov 1 22:06 name
lrwxrwxrwx 1 root root 0 Nov 1 22:06 of_node ->
../../../../../../firmware/devicetree/base/ocp/tscadc@44e0d000/adc
drwxr-xr-x 2 root root 0 Nov 1 22:06 power
drwxr-xr-x 2 root root 0 Nov 1 22:06 scan_elements
lrwxrwxrwx 1 root root 0 Nov 1 22:06 subsystem ->
../../../../../../bus/iio
-rw-r--r-- 1 root root 4096 Nov 1 22:06 uevent
While the /sys/bus/iio directory got created when I loaded the module
the device directory is empty
# ls /sys/bus/iio/devices
#
What am I missing that is preventing the ADC interface from being created ?
Any pointers would be appreciated.
Thanks
Chris K
--
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti
