OpenCPN on Raspberry PI2

[NahanniV]

Originally Posted by boat_alexandra

I have tried the new raspbian with vc4 driver....

I had to build opencpn from source. Maybe we should provide binaries for raspberry so the usual method with apt-get can work. Otherwise you need much more disk space to install all the development requirements.

You may know already, but many people are getting OpenCPN on Rpi in the OpenPlotter Project:
Sailing with free hardware | Sailoog
You could be very helpful to them if you wanted to contribute.

Originally Posted by boat_alexandra

It appears that opengl doesn't support texture compression. I think maybe they fixed this in the git version of the driver to support ETC1 in biggl (which is non-standard) but I will try again to see if I can use gles with the vc4 driver and opencpn.

It would be great if you could discuss any issues you see with OpenCPN using the VC4 driver with the author of the driver:
https://github.com/anholt
You may be the best OpenCPN developer to report problems in this area.

[seandepagnier]

It seems running with opengles is very slow and buggy, not working as I expected.

Therefore no texture compression on the raspberry.

[verkerkbr]

Hi BA,

have you tried the Wayland ? (sudo apt dist-upgrade)

OpenGL can now switched to on in OpenCPN. However still software rendering.

Swichting on Wayland with the VC4 driver

OpenCPN screen moves then remarkable faster.

Log shows: OpenGL > Renderer String: Gallium 0.4 on VC4 V3D 2.1
OpenGL Version reported 2.1. Mesa 13.0.0

I don't know how the latest version of the VC4 driver works.

It seems not far away from working "full speed".

Bram

[verkerkbr]

This shows my log before exiting of OpenCPN 4.4.0 when zooming in.

All a bit strange this repeated screen detections.

11:18:41 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:42 CET: Detected display size (horizontal): 444 mm
11:18:44 CET: Detected display size (horizontal): 444 mm
11:18:45 CET: Detected display size (horizontal): 444 mm
11:18:46 CET: Detected display size (horizontal): 444 mm
11:18:46 CET: Detected display size (horizontal): 444 mm
11:18:47 CET: Detected display size (horizontal): 444 mm
11:18:47 CET: Detected display size (horizontal): 444 mm
11:18:48 CET: Detected display size (horizontal): 444 mm
11:18:49 CET: Detected display size (horizontal): 444 mm
11:18:49 CET: Detected display size (horizontal): 444 mm
11:18:50 CET: Detected display size (horizontal): 444 mm
11:18:51 CET: Detected display size (horizontal): 444 mm
11:18:52 CET: Detected display size (horizontal): 444 mm
11:18:53 CET: Loading World Chart Q=4 in 3 ms.
11:18:53 CET: Detected display size (horizontal): 444 mm
11:18:54 CET: Detected display size (horizontal): 444 mm
11:18:55 CET: Detected display size (horizontal): 444 mm
11:18:57 CET: Detected display size (horizontal): 444 mm
11:18:58 CET: Detected display size (horizontal): 444 mm
11:18:59 CET: Detected display size (horizontal): 444 mm
11:19:00 CET: Detected display size (horizontal): 444 mm
11:19:01 CET: Detected display size (horizontal): 444 mm
11:19:02 CET: Detected display size (horizontal): 444 mm
11:19:03 CET: Detected display size (horizontal): 444 mm
11:19:04 CET: Detected display size (horizontal): 444 mm
11:19:05 CET: Detected display size (horizontal): 444 mm
11:19:06 CET: Detected display size (horizontal): 444 mm
11:19:07 CET: Chart cache purge
11:19:07 CET: Initializing Chart /home/pi/Downloads/NL/OC-32-410101.oesenc
11:19:07 CET: processChartInfo considering: K1/home/pi/Downloads/NL/
11:19:07 CET: processChartInfo found: K1!home!pi!Downloads!NL!
11:19:07 CET: validate_SENC_server
11:19:07 CET: Available TRUE
11:19:07 CET: Detected display size (horizontal): 444 mm

[seandepagnier]

Originally Posted by verkerkbr

Hi BA,

have you tried the Wayland ? (sudo apt dist-upgrade)

OpenGL can now switched to on in OpenCPN. However still software rendering.

Swichting on Wayland with the VC4 driver

OpenCPN screen moves then remarkable faster.

Log shows: OpenGL > Renderer String: Gallium 0.4 on VC4 V3D 2.1
OpenGL Version reported 2.1. Mesa 13.0.0

I don't know how the latest version of the VC4 driver works.

It seems not far away from working "full speed".

Bram

I didn't try wayland.

It takes 10 seconds to load x on the pi, and 7 to boot in raspbian, so 17 seconds to show chart.

In tinycore linux, I can boot in 3-4 seconds, but it still takes 10 more to load all the xorg to show the map. The vc4 driver isn't working in tinycore.

If I could use wayland it might help in both cases.



In the future we should get texture compression which will help the raspberry a lot for raster charts, but until then it will be slower.

The actual gpu is much less capable anyway, than say mali graphics. The odroid c2 is getting perfect rendering, and cost the same nearly as raspberry that is 3-5x slower! But odroid c2 is 64bit and some "very strange" stuff happening also.

[verkerkbr]

Read just some news about the latest kernel 4.10

- The Raspberry Pi VC4 DRM driver has ETC1 texture compression and fragment shader threading support.

Regards,


Bram

Raspian version now is 4.4.38.

[seandepagnier]

yes I'm hoping that etc1 is in the near future.

As for the broadcom itself is very limited compared to other mobile gpu

[LeaseOnLife]

