Jump to content

@lex

Members
  • Posts

    530
  • Joined

  • Last visited

Everything posted by @lex

  1. I tried to build the xserver based on Rockchip xserver (debian) on Ubuntu, not much success. Broke font displaying on Desktop. Maybe you could ask for the patch on the RK32xx section, they have it working (armhf). I will give another try. [ 12.433] (==) modeset(0): Depth 24, (==) framebuffer bpp 32 [ 12.433] (==) modeset(0): RGB weight 888 [ 12.433] (==) modeset(0): Default visual is TrueColor [ 12.433] (II) Loading sub module "glamoregl" [ 12.433] (II) LoadModule: "glamoregl" [ 12.434] (II) Loading /usr/lib/xorg/modules/libglamoregl.so [ 12.907] (II) Module glamoregl: vendor="X.Org Foundation" [ 12.907] compiled for 1.19.6, module version = 1.0.0 [ 12.908] ABI class: X.Org ANSI C Emulation, version 0.4 [ 12.908] (II) glamor: OpenGL accelerated X.org driver based. [ 12.973] (II) glamor: EGL version 1.4 Midgard-"r14p0-01rel0": [ 12.973] EGL_KHR_surfaceless_gles2 required. [ 13.038] (II) modeset(0): Using GLES2. [ 13.038] (WW) modeset(0): Glamor is using GLES2 but GLX needs GL. Indirect GLX may not work correctly. [ 13.038] (II) modeset(0): glamor initialized [ 13.074] (II) modeset(0): Output HDMI-1 has no monitor section [ 13.074] (II) modeset(0): Output DP-1 has no monitor section [ 13.157] (II) modeset(0): EDID for output HDMI-1 [ 13.158] (II) modeset(0): Manufacturer: GSM Model: 1 Serial#: 16843009 [ 13.158] (II) modeset(0): Year: 2013 Week: 1
  2. Seems correct. I am not sure you can get 2D glamour decoration if it is that what you want. According to Rockchip doc no special X11 server. Did you test the usual glmark2-es2 ? Not working? Seems i was wrong: http://rockchip.wikidot.com/graphics
  3. I have been playing with T86x on my NanoPi M4 and i can say 3D and OpenCL are working fine with the mali userspace blobs. This blob setup below can save you a lot of sweat unless you really want to go with Panfrost. I can run Kodi 18b5, which renders menu and video on mali. Blobs used: https://github.com/avafinger/nanopi-m4-ubuntu-base-minimal/releases/tag/v1.2.1
  4. If you want to get your hands dirty i can give you briefly the steps if i recall correctly (it works on NanoPi M4, so should work on NanoPi-T4) but unfortunately, i did not take note: a) encode/decode is done by gstreamer (decoding by mvp) install gstreamer (if not already installed) sudo apt-get install libgstreamer1.0-0 gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad gstreamer1.0-plugins-ugly gstreamer1.0- libav gstreamer1.0-doc gstreamer1.0-tools b) clone https://github.com/rockchip-linux/mpp , build and install it (install dependencies fisrt) cmake -DRKPLATFORM=ON -DHAVE_DRM=ON && make sudo make install c) clone gstreamer-rockchip (i can't remember if i did for the -extra also) git clone https://github.com/rockchip-linux/gstreamer-rockchip.git cd gstreamer-rockchip ./autogen.sh --disable-rkximage make sudo make install sudo ldconfig git clone https://github.com/rockchip-linux/gstreamer-rockchip-extra make clean ./autogen.sh make sudo make install sudo ldconfig d) check if the plugins are then installed correctly gst-inspect-1.0|grep 4l2 gst-inspect-1.0|grep rkcamsrc gst-inspect-1.0 | grep rk gst-inspect-1.0 rkximage gst-inspect-1.0 rkv4l2 You will need libdrm-dev and some other dependencies i can't remember. This steps should work on any RK3399. Have fun.
  5. I thought you were using ayufan's kernel. I think nightly build has support for VPU already. Anyway, for BSP kernel: https://github.com/rockchip-linux/mpp
  6. It is a bit low. Don't you worry about the 100% source code, if you want the source code for mali you have to pay... and i guess it is not cheap. Rockchip has gone really nice on VPU and GPU. I think Allwinner should follow this path and give better support for VPU and mali. There is already support for VPU and mali from Rockchip on linux. Usually mali fbdev is 20 ~ 30% faster than mali X11 (don't know about Wayland) but there is an RK3399 board that claims a score of 58 (very good indeed, though i don't know which window size possibly Full HD)). Can you tell what kernel version on your build?
  7. If you have HDMI attached (1920x1080) can you benchmark mali? glmark2-es2 -s 1920x1080
  8. I was looking for errors, CSI does not really show up in dmesg. Seems no errors. I think more info is needed so others can help: armbianmonitor -u PS: You should have something similar to this depending on how is your kernel defconfig: Module Size Used by sun6i_csi 24576 0 videobuf2_dma_contig 20480 1 sun6i_csi ov5640 32768 1 videobuf2_memops 16384 1 videobuf2_dma_contig videobuf2_v4l2 20480 1 sun6i_csi v4l2_fwnode 16384 2 ov5640,sun6i_csi videobuf2_common 36864 2 sun6i_csi,videobuf2_v4l2 v4l2_common 16384 1 ov5640 videodev 139264 6 ov5640,v4l2_fwnode,v4l2_common,videobuf2_common,sun6i_csi,videobuf2_v4l2 sunxi_cir 16384 0 media 24576 3 ov5640,videodev,sun6i_csi hci_uart 36864 0 btintel 16384 1 hci_uart bluetooth 327680 2 hci_uart,btintel ecdh_generic 28672 1 bluetooth brcmfmac 188416 0 brcmutil 16384 1 brcmfmac ipv6 397312 18
  9. A couple of things to check: * check if ov5640 and csi are loaded. dmesg|grep 5640 & dmesg|grep csi * check if you have the correct camera module
  10. The device tree: https://github.com/armbian/build/commit/10e206519089b8ff81b0dd6a6f3caa6c1adba04d#diff-5ec21c7daf434027694931230901ca60R96 If I recall correctly the driver (specific to FE boards) delivers YUV so you need to instruct fswebcam and cap-v4l2 to receive V4L2_PIX_FMT_YUYV. You can try mjpg-streamer that does that by default. Try 640x480 window size first and then move to 720p or higher. I have noticed there is (or there was) a slightly new/modified driver on mainline kernel 4.19.0 but did not have time to check the changes. That mainline driver has been originally written to v3s, you may check linux-sunxi. I don't know v3s so can't help much.
  11. Sorry, it's not king dot com's shareable file manager fault, probably me, apologies. Please try this: https://mega.nz/#F!9OxRnCya!6fsKg-X0tp76Pw89RdMspw
  12. Feel free to test: https://mega.nz/fm/BewyQRzK @guidol seems to have enhanced the image, currently very raw image. * If kernel is stable enough i may push it to github
  13. Quoted from the CSI driver author: "Allwinner V3s SoC features two CSI module. CSI0 is used for MIPI CSI-2 interface and CSI1 is used for parallel interface. This is not documented in datasheet but by test and guess." I don't have this board, but from product page; * DVP Parallel Camera Interface I think if DVP is attached to CSI1 there is a good chance it can work. I may be wrong. Please, check "dmesg | grep -i ov" and " dmesg | grep 5640 " and " dmesg | grep -i csi " for errors. Hope it helps.
  14. I would suggest checking CSI schematic for your board and review the CSI pins on DTS to match that with the schematic.
  15. Just In case anyone is interested I have pushed HTOP 2.2.1 to github, so it is possible to monitor big.LITTLE cores in real-time. You can view the big.LITTLE in action, Vcore, Cpu thermal throttling and Cpu frequency for each big or LITTLE core. HTOP is a nice console graphical tool for system-monitor, process-viewer and process-manager. DEB package and source code in case you want to extend or fix things. Be aware the process list and task can be very intrusive if you want to monitor many things at once. It has been tested on NanoPi M4 (thanks to FriendlyElec for the samples) but should work on any SBC just adjust the Vcore path for different kernel version. https://github.com/avafinger/htop-2.1.1_enhanced-version
  16. I have tested the OV5640 driver on K1+ (H5) only. According to @Igor comment, OV5640 is enabled on NeoAir (H3). Please see the patch: https://github.com/armbian/build/commit/10e206519089b8ff81b0dd6a6f3caa6c1adba04d - # Linux/arm 4.17.0-rc3 Kernel Configuration + # Linux/arm 4.17.2 Kernel Configuration I think you should apply this patch to your board and see if it works.
  17. The reason is the cap-v4l2 expects YUV420 and the driver delivers YUYV. Change the format and you will be fine.
  18. It is fine. For the torture test, better use a good heatsink. I just would like to comment that if you have an image without HDMI (no fb) and a good heatsink you get slightly better values. Now is time to move on and learn new platforms...
  19. Ok then, here is my take on the matter. You have to build the new image or wait for @Igor * Apply the patch described on the thread * Change the regulator like this: reg_dcdca: dcdca { regulator-always-on; regulator-min-microvolt = <810000>; regulator-max-microvolt = <1160000>; regulator-name = "vdd-cpu"; }; * rebuild Image There you have it: 7z b 7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=C.UTF-8,Utf16=on,HugeFiles=on,64 bits,4 CPUs LE) LE CPU Freq: 1717 1796 1796 1796 1796 1796 1796 1796 1796 RAM size: 964 MB, # CPU hardware threads: 4 RAM usage: 882 MB, # Benchmark threads: 4 Compressing | Decompressing Dict Speed Usage R/U Rating | Speed Usage R/U Rating KiB/s % MIPS MIPS | KiB/s % MIPS MIPS 22: 2679 333 783 2607 | 70708 388 1554 6033 23: 2615 333 800 2665 | 66860 388 1489 5785 24: 2545 333 821 2736 | 63737 390 1436 5595 25: 2420 329 839 2763 | 57802 388 1324 5144 ---------------------------------- | ------------------------------ Avr: 332 811 2693 | 389 1451 5639 Tot: 360 1131 4166
  20. You might ask @tkaiser, he did that on PineH64 and that applies to Opi One Plus.
  21. CAM500A needs to add some resistor to work with neo air. There was an instruction on FriendlyArm to add this resistor to become CAM500B, but i can't find it right now.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines