Search the Community

Showing results for tags 'advanced'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues
    • Peer to peer technical support
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner H5 & A64
    • Armada A388, A3700
    • Amlogic S905(x)
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Other supported boards
  • Development
    • Allwinner H6
    • Rockchip 3399
    • Development

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 7 results

  1. 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.
  2. Hello, Interested in replacing virtualbox as a VM host, "docker" tool seems to be able to run on Debian/Ubuntu/other linux distro/MacOS/Windows (as they claim) My test: 1/ Installing docker on my amd64 4-cores Ubuntu 14.04 (too much tweaking to run "armbian" properly) see doc here also I have been using "Create a Docker group" and don't forget to run "Hello World" test 2/ To create a new container with Ubuntu 14.04 (if you have added docker group to your non-privileged user, if not use "sudo") $ docker run --privileged -i -t ubuntu:14.04 /bin/bash "privileged" is needed for /dev/loop operations, if not the container cannot see the loop device, btw it is less "secure" but not "really" applicable here, I am on my test system. on the host system, the files are stored in "/var/lib/docker", you can move this folder on another HDD/SSD, then you need to (in my example) "cd /var/lib; ln -s /home4/docker docker" 3/ once you have the root shell of the VM # mkdir /root/armbian # cd /root/armbian then feel free to follow the Armbian tool instructions Once all is compiled & package, you can transfer the files with "sftp", "ftp", etc. Or if you want a challenge, grab the files in /var/lib/docker (good luck!) 4/ later to come back to the container, list the containers, get the "Container ID" then start the container $ docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES e12d3a2b9263 ubuntu:14.04 "/bin/bash" About an hour ago Up About an hour grave_ardinghelli d1efa716ad64 hello-world "/hello" 8 hours ago Exited (0) 8 hours ago elegant_meitner $ docker start -i e12d3a2b9263 (to be tested more carefully) edit: you need the "under work" script attached as the ubuntu:14.04 is *not* really a ubuntu server packaged style! edit2: [ o.k. ] Fixing release custom applications. [ jessie ] [ o.k. ] Install board specific applications. [ lamobo-r1 ] [ o.k. ] Fingerprinting. [ Armbian 4.6 Lamobo-r1 Debian jessie next Linux 4.2.6 ] [ o.k. ] Creating boot scripts [ lamobo-r1 ] [ o.k. ] Possible after install. [ o.k. ] Writing boot loader [ /dev/loop1 ] [ o.k. ] Shrink image last partition to [ minimum ] [ o.k. ] Create and sign [ ] [ o.k. ] Runtime [ 81 min ] et voilà ! more testing needed
  3. Rebuilding kernel several times in a row, made some changes, that would be nice to have in build script by default, and also some thoughts on custom kernel patches. 1.Option to not overwrite kernel config before compilation. Example: setting KERNEL_KEEP_CONFIG="yes" in Changes ( # use proven config if [ "$KERNEL_KEEP_CONFIG" != "yes" ]; then cp $SRC/lib/config/$LINUXCONFIG.config $SOURCES/$LINUXSOURCE/.config; fi 2. Option to use ccache for kernel compilation (at least). ccache can be set by creating symlinks for cross-compiling tools, but having an option in build script is more useful and easier IMHO. Example: setting USE_CCACHE="yes" in Changes (in if [ "$USE_CCACHE" = "yes" ] then make $CTHREADS ARCH=arm CROSS_COMPILE="ccache arm-linux-gnueabihf-" all zImage 2>&1 | dialog --backtitle "$backtitle" --progressbox "Compiling kernel ..." 20 70 else make $CTHREADS ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- all zImage 2>&1 | dialog --backtitle "$backtitle" --progressbox "Compiling kernel ..." 20 70 fi Also here stderr of compilation process is redirected to stdout so compiler warnings do not tear dialog window (2>&1). Compiling kernel with ccache right now, will report if it breaks anything. Looks like it doesn't like invoking make deb-pkg after compilation and tries to compile everything again, will test later other than this 4.3 related bug compilation works. 3. Automatically pick up and apply kernel patches from custom directory. Something like this: # in kernel souces root dir for patch in $SRC/patches/$KERNEL_TYPE/*.patch do patch -p1 < $patch done KERNEL_TYPE can be "next" or "legacy" to separate patches for different kernel branches. This can be extended to using device specific directories if necessary.
  4. Hello, FYI for prospective on Odroid XU4, testing images for XU4 (I also have a Cloushell (mini NAS including LCD display)) desktop image link folder Ubuntu 14.04.1 : ok, upgrade to 14.04.3 ok, upgrade to kernel 3.10.92 ok, upgrade to odroid final kernel 4.2.0 DEAD Ubuntu 15.04 : DEAD after reboot (kernel 4.2.0) It seems the image with kernel 4.2.0 just removed "journal" feature of ext4 on startup, so at next reboot, the ext4 fs is dead. trying to fix the SD card on a amd86 Ubuntu gives error like "/usr/sbin" dead, filesystem is garbage server image link ubuntu server image is not usable, dead after first reboot (kernel 4.2 ?) archlinux image using kernel 4.2 3.10.92 (existing 4.3/4.4-rc1 general kernel - untested) pretty ok after rebooting. Only drawback, everything is to be installed, I don't know much of archlinux tools. edit : Do not install odroid-cloudshell package, it really breaks the filesystem after reboot. edit2: in fact, kernel 3.10.92 make the ethernet interface (USB=>ETH) no longer working. It seems the drivers is "closed" sourced edit3: looking at images maybe edit4: ArchlinuxArm seems stable, kernel is old. but image is fine after reboots over and over. pacman is pretty cool!
  5. wildcat_paris

    compilation logging wrapper proposal

    Hello, When patching or generally compiling, "dialog" is not my friend for reading & testing I would propose adding a wrapper in (as in branch "second") dialog_wrapper () { ARGS=$(getopt -o b:p: -l "backtitle:,progressbox:" -n "$0" -- "$@"); if [ $? -ne 0 ]; then exit 1; fi eval set -- "$ARGS"; unset cmdl while true; do case "$1" in -b|--backtitle) shift; if [ -n "$1" ]; then cmdl="$cmdl --backtitle '$1'"; shift; fi ;; -p|--progressbox) shift; if [ -n "$1" ]; then cmdl="$cmdl --progressbox '$1'"; shift; fi ;; --) shift; break; ;; esac done for args in "$@" do cmdl="$cmdl $args" done LOGFILE=/dev/null if [[ $DIALOG_LOGFILE != "" ]] ; then LOGFILE=$DIALOG_LOGFILE [ ! -f $DIALOG_LOGFILE ] && touch $LOGFILE lines=$(wc -l <$DIALOG_LOGFILE) if [[ $lines -ge 2000 ]]; then rm -f $DIALOG_LOGFILE.log mv $DIALOG_LOGFILE $DIALOG_LOGFILE.log touch $DIALOG_LOGFILE fi fi if [[ $DIALOG_WRAPPER == "" ]] ; then tee -a $LOGFILE | eval "dialog $cmdl" else tee -a $LOGFILE fi } and replacing the "dialog" with "dialog_wrapper" for compilation in "", 2 options: #DIALOG_WRAPPER # use dialog as usual DIALOG_WRAPPER=1 # dialog is not active #DIALOG_LOGFILE # logfile is /dev/null DIALOG_LOGFILE=compile.log
  6. Hello Igor(?), Armbian Buddies, I have ended being not able to compile a kernel module (and it breaks dkms btw) because files in linux-headers are ELF x86-64 (not ELF ARM) but it is quick & dirty FIXED :-) (Maybe I have messed Armbian tool playing with v4.3 kernel ???) root@bpi:~/kern4.3_4# dpkg -i linux-headers-next-sunxi_4.6_armhf.deb Unpacking linux-headers-next-sunxi (4.6) over (4.6) ... Setting up linux-headers-next-sunxi (4.6) ... root@bpi:~/kern4.3_4# cd /usr/src/linux-headers-4.3.0-sunxi/scripts/basic/ root@bpi:/usr/src/linux-headers-4.3.0-sunxi/scripts/basic# file fixdep fixdep: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=6852442a0a099c53c54516da788bcb41eb855d61, not stripped root@bpi:/usr/src/linux-headers-4.3.0-sunxi/scripts/basic# uname -a Linux bpi 4.3.0-sunxi #34 SMP Thu Nov 12 16:08:33 CET 2015 armv7l armv7l armv7l GNU/Linux from Igor source I thought it would be ok but nope I ended getting this quick solution root@bpi:/usr/src/linux-headers-4.3.0-sunxi# make scripts HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/bin2c [...] root@bpi:/usr/src/linux-headers-4.3.0-sunxi# file scripts/basic/fixdep scripts/basic/fixdep: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=e21986187584d701fa8f4d5d987a9cee808208c8, not stripped and of course root@bpi:/usr/src/test# ls hello-1.c Makefile root@bpi:/usr/src/test# make make -C /lib/modules/4.3.0-sunxi/build M=/usr/src/test modules make[1]: Entering directory `/home2/src/linux-headers-4.3.0-sunxi' CC [M] /usr/src/test/hello-1.o Building modules, stage 2. MODPOST 1 modules CC /usr/src/test/hello-1.mod.o LD [M] /usr/src/test/hello-1.ko make[1]: Leaving directory `/home2/src/linux-headers-4.3.0-sunxi' root@bpi:/usr/src/test# insmod hello-1.ko root@bpi:/usr/src/test# lsmod | grep hello hello_1 799 0 ok, as zador.blood.stained wrote about issue with builddeb => anything related I have a patching issue in "scripts" folder ? root@bpi:/usr/src/linux-headers-4.3.0-sunxi/scripts/package# cat builddeb builddeb builddeb.orig builddeb.rej root@bpi:/usr/src/linux-headers-4.3.0-sunxi/scripts/package# cat builddeb.rej --- scripts/package/builddeb +++ scripts/package/builddeb @@ -110,13 +112,17 @@ BUILD_DEBUG="$(grep -s '^CONFIG_DEBUG_INFO=y' $KCONFIG_CONFIG || true)" # Setup the directory structure -rm -rf "$tmpdir" "$fwdir" "$kernel_headers_dir" "$libc_headers_dir" "$dbg_dir" +rm -rf "$tmpdir" "$fwdir" "$kernel_headers_dir" "$libc_headers_dir" "$dbg_dir" "$dtb_dir" mkdir -m 755 -p "$tmpdir/DEBIAN" mkdir -p "$tmpdir/lib" "$tmpdir/boot" "$tmpdir/usr/share/doc/$packagename" mkdir -m 755 -p "$fwdir/DEBIAN" mkdir -p "$fwdir/lib/firmware/$version/" "$fwdir/usr/share/doc/$fwpackagename" mkdir -m 755 -p "$libc_headers_dir/DEBIAN" mkdir -p "$libc_headers_dir/usr/share/doc/$libc_headers_packagename" + +mkdir -m 755 -p "$dtb_dir/DEBIAN" +mkdir -p "$dtb_dir/boot/dtb" "$dtb_dir/usr/share/doc/$dtb_packagename" + mkdir -m 755 -p "$kernel_headers_dir/DEBIAN" mkdir -p "$kernel_headers_dir/usr/share/doc/$kernel_headers_packagename" mkdir -p "$kernel_headers_dir/lib/modules/$version/" thanks! Guillaume PS: fyi, lamobo-r1 : sunxi-ss (kernel tests) & prng ok, AC97=> KO not recognized maybe DTB needs a fix
  7. 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 (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 DEBUGKBUILD="yes" # if "yes" then remove dialog for debug else "" for nice dialog style Cheers, Mr Poor 12.34 €