taken/moved from a discussion about the latest OpenCPN:

Originally Posted by LeaseOnLife

or, to play with Kernel 4.9.5 (works for me on PI3):

sudo BRANCH=next rpi-update

https://www.raspberrypi.org/forums/v...c.php?t=167934

Dirk

Originally Posted by verkerkbr

Beste L-o-L,

tried the 4.9 kernel version on my Raspberry Pi.

Works very well. Olthough no more music playing from internet with Chromium. But is seems to be solved in next update of the Chromium-browser.

And how about OpenGL accelerated video driver ?

Where to get the latest driver, if it allready available and working.

Regards,


Bram

Hardware acceleration:

no matter what I tried, since using wayland, the active driver was always the "fbturbo" sw accelerated driver (check /var/log/Xorg.0.log). While it works with opencpn and glxgears showing 130-180fps, the cpuload was high ~50%.

I just learned how to disable the fbturbo driver: remove/rename the file /usr/share/X11/xorg.conf.d/99-fturbo.conf.

The open source VC4 driver (dtoverlay=vc4-kms-v3d) doesn't work well with my hdmi-vga converter, but the closed source driver does work for me (dtoverlay=vc4-fkms-v3d).
With

vblank_mode=0 glxgears

I am getting 750 fps at 25% cpu load shown in the taskbar!!

Cheers

Dirk

[seandepagnier]

To be clear, has anyone gotten accelerated graphics working in wayland? This might give less overhead and faster boot time, but so far I have only used acceleration in x.



I also must use this fkms. Are you sure it's open vs closed?? I am using raspberry 2.

I am using chinese hdmi lcd.

[verkerkbr]

Followed the instructions from LeaseOnLife:

kernel version 4.9
Swichting off the ftturbo
latest beta version of OpenCPN

Systems works now very fast with the OpenGL setting to on in OpenCPN

O-log shows:

OpenGL > renderer String Gallium 0.4 on VC4 V3D 2.1

GLXgears in vblank=0 mode is running at 450 FPS

Switched on the VC4 experimental driver.

Processor load stays at around 30%

[LeaseOnLife]

Originally Posted by boat_alexandra

To be clear, has anyone gotten accelerated graphics working in wayland? This might give less overhead and faster boot time, but so far I have only used acceleration in x.



I also must use this fkms. Are you sure it's open vs closed?? I am using raspberry 2.

I am using chinese hdmi lcd.

yes i am using wayland.
regarding closed/open sourced for fkms: see
https://github.com/raspberrypi/linux...836df87a355419

This gets us normal 3D support on top of the existing firmware display stack. There's no real modesetting support, no async pageflips (hurting performance), etc., but it means that the desktop can at least run until we get full native modesetting.

To me that reads it is using some closed source part (firmware), but since it works, I don't really care :-)

Dirk

[LeaseOnLife]

Originally Posted by boat_alexandra

To be clear, has anyone gotten accelerated graphics working in wayland? ...

Possible correction to my last port. This is what I have installed on my Raspberry:

ii  xserver-common                        2:1.18.4-2+rpi1                           all          common files used by various X servers
ii  xserver-xorg                          1:7.7+16                                  armhf        X.Org X server
ii  xserver-xorg-core                     2:1.18.4-2+rpi1                           armhf        Xorg X server - core server
ii  xserver-xorg-input-all                1:7.7+16                                  armhf        X.Org X server -- input driver metapackage
ii  xserver-xorg-input-evdev              1:2.10.3-1                                armhf        X.Org X server -- evdev input driver
ii  xserver-xorg-input-libinput           0.20.0-1                                  armhf        X.Org X server -- libinput input driver
ii  xserver-xorg-input-synaptics          1.8.3-2                                   armhf        Synaptics TouchPad driver for X.Org server
ii  xserver-xorg-video-fbdev              1:0.4.4-1+rpi2                            armhf        X.Org X server -- fbdev display driver
ii  libwayland-client0:armhf              1.11.0-2                                  armhf        wayland compositor infrastructure - client library
ii  libwayland-cursor0:armhf              1.11.0-2                                  armhf        wayland compositor infrastructure - cursor library
ii  libwayland-egl1-mesa:armhf            13.0.0-1+rpi1                             armhf        implementation of the Wayland EGL platform -- runtime
ii  libwayland-server0:armhf              1.11.0-2                                  armhf        wayland compositor infrastructure - server library

what does that mean? Sean, tell me :-)

Dirk

[LeaseOnLife]

Originally Posted by verkerkbr

...
Swichting off the ftturbo ...

fturbo shall never confuse me again:

apt-get remove --purge xserver-xorg-video-fbturbo

and it still works

[Hakan]

For info:
I'm running Rpi2 Raspbian Linux 8 Jessie and now also Kernel 4.9.5. All the rest, except then kernel "next" update, is out of the box.
I've built 4.5.127 and use OpenGL, CM93 and BR24Radar_pi!
I can zoom in/out, move charts around and of course navigate w/o big delays. Works great, better then ever. (Actually I saw no difference to kernel 4.4 I think O4.5.127 did the thing.)
O logs OpenGL:
Version: 3.0 Mesa 13.0.0
Texture rect...:de1
Using: Vertex buffer Objects
.
.
Using: s3tc dxt1 compression


Håkan

[seandepagnier]

A lot of my recent optimizations which were critical for quilting performance with many charts as well as improving raster performances reached this beta.

Still am waiting for etc1 support on the raspberry which will allow using compressed cache. This should make things very fast even with slow sdcard full of charts.