@lex

Members
  • Content Count

    442
  • Joined

  • Last visited


Reputation Activity

  1. Like
    @lex got a reaction from lanefu in Enable OV5640 on NanoPi A64   
    This weekend I was revising and testing the OV5640 for some A64 boards.
    To enable the Camera (OV5640) on NanoPi A64 for the mainline kernel you have to update the following:
    * DT
    * GPIO-I2C 
    Here is the excerpt :
     
    Kernel config:
     
    CONFIG_I2C_GPIO=m
    CONFIG_VIDEO_OV5640=m
    CONFIG_VIDEO_SUN6I_CSI=m
     
  2. Like
    @lex got a reaction from NicoD in RK3399 Game Playing, What games work, Assaultcube, Torc etc   
    That's the reason. It updates to new libEGL and breaks the symlink to libmali. If for some reason the new lib is installed you have to manually re-create the symlinks, or just don't update.
  3. Like
    @lex reacted to guidol in [Experiment] armbian on NanoPi A64   
    Hah I did found something....after @kamma did tell it would be OK with the PineA64-deconfig....

    It seems that the deactivated usb@1c19000 allwinner,sun8i-a33-musb has to be activated as status = "okay";
    and in dr_mode = "host"; like on the pine64
     
    I changed the sun50i-a64-nanopi-a64.dts and compiled it back to .dtb and did put it in /boot/dtb/allwinner and reboot.
     
    see config here in hidden spoiler:
     
    Now the NanoPi A64 does recognize the USB-Stick at the upper port.
     
    [    1.856580] sun4i-usb-phy 1c19400.phy: failed to get clock usb0_phy
    [    2.129298] usb_phy_generic usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found, using dummy regulator
    [    2.129351] usb_phy_generic usb_phy_generic.0.auto: Linked as a consumer to regulator.0
    [    2.129630] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
    [    2.129639] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 5
    [    2.129813] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.00
    [    2.129821] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [    2.129826] usb usb5: Product: MUSB HDRC host driver
    [    2.129832] usb usb5: Manufacturer: Linux 5.0.7-sunxi64 musb-hcd
    [    2.129837] usb usb5: SerialNumber: musb-hdrc.1.auto
    [   82.404779] usb 3-1: new high-speed USB device number 2 using ehci-platform
    [   82.562191] usb 3-1: New USB device found, idVendor=0930, idProduct=6545, bcdDevice= 1.10
    [   82.562202] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [   82.562206] usb 3-1: Product: TransMemory-Mx
    [   82.562211] usb 3-1: Manufacturer: TOSHIBA
    [   82.562215] usb 3-1: SerialNumber: C03FD55EAF4CEFC050138484
    [   82.563032] usb-storage 3-1:1.0: USB Mass Storage device detected
    [   82.570592] scsi host0: usb-storage 3-1:1.0
    [   89.518200] usb 3-1: USB disconnect, device number 2
    [   92.721680] usb 1-1: new high-speed USB device number 3 using ehci-platform
    [   92.879376] usb 1-1: New USB device found, idVendor=0930, idProduct=6545, bcdDevice= 1.10
    [   92.879387] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [   92.879391] usb 1-1: Product: TransMemory-Mx
    [   92.879395] usb 1-1: Manufacturer: TOSHIBA
    [   92.879400] usb 1-1: SerialNumber: C03FD55EAF4CEFC050138484
    [   92.880125] usb-storage 1-1:1.0: USB Mass Storage device detected
    [   92.883967] scsi host0: usb-storage 1-1:1.0
    [ 1054.498911] usb 1-1: USB disconnect, device number 3
  4. Like
    @lex got a reaction from qblueRed42 in Monitoring your system health with HTOP (big.LITTLE)   
    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
     

  5. Like
    @lex got a reaction from devman in Monitoring your system health with HTOP (big.LITTLE)   
    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
     

  6. Like
    @lex reacted to jernej in Orangepi 3 h6 allwiner chip   
    DMA channels for SPI0 are 22 and 22 (Rx, Tx).
     
    BTW, I already sent patches, but I still want to know if it will work for you once you fix DT issues.
  7. Like
    @lex got a reaction from NicoD in Orangepi 3 h6 allwiner chip   
    I have watched this thread and decided to check the status of the mainline kernel 5.0 for the H6 with the @Icenowy 's work on top of it.
    I can say it works really nice (tested on Orange Pi 3 H6):
    * HDMI
    * DVFS
    * Gbps / ethernet
     
    I have prepared a blindly DT that should work on Opi 3 H6: https://github.com/avafinger/orangepi-h6-ubuntu-base-minimal/tree/master/dts
     @Igor , Basically fetch the mainline kernel 5, apply your patch set on top and add/modify my DT.
     
    I have tried to add i2c and spi but it did not work as i expected.
    I had something like this:
    For the i2c
            i2c0: i2c@5002000 {             compatible = "allwinner,sun6i-a31-i2c";             reg = <0x05002000 0x400>;             interrupts = <GIC_SPI 4 IRQ_TYPE_LEVEL_HIGH>;             clocks = <&ccu CLK_BUS_I2C0>;             resets = <&ccu RST_BUS_I2C0>;             status = "disabled";             #address-cells = <1>;             #size-cells = <0>;         };         i2c1: i2c@5002400 {             compatible = "allwinner,sun6i-a31-i2c";             reg = <0x05002400 0x400>;             interrupts = <GIC_SPI 5 IRQ_TYPE_LEVEL_HIGH>;             clocks = <&ccu CLK_BUS_I2C1>;             resets = <&ccu RST_BUS_I2C1>;             status = "disabled";             #address-cells = <1>;             #size-cells = <0>;         };             i2c0_pins: i2c0_pins {                 pins = "PH5", "PH6";                 function = "i2c0";             };             i2c1_pins: i2c1_pins {                 pins = "PD25", "PD26";                 function = "i2c1";             }; Default i2c in use (PMIC and possibly HDMI):
    ls /dev/i2c-* /dev/i2c-0  /dev/i2c-1 i2cdetect -y 0      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 00:          -- -- -- -- -- -- -- -- -- -- -- -- --  10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- --  40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  70: -- -- -- -- -- -- -- --                          i2cdetect -y 1      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 00:          -- -- -- -- -- -- -- -- -- -- -- -- --  10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  30: 30 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  50: 50 51 52 53 54 55 56 57 -- -- -- -- -- -- -- --  60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  70: -- -- -- -- -- -- -- --            
    For the SPI0:
     
            spi0: spi@5010000 {             compatible = "allwinner,sun8i-h3-spi";             reg = <0x05010000 0x1000>;             interrupts = <GIC_SPI 10 IRQ_TYPE_LEVEL_HIGH>;             clocks = <&ccu CLK_BUS_SPI0>, <&ccu CLK_SPI0>;             clock-names = "ahb", "mod";             dmas = <&dma 23>, <&dma 23>;             dma-names = "rx", "tx";             pinctrl-names = "default";             pinctrl-0 = <&spi0_pins>;             resets = <&ccu RST_BUS_SPI0>;             status = "disabled";             num-cs = <1>;             #address-cells = <1>;             #size-cells = <0>;         };             spi0_pins: spi0 {                 pins = "PC0", "PC2", "PC3", "PC5";                 function = "spi0";             }; One thing i noticed was some instability on SD card but resorting to 4.19-rc6 clk values fixed it.
     
    Regarding the reboot command, i applied the latest ATF power fix (as suggested by @jernej but reboot works exactly as shutdown -h now
  8. Like
    @lex got a reaction from Werner in Orangepi 3 h6 allwiner chip   
    I have watched this thread and decided to check the status of the mainline kernel 5.0 for the H6 with the @Icenowy 's work on top of it.
    I can say it works really nice (tested on Orange Pi 3 H6):
    * HDMI
    * DVFS
    * Gbps / ethernet
     
    I have prepared a blindly DT that should work on Opi 3 H6: https://github.com/avafinger/orangepi-h6-ubuntu-base-minimal/tree/master/dts
     @Igor , Basically fetch the mainline kernel 5, apply your patch set on top and add/modify my DT.
     
    I have tried to add i2c and spi but it did not work as i expected.
    I had something like this:
    For the i2c
            i2c0: i2c@5002000 {             compatible = "allwinner,sun6i-a31-i2c";             reg = <0x05002000 0x400>;             interrupts = <GIC_SPI 4 IRQ_TYPE_LEVEL_HIGH>;             clocks = <&ccu CLK_BUS_I2C0>;             resets = <&ccu RST_BUS_I2C0>;             status = "disabled";             #address-cells = <1>;             #size-cells = <0>;         };         i2c1: i2c@5002400 {             compatible = "allwinner,sun6i-a31-i2c";             reg = <0x05002400 0x400>;             interrupts = <GIC_SPI 5 IRQ_TYPE_LEVEL_HIGH>;             clocks = <&ccu CLK_BUS_I2C1>;             resets = <&ccu RST_BUS_I2C1>;             status = "disabled";             #address-cells = <1>;             #size-cells = <0>;         };             i2c0_pins: i2c0_pins {                 pins = "PH5", "PH6";                 function = "i2c0";             };             i2c1_pins: i2c1_pins {                 pins = "PD25", "PD26";                 function = "i2c1";             }; Default i2c in use (PMIC and possibly HDMI):
    ls /dev/i2c-* /dev/i2c-0  /dev/i2c-1 i2cdetect -y 0      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 00:          -- -- -- -- -- -- -- -- -- -- -- -- --  10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- --  40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  70: -- -- -- -- -- -- -- --                          i2cdetect -y 1      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 00:          -- -- -- -- -- -- -- -- -- -- -- -- --  10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  30: 30 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  50: 50 51 52 53 54 55 56 57 -- -- -- -- -- -- -- --  60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  70: -- -- -- -- -- -- -- --            
    For the SPI0:
     
            spi0: spi@5010000 {             compatible = "allwinner,sun8i-h3-spi";             reg = <0x05010000 0x1000>;             interrupts = <GIC_SPI 10 IRQ_TYPE_LEVEL_HIGH>;             clocks = <&ccu CLK_BUS_SPI0>, <&ccu CLK_SPI0>;             clock-names = "ahb", "mod";             dmas = <&dma 23>, <&dma 23>;             dma-names = "rx", "tx";             pinctrl-names = "default";             pinctrl-0 = <&spi0_pins>;             resets = <&ccu RST_BUS_SPI0>;             status = "disabled";             num-cs = <1>;             #address-cells = <1>;             #size-cells = <0>;         };             spi0_pins: spi0 {                 pins = "PC0", "PC2", "PC3", "PC5";                 function = "spi0";             }; One thing i noticed was some instability on SD card but resorting to 4.19-rc6 clk values fixed it.
     
    Regarding the reboot command, i applied the latest ATF power fix (as suggested by @jernej but reboot works exactly as shutdown -h now
  9. Like
    @lex got a reaction from guidol in Orangepi 3 h6 allwiner chip   
    I have watched this thread and decided to check the status of the mainline kernel 5.0 for the H6 with the @Icenowy 's work on top of it.
    I can say it works really nice (tested on Orange Pi 3 H6):
    * HDMI
    * DVFS
    * Gbps / ethernet
     
    I have prepared a blindly DT that should work on Opi 3 H6: https://github.com/avafinger/orangepi-h6-ubuntu-base-minimal/tree/master/dts
     @Igor , Basically fetch the mainline kernel 5, apply your patch set on top and add/modify my DT.
     
    I have tried to add i2c and spi but it did not work as i expected.
    I had something like this:
    For the i2c
            i2c0: i2c@5002000 {             compatible = "allwinner,sun6i-a31-i2c";             reg = <0x05002000 0x400>;             interrupts = <GIC_SPI 4 IRQ_TYPE_LEVEL_HIGH>;             clocks = <&ccu CLK_BUS_I2C0>;             resets = <&ccu RST_BUS_I2C0>;             status = "disabled";             #address-cells = <1>;             #size-cells = <0>;         };         i2c1: i2c@5002400 {             compatible = "allwinner,sun6i-a31-i2c";             reg = <0x05002400 0x400>;             interrupts = <GIC_SPI 5 IRQ_TYPE_LEVEL_HIGH>;             clocks = <&ccu CLK_BUS_I2C1>;             resets = <&ccu RST_BUS_I2C1>;             status = "disabled";             #address-cells = <1>;             #size-cells = <0>;         };             i2c0_pins: i2c0_pins {                 pins = "PH5", "PH6";                 function = "i2c0";             };             i2c1_pins: i2c1_pins {                 pins = "PD25", "PD26";                 function = "i2c1";             }; Default i2c in use (PMIC and possibly HDMI):
    ls /dev/i2c-* /dev/i2c-0  /dev/i2c-1 i2cdetect -y 0      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 00:          -- -- -- -- -- -- -- -- -- -- -- -- --  10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- --  40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  70: -- -- -- -- -- -- -- --                          i2cdetect -y 1      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 00:          -- -- -- -- -- -- -- -- -- -- -- -- --  10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  30: 30 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  50: 50 51 52 53 54 55 56 57 -- -- -- -- -- -- -- --  60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  70: -- -- -- -- -- -- -- --            
    For the SPI0:
     
            spi0: spi@5010000 {             compatible = "allwinner,sun8i-h3-spi";             reg = <0x05010000 0x1000>;             interrupts = <GIC_SPI 10 IRQ_TYPE_LEVEL_HIGH>;             clocks = <&ccu CLK_BUS_SPI0>, <&ccu CLK_SPI0>;             clock-names = "ahb", "mod";             dmas = <&dma 23>, <&dma 23>;             dma-names = "rx", "tx";             pinctrl-names = "default";             pinctrl-0 = <&spi0_pins>;             resets = <&ccu RST_BUS_SPI0>;             status = "disabled";             num-cs = <1>;             #address-cells = <1>;             #size-cells = <0>;         };             spi0_pins: spi0 {                 pins = "PC0", "PC2", "PC3", "PC5";                 function = "spi0";             }; One thing i noticed was some instability on SD card but resorting to 4.19-rc6 clk values fixed it.
     
    Regarding the reboot command, i applied the latest ATF power fix (as suggested by @jernej but reboot works exactly as shutdown -h now
  10. Like
    @lex got a reaction from pazzoide in htop has strange "layout"   
    Type in the shell:
    printf   "This is ASCII representation:\n|\n\`\n\`-\nThis is UTF-8 representation:\n\xe2\x94\x82\n\xe2\x94\x9c\n\xe2\x94\x94\xe2\x94\x80\n"
     
    You should see this:
    This is ASCII representation:
    |
    `
    `-
    This is UTF-8 representation:


    └─
     
    If you don't see the above representation, you should set UTF-8 for your language in Terminal.
  11. Like
    @lex got a reaction from pazzoide in htop has strange "layout"   
    htop was built without support for ncursessw (shared libraries for terminal handling (wide character support)).
    I realized that is not the problem, i found out if you run htop from ssh terminal and from a console terminal you get ASCII on one and UTF-8 on the other (or vice-versa) and both have UTF-8 support.
    Can you please check if you have the same behavior?  
     
     
  12. Like
    @lex got a reaction from guidol in htop has strange "layout"   
    Type in the shell:
    printf   "This is ASCII representation:\n|\n\`\n\`-\nThis is UTF-8 representation:\n\xe2\x94\x82\n\xe2\x94\x9c\n\xe2\x94\x94\xe2\x94\x80\n"
     
    You should see this:
    This is ASCII representation:
    |
    `
    `-
    This is UTF-8 representation:


    └─
     
    If you don't see the above representation, you should set UTF-8 for your language in Terminal.
  13. Like
    @lex got a reaction from guidol in [Experiment] armbian on NanoPi A64   
    My last update on this issue in case someone is working to get sound on A64 (>= 4.20).
    I tried every patch out there,  triple checked the code , same situation, no sound. 
    I must have missed something or overlooked something.
    I finally tried Vasily's kernel and for my surprise no sound. Last hope, i tried Vasily ARCH img, no luck, no sound even on Pine64.
    Maybe it works on Pinebook,.... 
     
  14. Like
    @lex reacted to zador.blood.stained in NanoPC T4   
    Looks like we got an upstream DT for the T4: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/arch/arm64/boot/dts/rockchip?id=e7a095908227fb3ccc86d001d9e13c9ae2bef8e6
  15. Like
    @lex got a reaction from jock in Monitoring your system health with HTOP (big.LITTLE)   
    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. Like
    @lex got a reaction from Tido in Monitoring your system health with HTOP (big.LITTLE)   
    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
     

  17. Like
    @lex got a reaction from Werner in Orange pi one plus - 1800 MHz   
    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  
  18. Like
    @lex got a reaction from Werner in Orange pi one plus - 1800 MHz   
    You might ask @tkaiser, he did that on PineH64 and that applies to Opi One Plus.
     
     
  19. Like
    @lex got a reaction from Werner in Orange pi one plus - 1800 MHz   
    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... 
  20. Like
    @lex got a reaction from tkaiser in Trying to compile Pine H64   
    OrangePi One Plus BSP 4.9, kernel 4.9.56 stock for analisys. 
    Here is DRAM initialization in use (hope is what you meant):
    [271]PMU: AXP806 [275]set pll start [278]set pll end [279]rtc[0] value = 0x00000000 [282]rtc[1] value = 0x00000000 [285]rtc[2] value = 0x00000000 [288]rtc[3] value = 0x00000000 [292]rtc[4] value = 0x00000000 [295]rtc[5] value = 0x00000000 [298]DRAM VERSION IS V2_5 [300]PMU:Set DDR Vol 1200mV OK. [304]PMU:Set DDR Vol 1200mV OK. [314]BYTE0 GATE ERRO IS = 00000002 [318]BYTE1 GATE ERRO IS = 00000002 [321]BYTE2 GATE ERRO IS = 00000002 [324]BYTE3 GATE ERRO IS = 00000002 [336]DRAM CLK =744 MHZ [338]DRAM Type =7 (3:DDR3,4:DDR4,6:LPDDR2,7:LPDDR3) [343]DRAM zq value: 003b3bfb [350]IPRD=006f006e--PGCR0=00000f5d--PLL=b0003d00 [354]DRAM SIZE =1024 M,para1 = 000030fa,para2 = 04000000 [366]DRAM simple test OK. [369]dram size =1024 tinymembench, running first time with interactive governor:

    CPU:
    Running subsequent tinymembench with performance governor:
     
    CPU:
     
     
    Things you should consider in your analysis that could favor some results or not.
     
    * axp806 not detected by kernel
    [    0.431724] [axp806] chip id not detect 0xff ! [    1.496996] input: axp80x-powerkey as /devices/platform/soc/pmu0/axp80x-powerkey/input/input0 [    4.925539] axp80x_aldo1: unsupportable voltage range: 858992688-3300000uV * eth not functional
    [    0.816207] sun50iw6p1-pinctrl pio: expect_func as:gmac0, but muxsel(5) is func:csi0 [    0.824909] sun50iw6p1-pinctrl pio: expect_func as:gmac0, but muxsel(5) is func:mdc0 [    0.833599] sun50iw6p1-pinctrl pio: expect_func as:gmac0, but muxsel(5) is func:mdio0 [    0.843450] gmac-power2: NULL [   11.600421] libphy: gmac0: probed And the usual:
     
     
    I am pretty sure it runs at 1.8 GHz:
    CPU1 freq      : 1800 MHz  CPU2 freq      : 1800 MHz  CPU3 freq      : 1800 MHz  CPU4 freq      : 1800 MHz  CPU count      : 4   Governor       : performance   SOC Temp       : 55 C  Next time i get results from 3.10...
  21. Like
    @lex got a reaction from tkaiser in Trying to compile Pine H64   
    I am running @Icenowy kernel, 1.5 GHz, 3.10.65 with some minor modification and 4.4.y 4.9.y without ethernet and axp805/6 not recognized .
    I will run  tinymembench possibly tomoorow (lack of time)...
  22. Like
    @lex got a reaction from Werner in OrangePi One Plus network questions   
    FYI, Orange Pi One Plus ethernet Gbit is already working on mainline kernel.
    Thanks to Jagan Teki and Icenowy for their work!
     ./iperf3 -c 192.168.254.100 Connecting to host 192.168.254.100, port 5201 [  4] local 192.168.254.253 port 32808 connected to 192.168.254.100 port 5201 [ ID] Interval           Transfer     Bandwidth       Retr  Cwnd [  4]   0.00-1.00   sec   112 MBytes   942 Mbits/sec    0    112 KBytes        [  4]   1.00-2.00   sec   112 MBytes   941 Mbits/sec    0    119 KBytes        [  4]   2.00-3.00   sec   112 MBytes   941 Mbits/sec    0    119 KBytes        [  4]   3.00-4.00   sec   112 MBytes   941 Mbits/sec    0    119 KBytes        [  4]   4.00-5.00   sec   112 MBytes   941 Mbits/sec    0    119 KBytes        [  4]   5.00-6.00   sec   112 MBytes   941 Mbits/sec    0    119 KBytes        [  4]   6.00-7.00   sec   112 MBytes   942 Mbits/sec    0    202 KBytes        [  4]   7.00-8.00   sec   112 MBytes   942 Mbits/sec    0    202 KBytes        [  4]   8.00-9.00   sec   112 MBytes   941 Mbits/sec    0    202 KBytes        [  4]   9.00-10.00  sec   112 MBytes   942 Mbits/sec    0    202 KBytes        - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval           Transfer     Bandwidth       Retr [  4]   0.00-10.00  sec  1.10 GBytes   942 Mbits/sec    0             sender [  4]   0.00-10.00  sec  1.10 GBytes   941 Mbits/sec                  receiver iperf Done. ./iperf3 -R -c 192.168.254.100 Connecting to host 192.168.254.100, port 5201 Reverse mode, remote host 192.168.254.100 is sending [  4] local 192.168.254.253 port 32816 connected to 192.168.254.100 port 5201 [ ID] Interval           Transfer     Bandwidth [  4]   0.00-1.00   sec   107 MBytes   895 Mbits/sec                   [  4]   1.00-2.00   sec   107 MBytes   896 Mbits/sec                   [  4]   2.00-3.00   sec   106 MBytes   892 Mbits/sec                   [  4]   3.00-4.00   sec   106 MBytes   890 Mbits/sec                   [  4]   4.00-5.00   sec   106 MBytes   893 Mbits/sec                   [  4]   5.00-6.00   sec   107 MBytes   894 Mbits/sec                   [  4]   6.00-7.00   sec   106 MBytes   889 Mbits/sec                   [  4]   7.00-8.00   sec   107 MBytes   894 Mbits/sec                   [  4]   8.00-9.00   sec   106 MBytes   891 Mbits/sec                   [  4]   9.00-10.00  sec   106 MBytes   892 Mbits/sec                   - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval           Transfer     Bandwidth       Retr [  4]   0.00-10.00  sec  1.04 GBytes   893 Mbits/sec  4257             sender [  4]   0.00-10.00  sec  1.04 GBytes   893 Mbits/sec                  receiver iperf Done.  
  23. Like
    @lex got a reaction from LeopoldVonBuschLight in OV5640 on mainline kernel   
    Today I had a chance to test OV5640 on mainline kernel 4.17.2 and see the status of OV5640 and CSI drivers, thanks to FE work and the author of the driver (help name here...). I tested on NanoPi K1 Plus (H5) to verify the images in very low light conditions, so don't expect good quality.
    I could take some images using fswebcam and you should expect basic v4l2 functionality already works if not all. I think motion (did not test  / had time to test it) can work with current OV5640 on mainline kernel.
    Grabbing Image is very fast, currently, Image size I can get are 320x240 and 640x480 pixels, above this i get a dark image. I have not looked at the driver source code to see if it is implemented or not.  
     
    Basically, you need to add the sun6i_csi and ov5640 drivers to the kernel and adjust DT to have the endpoint. FE has already done it and left H5 for homework, but is the same as H3.
     
    To check the functionality, install v4l2-utils and when the driver sun6i_cs loads, it creates the device node /dev/video0 and you can check that:
     
    sudo v4l2-ctl -d /dev/video0 -D Driver Info (not using libv4l2):     Driver name   : sun6i-video     Card type     : sun6i-csi     Bus info      : platform:camera     Driver version: 4.17.2     Capabilities  : 0x84200001         Video Capture         Streaming         Extended Pix Format         Device Capabilities     Device Caps   : 0x04200001         Video Capture         Streaming         Extended Pix Format You should see the modules loaded like this:
    lsmod Module                  Size  Used by sun6i_csi              24576  0 videobuf2_dma_contig    20480  1 sun6i_csi videobuf2_memops       16384  1 videobuf2_dma_contig ov5640                 36864  1 videobuf2_v4l2         24576  1 sun6i_csi videobuf2_common       40960  2 videobuf2_v4l2,sun6i_csi v4l2_fwnode            20480  2 ov5640,sun6i_csi v4l2_common            16384  1 ov5640 videodev              196608  6 v4l2_fwnode,v4l2_common,ov5640,videobuf2_v4l2,sun6i_csi,videobuf2_common sunxi_cir              16384  0 media                  36864  3 videodev,ov5640,sun6i_csi rc_core                40960  2 sunxi_cir sch_fq_codel           20480  6 8189es               1118208  0 So time to revisit the camera drivers on mainline.
    Here are some images (remember, low light condition!):
     
    *update: All possible window sizes are working for streaming!
     
     
     


  24. Like
    @lex got a reaction from Moklev in New Mali blobs (Allwinner, mainline)   
    That's interesting.
    And then the fun begins, i gave it a try using r8p1 with kernel 4.4 on A64 and it works... a bit slow but works, though i don't know for how long. Framebuffer only.
     
    The weird thing (it's  kind of frankenstein):
    =======================================================
        glmark2 2012.12
    =======================================================
        OpenGL Information
        GL_VENDOR:     ARM
        GL_RENDERER:   Mali-400 MP
        GL_VERSION:    OpenGL ES 2.0 "mali450-r5p1-01rel0-lollipop-233-g52c929d"
    =======================================================
    [build] use-vbo=false: FPS: 60 FrameTime: 16.667 ms
    [build] use-vbo=true: FPS: 60 FrameTime: 16.667 ms
    [texture] texture-filter=nearest: FPS: 60 FrameTime: 16.667 ms
    [texture] texture-filter=linear: FPS: 60 FrameTime: 16.667 ms
    [texture] texture-filter=mipmap: FPS: 60 FrameTime: 16.667 ms
    [shading] shading=gouraud: FPS: 60 FrameTime: 16.667 ms
     
    Does Anyone one know a complete recipe for building KODI or similar (framebuffer) to check if this is really working?
  25. Like
    @lex got a reaction from Moklev in OV5640 on mainline kernel   
    Today I had a chance to test OV5640 on mainline kernel 4.17.2 and see the status of OV5640 and CSI drivers, thanks to FE work and the author of the driver (help name here...). I tested on NanoPi K1 Plus (H5) to verify the images in very low light conditions, so don't expect good quality.
    I could take some images using fswebcam and you should expect basic v4l2 functionality already works if not all. I think motion (did not test  / had time to test it) can work with current OV5640 on mainline kernel.
    Grabbing Image is very fast, currently, Image size I can get are 320x240 and 640x480 pixels, above this i get a dark image. I have not looked at the driver source code to see if it is implemented or not.  
     
    Basically, you need to add the sun6i_csi and ov5640 drivers to the kernel and adjust DT to have the endpoint. FE has already done it and left H5 for homework, but is the same as H3.
     
    To check the functionality, install v4l2-utils and when the driver sun6i_cs loads, it creates the device node /dev/video0 and you can check that:
     
    sudo v4l2-ctl -d /dev/video0 -D Driver Info (not using libv4l2):     Driver name   : sun6i-video     Card type     : sun6i-csi     Bus info      : platform:camera     Driver version: 4.17.2     Capabilities  : 0x84200001         Video Capture         Streaming         Extended Pix Format         Device Capabilities     Device Caps   : 0x04200001         Video Capture         Streaming         Extended Pix Format You should see the modules loaded like this:
    lsmod Module                  Size  Used by sun6i_csi              24576  0 videobuf2_dma_contig    20480  1 sun6i_csi videobuf2_memops       16384  1 videobuf2_dma_contig ov5640                 36864  1 videobuf2_v4l2         24576  1 sun6i_csi videobuf2_common       40960  2 videobuf2_v4l2,sun6i_csi v4l2_fwnode            20480  2 ov5640,sun6i_csi v4l2_common            16384  1 ov5640 videodev              196608  6 v4l2_fwnode,v4l2_common,ov5640,videobuf2_v4l2,sun6i_csi,videobuf2_common sunxi_cir              16384  0 media                  36864  3 videodev,ov5640,sun6i_csi rc_core                40960  2 sunxi_cir sch_fq_codel           20480  6 8189es               1118208  0 So time to revisit the camera drivers on mainline.
    Here are some images (remember, low light condition!):
     
    *update: All possible window sizes are working for streaming!