Search the Community

Showing results for tags 'mainline'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Technical support
    • Getting started
    • Allwinner A20
    • Allwinner H2 & H3
    • Amlogic S905(x)
    • Armada A388, A3700
    • Freescale imx6
    • Rockchip 3288 & 3328
    • Other supported boards
    • Common issues
  • Community forums
    • Peer to peer technical support
    • TV boxes
    • General chit chat
  • Development
    • Allwinner A64, H5 & H6
    • Rockchip 3399
    • Development

Categories

There are no results to display.

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 12 results

  1. robert@axium.co.nz

    Solved - H3 SPI with DMA using mainline kernel

    Using the dev build of Armbian for the OrangePi One, does the SPI driver in the mainline kernel support DMA? According to the mainline status page the work on SPI is done, and DMA has been supported since 4.2 I have enabled the spi interface in the device tree and my driver initialises properly with the master. But in my kernel driver I attempt to allocate some memory with dma_alloc_coherent and it fails. The driver works fine with the legacy kernel and with alternative hardware (raspberry pi). Is there some additional configuration needed or does anyone have any pointers to information on this that I look at? --edit Solved it - the mainline driver doesn't like the GFP_DMA flag being present on the dma_alloc_coherent call.
  2. zador.blood.stained

    Mainline A10/A20 audio driver

    Looks like A10/A20 audio codec support got merged to linux-next tree. Igor, can you please add these patches? I'll try to find all related bits. There are too many commits to link them one by one. Here is merge commit, it's easier to remove not needed bcm2835 and sun6i stuff from it. https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit?id=2030deefd5bfb68317732d8f64c69c7cb5169e9d
  3. AXP202/209 sysfs interface patch for axp20x MFD drvier in mainline kernel ➜ ~ % ls /sys/power/axp_pmu/{ac,vbus,battery,charger,pmu,control,ocv_curve} /sys/power/axp_pmu/ocv_curve /sys/power/axp_pmu/ac: amperage connected used voltage /sys/power/axp_pmu/battery: amperage capacity charge charging connected power ts_voltage voltage /sys/power/axp_pmu/charger: amperage cell_activation charging low_power /sys/power/axp_pmu/control: battery_rdc disable_fuel_gauge set_vbus_direct_mode charge_rtc_battery reset_charge_counter /sys/power/axp_pmu/pmu: overheat temp voltage /sys/power/axp_pmu/vbus: amperage connected strong used voltage ➜ ~ % Shortlog: How to test: Patches for next and dev branches are included in Armbian build framework, use standart procedures to build and install new kernel. .. or you can download this prebuilt kernel for next branch. Latest version of the patch, basic documentation and battery calibration utility are available on GitHub. TODO list: Find and fix bugs. Check if can be converted into a separate kernel module, preferrably power supply class driver. Limitations: AXP202/AXP209 only for now. Things are implemented according to datasheet and my understanding of it. Default settings for main battery according to datasheet: Target voltage: 4.2V Charging current: 500mA/1200mA (?) Defaut settings for RTC battery: Charging: disabled by default. Target voltage: 3.0V Charging current: 200uA Standart disclaimer: Code looks simple enough, but i wouldn't recommend using it on production environment yet. Bugreports are welcome, but I'm not responsible for kernel panics, lost data and exploded PMUs.
  4. Vancouver

    SPI issue with Banana Pro/A20

    Hi all, there is an issue with SPI on a Banana Pro (A20). I am on mainline kernel 4.5.5 now, but the problem already occurred on 3.4.109. SPI transfers are way to slow for my application, independently from the SPI clock. Investigating the SPI signals it turned out that there is an enormous delay between CS going active (low) and the transmission starting. The delay is in the magnitude of 10...20 usec which is a large multiple of the pure transmission time, so increasing the SPI clock does not solve the problem. The connected device is an SPI TFT display, so I have to send a large number of SPI words of 2 bytes each, where CS must toggle after each word (required by the target device). Consequently, the transmission of a large amount of data takes about several hundred times longer than required. I am not a driver expert, but I have looked into the source code of spi_sun4i.c which is the low level driver used for the A20 as far as I know. Here it seems, that the CS signal is under software control, i.e. it is handled as a normal GPIO. CS must be set/cleared by an explicit function call. I wonder, if this is the reason for the large delay. I found a quick-and-dirty workaround, where somebody configured the SPI controller directly via /dev/mem (i.e. bypassing kernel driver) and kept CS under hardware control, so the delay between CS and start of transmission is only some hundred nanoseconds. Now I am thinking of a modification of the SPI low level driver to keep CS under hardware control as well. However, I am not sure if this is a solution to my problem. Does anybody have a similar experience or a better idea than kernel modification? Any comments are welcome :-) Thanks
  5. Vancouver

    eth0 configuration lost

    Hi, not sure if this problem is related to Armbian, but in my case it occurs only on an Armian system. I have mainline kernel (4.7.x) running on a Banana Pro. wlan is configured as access point and works without any problems. eth0 is configured as client with static IP. The Banana is running 24/7, but the ethernet port is used only sporadically. The switch where eth0 is connected to is powered down most time. The problem is that eth0 forgets its IP configuration after a while, ifconfig then reports no IP address for eth0. I have to login via wlan and then ifdown/ifup eth0, then it works again. After a couple of hours (I dont know exactly how long), the IP is lost again. What is going wrong here?
  6. I am having the exact same hw configuration as described here. I am using latest (stable) mainline kernel 4.0.5, SPI is enabled in DTB like this: spi0: spi@01c05000 { pinctrl-names = "default"; pinctrl-0 = <&spi0_pins_a>; status = "okay"; spi0_0 { #address-cells = <1>; #size-cells = <0>; compatible = "spidev"; reg = <0>; spi-max-frequency = <50000000>; }; }; I am loading the driver like this and the displays back light goes on - so far is o.k. modprobe fbtft_device name=adafruit22a rotate=90 speed=4800000 fps=30 gpios=reset:272,led:226,dc:245 busnum=32766 This way, with different GPIOS numbers and without busnum parameter works perfectly well on kernel 3.4.x Kernel output when loading the driver on 4.0.5 [27880.540870] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [27880.549004] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned. [27880.551333] fbtft_device: SPI devices registered: [27880.551386] fbtft_device: spidev spi32766.0 50000kHz 8 bits mode=0x00 [27880.551406] fbtft_device: 'fb' Platform devices registered: [27880.551570] fbtft_device: Deleting spi32766.0 [27880.553696] fbtft_device: GPIOS used by 'adafruit22a': [27880.553735] fbtft_device: 'reset' = GPIO272 [27880.553756] fbtft_device: 'led' = GPIO226 [27880.553775] fbtft_device: 'dc' = GPIO245 [27880.553793] fbtft_device: SPI devices registered: [27880.553820] fbtft_device: fb_ili9340 spi32766.0 4800kHz 8 bits mode=0x00 [27880.575688] fb_ili9340: module is from the staging directory, the quality is unknown, you have been warned. [27880.819789] fb_ili9340 spi32766.0: SPI transfer failed: -22 [27880.819830] spi_master spi32766: failed to transfer one message from queue [27880.819850] fb_ili9340 spi32766.0: fbtft_update_display: write_vmem failed to update display buffer [27880.821093] graphics fb1: fb_ili9340 frame buffer, 320x240, 150 KiB video memory, 4 KiB DMA buffer memory, fps=33, spi32766.0 at 4 MHz When I write some picture to the display I got this: [28727.125092] fb_ili9340 spi32766.0: SPI transfer failed: -22 [28727.125141] spi_master spi32766: failed to transfer one message from queue [28727.125162] fb_ili9340 spi32766.0: fbtft_update_display: write_vmem failed to update display buffer [28727.154895] fb_ili9340 spi32766.0: SPI transfer failed: -22 [28727.154937] spi_master spi32766: failed to transfer one message from queue [28727.154957] fb_ili9340 spi32766.0: fbtft_update_display: write_vmem failed to update display buffer I haven't done the famous spi_test.c test and I also doesn't have any equipment to debug further. Is there any stupid thing that I am doing wrong or is this simply not done yet? Anyone got further on this?
  7. Carlos Garcés

    Kernel compilation and device tree

    Hi! I'm testing the image for cubieboard (A10 SOC) onto my MK 802 II and the legacy kernel is working fine (USB, OGT, WIFI, HDMI...) I just have changed the script.bin I'm reading some documentation about the device trees and I don't understand how you compile the vanilla kernel. Sorry if is a stupid questions but my board has his own .dts (sun4i-a10-mk802ii.dts), how you get a common vanilla kernel valid for all the configurations without using one specific .dts for each board? Probably I'm missing something very basic for ARM kernels, but this is my 1º aproach.
  8. Hello Igor, I am starting exploring your nice "lib" tools for mainline/lamobo/trusty and end with this error message. the host is trusty / amd64 / quad cores / 8 GB RAM unsure if /bin/mktemp refers to loopback device or host /tmp lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk x Installing Armbian on the top of Ubuntu trusty base system ... x x x x build-essential x x x x lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk x x x 0% x x x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj [ error ] Installation failed Setting up cmake-data (2.8.12.2-0ubuntu3) ... Setting up cmake (2.8.12.2-0ubuntu3) ... Processing triggers for libc-bin (2.19-0ubuntu6) ... Processing triggers for ca-certificates (20141019ubuntu0.14.04.1) ... /bin/mktemp: failed to create file via template '/tmp/user/0/ca-certificates.crt.tmp.XXXXXX': No such file or directory dpkg: error processing package ca-certificates (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: ca-certificates E: Sub-process /usr/bin/dpkg returned an error code (1) FYI gr@gr /run $ df -h Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur /dev/sda1 115G 63G 47G 58% / none 4,0K 0 4,0K 0% /sys/fs/cgroup udev 3,9G 4,0K 3,9G 1% /dev none 1,0G 8,0K 1,0G 1% /tmp tmpfs 799M 1,1M 798M 1% /run none 5,0M 0 5,0M 0% /run/lock none 3,9G 0 3,9G 0% /run/shm none 100M 0 100M 0% /run/user ramlog-tmpfs 2,0G 706M 1,3G 36% /var/log /dev/sda2 991M 105M 820M 12% /boot /dev/sdb6 210G 141G 59G 71% /home2 /dev/sdc1 1,8T 533G 1,2T 31% /home4 /dev/mapper/sdd1 1,8T 93M 1,7T 1% /home5 /dev/loop0p1 3,8G 526M 3,1G 15% /home/gr/armbian/output/cache/sdcard chdev 3,9G 4,0K 3,9G 1% /home/gr/armbian/output/cache/sdcard/dev regards, Guillaume
  9. Hi Igor, Hi Buddies, with the new changes of *.sh files because of "2>&1" you cannot figure out the compilation errors -- or if any staling questions like patching file tools/include/tools/be_byteshift.h patching file tools/include/tools/le_byteshift.h dpkg-deb: building package `linux-firmware-image-next-sunxi' in `../linux-firmware-image-next-sunxi_4.6_armhf.deb'. gzip: ./debian/dtbtmp/usr/share/doc/linux-dtb-next-sunxi/changelog.Debian.gz already exists; do you wish to overwrite (y or n)? so I have tried and would suggest the following changes in common.sh (or anything better for bash conditional piping) #make $CTHREADS ARCH=arm CROSS_COMPILE="$CCACHE arm-linux-gnueabihf-" zImage modules 2>&1 | dialog --backtitle "$backtitle" --progressbox "Compiling kernel $CCACHE ..." 20 80 MKE="make $CTHREADS ARCH=arm CROSS_COMPILE=\"$CCACHE arm-linux-gnueabihf-\" zImage modules" [[ $DEBUGKBUILD = "" ]] && MKE="${MKE} 2>&1 | dialog --backtitle \"$backtitle\" --progressbox \"Compiling kernel $CCACHE ...\" 20 80" eval $MKE #make $CTHREADS ARCH=arm CROSS_COMPILE="$CCACHE arm-linux-gnueabihf-" dtbs 2>&1 | dialog --backtitle "$backtitle" --progressbox "Compiling DTB $CCACHE ..." 20 80 MKE="make $CTHREADS ARCH=arm CROSS_COMPILE=\"$CCACHE arm-linux-gnueabihf-\" dtbs" [[ $DEBUGKBUILD = "" ]] && MKE="${MKE} 2>&1 | dialog --backtitle \"$backtitle\" --progressbox \"Compiling DTB $CCACHE ...\" 20 80" eval $MKE #make -j1 $KERNEL_PACKING KDEB_PKGVERSION=$REVISION LOCALVERSION="-"$LINUXFAMILY KBUILD_DEBARCH=armhf ARCH=arm DEBFULLNAME="$MAINTAINER" \ #DEBEMAIL="$MAINTAINERMAIL" CROSS_COMPILE="$CCACHE arm-linux-gnueabihf-" 2>&1 | dialog --backtitle "$backtitle" --progressbox "Packing kernel $CCACHE ..." 20 80 MKE="\ make -j1 $KERNEL_PACKING KDEB_PKGVERSION=$REVISION LOCALVERSION=\"-\"$LINUXFAMILY KBUILD_DEBARCH=armhf ARCH=arm DEBFULLNAME=\"$MAINTAINER\" \ DEBEMAIL=\"$MAINTAINERMAIL\" CROSS_COMPILE=\"$CCACHE arm-linux-gnueabihf-\"\ " [[ $DEBUGKBUILD = "" ]] && MKE="${MKE} 2>&1 | dialog --backtitle \"$backtitle\" --progressbox \"Packing kernel $CCACHE ...\" 20 80" eval $MKE including in compile.sh DEBUGKBUILD="yes" # if "yes" then remove dialog for debug else "" for nice dialog style Cheers, Mr Poor 12.34 €
  10. Hello Igor, greatings everyone, I have realized the "build" link is missing to the /usr/src/linux-headers-x.x.x-sunxi Ubuntu Trusty (x86/amd64 kernel) provides such a link I was building a small kernel module from source (frandom-dkms) on my labomo-r1 gr@bpi:/lib/modules/4.2.3-sunxi$ ll total 1260 drwxr-xr-x 4 root root 4096 Oct 13 18:34 ./ drwxr-xr-x 3 root root 4096 Oct 13 15:20 ../ lrwxrwxrwx 1 root root 34 Oct 13 14:23 build -> /usr/src/linux-headers-4.2.3-sunxi/ drwxr-xr-x 9 root root 4096 Oct 13 15:20 kernel/ -rw-r--r-- 1 root root 360156 Oct 13 18:34 modules.alias -rw-r--r-- 1 root root 367304 Oct 13 18:34 modules.alias.bin -rw-r--r-- 1 root root 14935 Oct 11 14:12 modules.builtin -rw-r--r-- 1 root root 17813 Oct 13 18:34 modules.builtin.bin -rw-r--r-- 1 root root 82602 Oct 13 18:34 modules.dep -rw-r--r-- 1 root root 128280 Oct 13 18:34 modules.dep.bin -rw-r--r-- 1 root root 128 Oct 13 18:34 modules.devname -rw-r--r-- 1 root root 40034 Oct 11 14:12 modules.order -rw-r--r-- 1 root root 131 Oct 13 18:34 modules.softdep -rw-r--r-- 1 root root 103401 Oct 13 18:34 modules.symbols -rw-r--r-- 1 root root 131685 Oct 13 18:34 modules.symbols.bin drwxr-xr-x 3 root root 4096 Oct 13 18:34 updates/ without the link: gr@bpi:~/frandom/frandom-master$ ls CHANGELOG debian description-pak etc frandom.c INSTALL Makefile README usr gr@bpi:~/frandom/frandom-master$ make make -C /lib/modules/4.2.3-sunxi/build SUBDIRS=/home/gr/frandom/frandom-master modules make: *** /lib/modules/4.2.3-sunxi/build: No such file or directory. Stop. make: *** [default] Error 2 with the link: gr@bpi:~/frandom/frandom-master$ make make -C /lib/modules/4.2.3-sunxi/build SUBDIRS=/home/gr/frandom/frandom-master modules make[1]: Entering directory `/home2/src/linux-headers-4.2.3-sunxi' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; \ /bin/false) mkdir -p /home/gr/frandom/frandom-master/.tmp_versions ; rm -f /home/gr/frandom/frandom-master/.tmp_versions/* make -f ./scripts/Makefile.build obj=/home/gr/frandom/frandom-master gcc -Wp,-MD,/home/gr/frandom/frandom-master/.frandom.o.d -nostdinc -isystem /usr/lib/gcc/arm-linux-gnueabihf/4.8/include -I./arch/arm/include -Iarch/arm/include/generated/uapi -Iarch/arm/include/generated -Iinclude -I./arch/arm/include/uapi -Iarch/arm/include/generated/uapi -I./include/uapi -Iinclude/generated/uapi -include ./include/linux/kconfig.h -D__KERNEL__ -mlittle-endian -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-dwarf2-cfi-asm -mabi=aapcs-linux -mno-thumb-interwork -mfpu=vfp -funwind-tables -marm -D__LINUX_ARM_ARCH__=7 -march=armv7-a -msoft-float -Uarm -fno-delete-null-pointer-checks -O2 --param=allow-store-data-races=0 -Wframe-larger-than=1024 -fno-stack-protector -Wno-unused-but-set-variable -fomit-frame-pointer -fno-var-tracking-assignments -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -DCC_HAVE_ASM_GOTO -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(frandom)" -D"KBUILD_MODNAME=KBUILD_STR(frandom)" -c -o /home/gr/frandom/frandom-master/frandom.o /home/gr/frandom/frandom-master/frandom.c (cat /dev/null; echo kernel//home/gr/frandom/frandom-master/frandom.ko;) > /home/gr/frandom/frandom-master/modules.order make -f ./scripts/Makefile.modpost find /home/gr/frandom/frandom-master/.tmp_versions -name '*.mod' | xargs -r grep -h '\.ko$' | sort -u | sed 's/\.ko$/.o/' | scripts/mod/modpost -i ./Module.symvers -I /home/gr/frandom/frandom-master/Module.symvers -o /home/gr/frandom/frandom-master/Module.symvers -S -w -s -T - gcc -Wp,-MD,/home/gr/frandom/frandom-master/.frandom.mod.o.d -nostdinc -isystem /usr/lib/gcc/arm-linux-gnueabihf/4.8/include -I./arch/arm/include -Iarch/arm/include/generated/uapi -Iarch/arm/include/generated -Iinclude -I./arch/arm/include/uapi -Iarch/arm/include/generated/uapi -I./include/uapi -Iinclude/generated/uapi -include ./include/linux/kconfig.h -D__KERNEL__ -mlittle-endian -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-dwarf2-cfi-asm -mabi=aapcs-linux -mno-thumb-interwork -mfpu=vfp -funwind-tables -marm -D__LINUX_ARM_ARCH__=7 -march=armv7-a -msoft-float -Uarm -fno-delete-null-pointer-checks -O2 --param=allow-store-data-races=0 -Wframe-larger-than=1024 -fno-stack-protector -Wno-unused-but-set-variable -fomit-frame-pointer -fno-var-tracking-assignments -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -DCC_HAVE_ASM_GOTO -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(frandom.mod)" -D"KBUILD_MODNAME=KBUILD_STR(frandom)" -DMODULE -c -o /home/gr/frandom/frandom-master/frandom.mod.o /home/gr/frandom/frandom-master/frandom.mod.c ld -EL -r -T ./scripts/module-common.lds --build-id -o /home/gr/frandom/frandom-master/frandom.ko /home/gr/frandom/frandom-master/frandom.o /home/gr/frandom/frandom-master/frandom.mod.o make[1]: Leaving directory `/home2/src/linux-headers-4.2.3-sunxi' gr@bpi:~/frandom/frandom-master$ ls CHANGELOG description-pak frandom.c frandom.mod.c frandom.o Makefile Module.symvers usr debian etc frandom.ko frandom.mod.o INSTALL modules.order README thanks! Guillaume
  11. What do we have? Serial connection: Hardware schematics: orangepi-plus-h3-v1_1.pdf Wireless: Realtek RTL 8189 ETV Allwinner introduced new way of storing board definitions (also on A23 and A80) so it's a bit different than on A20 boards. H3_Manual_build_howto Kernel building with Allwinner SDK is terrible and was not able to build it. I must admit I haven't invest much time and energy yet.
  12. Hello Igor, I have noticed for a couple of kernel updates, a very minor issue : the previous initrd.img-x.x.x-sunxi is not removed I have tested both dpkg -i *.deb or apt upgrade, same issue so I guess a debian pkg script update is needed. gr@bpi:~$ ls -l /boot total 13864 drwxr-xr-x 2 root root 4096 Oct 13 15:37 bin -rw-r--r-- 1 root root 6944 Aug 31 17:48 boot.bmp -rw-r--r-- 1 root root 1749 Aug 31 17:49 boot.cmd -rw-r--r-- 1 root root 1821 Aug 31 17:49 boot.scr -rw-r--r-- 1 root root 115484 Oct 11 14:12 config-4.2.3-sunxi drwxr-xr-x 2 root root 12288 Oct 13 15:37 dtb drwxr-xr-x 2 root root 4096 Oct 13 14:23 dtb.old -rw-r--r-- 1 root root 3294810 Oct 10 23:13 initrd.img-4.2.2-sunxi -rw-r--r-- 1 root root 3312199 Oct 13 15:38 initrd.img-4.2.3-sunxi lrwxrwxrwx 1 root root 23 Sep 17 00:46 script.bin -> /boot/bin/lamobo-r1.bin -rw-r--r-- 1 root root 1955569 Oct 11 14:12 System.map-4.2.3-sunxi -rwxr-xr-x 1 root root 5468416 Oct 11 14:12 vmlinuz-4.2.3-sunxi lrwxrwxrwx 1 root root 25 Oct 13 15:38 zImage -> /boot/vmlinuz-4.2.3-sunxi thanks. Guillaume