SliTaz Forum

Slitaz on armel?

(58 posts) (5 voices)

• Started 10 years ago by pirandr
• Latest reply from alanyih
• This topic is not a support question

Tags:

No tags yet.

1. 

   pirandr
   

   offline

   Member

   @alaniyh

   Fix README and clean-tools

   I've finally got around to doing this and put up a new version at

   https://github.com/pirandr/slitaz-arm

   Although I think the version at http://mirror.slitaz.org/arm/cross/slitaz-arm-toolchain-20140304.tar.bz2 is already stripped. So its better not to update to my "new" version.

   @pankso: The top of the README in slitaz-arm-toolchain-20140304.tar.bz2 is still wrong though as alanyih pointed out

   /usr/cross
   should be /cross

   But actually, right now this README is hard coded into cross and should probably also be updated (eventually).

   Broadcom VideoCore

   This sounds really good! (I'll have to look at the details to make sure this isn't another shim. :) ) And what odd timing too. It also seems like its not just for the Raspberry but possibly for other Broadcom boards.

   The source release targets the BCM21553 cellphone chip, but it should be reasonably straightforward to port this to the BCM2835

   I'm curious as to why they didn't release the source for BCM2835 alongside. It feels a bit strange, like this had nothing to do with the RaspPi at all (but happens to benefit it).

   libtools minefield

   Oops. I guess you figured it out a year earlier. Even with exactly the same link. :)

   arm.slitaz.org

   The page looks really cool and its nice to have everything gathered up in one place. (I'll have to try directfb again when I have time, which seems like never right now.)

   xorg-server-light

   Right. I should have tried getting the light version working first.

   Currently, http://cook.slitaz.org/cross/arm/cooker.cgi?pkg=xorg-server-light shows a C compiler error, but this is a red herring.

   I think the real problem is that some of the C libraries got replaced when dependencies were installed. I got the same error when I tried to cook xorg-server-light on a fresh chroot.

   I also realised that switching mirrors (tazpkg -sm) is really dangerous when you have packages in the local cache (since it will pull from the cache, which came from another mirror). So you might end up installing things you didn't want to into /cross/arm/sysroot.

   This can be fixed (temporarily) by just regenerating a /cross/arm/sysroot. I just untarred the toolchain are replaced all of /cross.

   However, this will keep happening (and replace some important files in /cross/arm/sysroot). It turns out it is because it is trying to install glibc-dev (which we don't have for arm yet) into /cross/arm/sysroot. But I don't think this is actually needed.

   Changing this let me get to the first real compilation error, which is a library path problem (about finding pixman.h). And that's where I stopped.

   Posted 10 years ago #
2. 

   alanyih
   

   offline

   Administrator

   I also realised that switching mirrors (tazpkg -sm) is really dangerous when you have packages in the local cache (since it will pull from the cache, which came from another mirror).

   Sorry!

   1.Using packages DB: /cross/arm/sysroot/var/lib/tazpkg
   http://forum.slitaz.org/topic/slitaz-on-armel/page/2#post-28162

   vi /cross/arm/sysroot/var/lib/tazpkg/mirror <====

   http://cook.slitaz.org/cross/arm/packages/

   Or path/to/your_arm_packages

   2. add libtool

   libtools minefield

   Oops. I guess you figured it out a year earlier. Even with exactly the same link. :)

   add libtool

   2. Cross Toolchain
   http://cook.slitaz.org/cross/arm/toolchain.cgi

   Packages log: binutils eglibc gcc-final gcc-static libtool linux-headers
   

   Posted 10 years ago #
3. 

   pirandr
   

   offline

   Member

   I just wanted to drop a quick note.

   xorg-server-light

   I just cooked xorg-server-light, but used a few hacks for now. I haven't tested it yet on the Pi.

   https://github.com/pirandr/slitaz-arm/blob/master/cross-compiled/xorg-server-light-1.12.4-arm.tazpkg

   The main problem (aside from the glibc-dev issue) was that it look for libraries in /usr/lib instead of /cross/arm/sysroot/usr/lib. For the hack I ran sed against all generated Makefiles, which I strongly advise against doing in a final solution.

   Some possibilities are to explicitly pass the path to configure for these libraries (I think there are only 2 or 3 in the end). Or maybe even make a custom pkg-config for cross compilation (since configure calls pkg-config to get these paths).

   In the receipt I had, there was a typo setting up ARM_LIBS but also these extra lines (I think which were added for ARM)

   <br />
   XSERVERCFLAGS_LIBS="-L${ARM_LIBS} -lrt -lpthread -lgcrypt -lm -lz \<br />
   -lcrypto -lpixman -lxkbfile -lXfont -lfreetype -lXau -lfontenc -lXdmcp" \<br />
   XSERVERLIBS_LIBS="-L${ARM_LIBS} -lrt -lpthread -lgcrypt -lm -lz \<br />
   -lcrypto -lpixman -lxkbfile -lXfont -lfreetype -lXau -lfontenc -lXdmcp" \<br />

   which ended up doing more harm than good (I already removed -lmd here). If they were only added to help with the arm build, maybe just keeping -L${ARM_LIBS} in each case will be enough (haven't tested this yet either).

   Cross compilation libtool

   Thanks! I've add libtool to cross now.

   Setting mirror

   No problem. It didn't really cause much trouble. I'll try that way next.

   Posted 10 years ago #
4. 

   alanyih
   

   offline

   Administrator

   Cross compilation libtool
   Thanks! I've add libtool to cross now.

   Build time : 7094s ~ 118m

   How long Build time?

   slitaz-arm-toolchain-20140310.tar.bz2
   https://github.com/pirandr/slitaz-arm/blob/master/slitaz-arm-toolchain-20140310.tar.bz2

   file 49745.431 kb

   slitaz-arm-toolchain-20140311.tar.bz2
   https://github.com/pirandr/slitaz-arm/blob/master/slitaz-arm-toolchain-20140311.tar.bz2

   file 50066.873 kb

   Summary - arm

   Packages: 275 in the wok - 267 cooked - 8 unbuilt - Server date: 2014-03-13 13:51 CET

   Posted 10 years ago #
5. 

   alanyih
   

   offline

   Administrator

   RasppberryPi

   SoC: Broadcom BCM2835 (CPU + GPU. SDRAM is a separate chip stacked on top)

   CPU: 700 MHz ARM11 ARM1176JZF-S core

   GPU: Broadcom VideoCore IV,OpenGL ES 2.0,OpenVG 1080p30 H.264 high-profile encode/decode

   Memory (SDRAM):256 MB / 512 MB

   MK802 II

   Main Chip: Allwinner A10/ 1GHz Cortex-A8

   Memory: 1GB

   Storage: 4GB, Micro SD 2-32GB Memory

   GPU: Mali400

   Radxa Rock

   SOC Rockchip RK3188

   CPU ARM Cortex-A9 quad core @ 1.6Ghz

   Memory 1GB / 2GB DDR3 @ 800Mhz

   Storage 4GB / 8GB NAND Flash, Micro-SD SDXC up to 128GB

   GPU Mali400-mp4@533Mhz, OpenGL ES 2.0

   Comparison of current ARM cores
   http://en.wikipedia.org/wiki/Comparison_of_current_ARM_cores

   

   Attachments

   1. ArmBaseChip.jpg (145.8 KB, 1,645 downloads) 10 years old
   2. ArmArchitecture.jpg (61.2 KB, 1,695 downloads) 10 years old
   3. ArmRoadMap.jpg (41.3 KB, 1,559 downloads) 10 years old

   Posted 10 years ago #
6. 

   pirandr
   

   offline

   Member

   ARM based devices comparison

   Very interesting. When you said Allwinner and Mali400, I thought you were talking about the Cubieboard. I hadn't heard about the MK802 II before.

   Its too bad there's no open GPU driver (well, the Raspberry Pi is now the closest with the recent announcement).

   Toolchain build time

   Yeah, 2 hours seems about right for building the cross compilation toolchain (memory's a bit fuzzy here). But just adding libtool didn't take very long.

   Posted 10 years ago #
7. 

   alanyih
   

   offline

   Administrator

   Open Source Mali-200/300/400/450 GPU Kernel Device Drivers
   http://malideveloper.arm.com/develop-for-mali/drivers/open-source-mali-gpus-linux-kernel-device-drivers/

   Source code for Mali GPUs Kernel Device Drivers, UMP Device Drivers and DRM Device Drivers under GPLv2 licence

   The Linux and Android version of the Mali GPUs DDKs include three components which run within the kernel. The most important of these, known as the Device Driver, provides the low-level access to the Mali-200, Mali-300, Mali-400 and Mali-450 GPU. An important, secondary component is the Unified Memory Provider (UMP) which can be used in a variety of ways to facilitate zero-copy operations within the driver stack. An additional component, the Mali Direct Rendering Manager (DRM), is provided to integrate the Mali GPU DDKs into the X11 environment and for enabling the Direct Rendering Interface (DRI2).

   Posted 10 years ago #
8. 

   alanyih
   

   offline

   Administrator

   Radxa Rock

   SOC Rockchip RK3188
   CPU ARM Cortex-A9 quad core @ 1.6Ghz

   1.
   rock@slitaz:~$ uname -a
   Linux slitaz 3.0.36+ #1 SMP PREEMPT Thu Apr 3 20:41:51 UTC 2014 armv7l armv7l armv7l GNU/Linux

   2.
   rock@slitaz:~$ dmesg | head -5
   [ 0.000000] Initializing cgroup subsys cpu
   [ 0.000000] Linux version 3.0.36+ (root@slitaz) (gcc version 4.6.3 (SliTaz) ) #1 SMP PREEMPT Thu Apr 3 20:41:51 UTC 2014
   [ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c5387d
   [ 0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
   [ 0.000000] Machine: RK30board

   3.
   rock@slitaz:~$ lscpu
   Architecture: armv7l
   Byte Order: Little Endian
   CPU(s): 4
   On-line CPU(s) list: 0-3
   Thread(s) per core: 1
   Core(s) per socket: 1
   Socket(s): 4

   4.
   rock@radxa:~$ free -m
   total used free shared buffers cached
   Mem: 1852 160 1692 0 10 59
   -/+ buffers/cache: 89 1763
   Swap: 0 0 0

   5.
   rock@radxa:~$ df -h
   Filesystem Size Used Avail Use% Mounted on
   /dev/mtdblock1 7.4G 1.8G 5.3G 25% /
   udev 924M 68K 924M 1% /dev
   none 4.0K 0 4.0K 0% /sys/fs/cgroup
   none 186M 212K 186M 1% /run
   none 5.0M 0 5.0M 0% /run/lock
   none 927M 0 927M 0% /run/shm
   none 100M 12K 100M 1% /run/user
   rock@radxa:~$

   

   Attachments

   1. radxa-slitaz.png (88.3 KB, 1,520 downloads) 10 years old

   Posted 10 years ago #
9. 

   alanyih
   

   offline

   Administrator

   GPU Mali400-mp4@533Mhz, OpenGL ES 2.0

   1.
   rock@slitaz:~$ lsmod
   Module Size Used by
   mali_drm 5196 1
   drm 142897 2 mali_drm
   mali 127376 0
   ump 27356 3 mali
   8723au 849716 0
   rk30xxnand_ko 161856 0

   2.
   rock@slitaz:~$ modinfo mali
   filename: /lib/modules/3.0.36+/kernel/misc/mali.ko
   version: r3p2-01rel2
   author: ARM Ltd.
   license: GPL
   srcversion: 2DCA5E55A6EDAA8348F84D8
   depends: ump
   vermagic: 3.0.36+ SMP preempt mod_unload ARMv7
   parm: mali_debug_level:Higher number, more dmesg output (int)
   parm: mali_max_job_runtime:Maximum allowed job runtime in msecs.
   Jobs will be killed after this no matter what (int)
   parm: mali_l2_max_reads:Maximum reads for Mali L2 cache (int)
   parm: mali_dedicated_mem_start:Physical start address of dedicated Mali GPU memory. (uint)
   parm: mali_dedicated_mem_size:Size of dedicated Mali GPU memory. (uint)
   parm: mali_shared_mem_size:Size of shared Mali GPU memory. (uint)
   parm: mali_boot_profiling:Start profiling as a part of Mali driver initialization (int)
   parm: mali_max_pp_cores_group_1:Limit the number of PP cores to use from first PP group. (int)
   parm: mali_max_pp_cores_group_2:Limit the number of PP cores to use from second PP group (Mali-450 only). (int)

   3.
   rock@slitaz:~$ es2gears
   EGL_VERSION = 1.4 Linux-r3p2-01rel2
   vertex shader info:
   fragment shader info:
   info:
   1569 frames in 5.0 seconds = 313.800 FPS
   1596 frames in 5.0 seconds = 319.072 FPS
   1551 frames in 5.0 seconds = 310.200 FPS
   1508 frames in 5.0 seconds = 301.419 FPS

   4.
   rock@slitaz:~$ glmark2-es2
   =======================================================
   glmark2 2012.08
   =======================================================
   OpenGL Information
   GL_VENDOR: ARM
   GL_RENDERER: Mali-400 MP
   GL_VERSION: OpenGL ES 2.0
   =======================================================
   [build] use-vbo=false: FPS: 75 FrameTime: 13.333 ms
   [build] use-vbo=true: FPS: 80 FrameTime: 12.500 ms
   [texture] texture-filter=nearest: FPS: 95 FrameTime: 10.526 ms
   [texture] texture-filter=linear: FPS: 94 FrameTime: 10.638 ms
   [texture] texture-filter=mipmap: FPS: 95 FrameTime: 10.526 ms
   [shading] shading=gouraud: FPS: 61 FrameTime: 16.393 ms
   [shading] shading=blinn-phong-inf: FPS: 52 FrameTime: 19.231 ms
   [..]

   [conditionals] fragment-steps=0:vertex-steps=0: FPS: 114 FrameTime: 8.772 ms
   [conditionals] fragment-steps=5:vertex-steps=0: FPS: 72 FrameTime: 13.889 ms
   [conditionals] fragment-steps=0:vertex-steps=5: FPS: 107 FrameTime: 9.346 ms
   [function] fragment-complexity=low:fragment-steps=5: FPS: 85 FrameTime: 11.765 ms
   [function] fragment-complexity=medium:fragment-steps=5: FPS: 58 FrameTime: 17.241 ms
   [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 81 FrameTime: 12.346 ms
   [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 84 FrameTime: 11.905 ms
   [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 91 FrameTime: 10.989 ms
   =======================================================
   glmark2 Score: 81
   =======================================================
   rock@slitaz:~$

   Posted 10 years ago #
10. 

    alanyih
    

    offline

    Administrator

    Welcome to Radxa Rock
    SliTaz boot time: 5s

    1.
    root@slitaz:~# uname -a
    Linux slitaz 3.10.30-slitaz #1 SMP PREEMPT Tue May 13 19:39:35 UTC 2014 armv7l GNU/Linux

    2.
    root@slitaz:~# dmesg | grep Machine
    [ 0.000000] Machine: RK30board, model: rockchip,rk3188

    3.
    root@slitaz:~# date
    Wed May 14 14:45:01 UTC 2014

    4.
    root@slitaz:~# nslookup http://www.slitaz.org
    Server: 192.168.0.1
    Address 1: 192.168.0.1 dir-605

    Name: http://www.slitaz.org
    Address 1: 46.105.127.17 ks385316.kimsufi.com
    Address 2: 212.83.135.187 pangolin.slitaz-fr.org

    5.
    root@slitaz:~# slitaz

    SliTaz GNU/Linux
    ================================================================================================================================================================
    Release : cooking
    Architecture : arm
    Kernel : 3.10.30-slitaz
    Boot options : clk_ignore_unused console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p2 rw rootfstype=ext4 init=/sbin/init mac_addr=de:ad:de:ad:be:ef initrd=0x62000000,0x003E0000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot) bootver=2013-12-02#2.08 firmware_ver=4.2.2
    Home path : /home/slitaz
    Configs : /etc/slitaz
    Log files : /var/log/slitaz
    Packages DB : /var/lib/tazpkg
    Installed : 18 packages
    Mirror : http://arm.balinor.net/slitaz/armhf/packages/
    ================================================================================================================================================================
    Config file: /etc/slitaz/slitaz.conf

    

    Attachments

    1. radxa-slitaz.jpg (130 KB, 1,764 downloads) 10 years old

    Posted 10 years ago #
11. 

    alanyih
    

    offline

    Administrator

    Radxa Rock - device-tree

    1.
    Starting udhcpc client on: eth0...
    udhcpc (v1.20.2) started
    Sending discover...
    Sending discover...
    Sending discover...
    No lease, forking to background
    Processing: /etc/init.d/local.sh
    Starting all daemons...
    Generating Dropbear rsa key... [ Done ]
    Generating Dropbear dss key... [ Done ]
    Starting SSH server: Dropbear... [ Done ]

    Welcome to Radxa Rock
    SliTaz boot time: 6s

    2.
    root@slitaz:~# dmesg | grep -B 3 Machine
    [ 0.000000] Linux version 3.10.37-slitaz (root@slitaz) (gcc version 4.6.3 (SliTaz) ) #1 SMP PREEMPT Fri May 16 13:57:21 UTC 2014
    [ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c53c7d
    [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
    [ 0.000000] Machine: RK30board, model: rockchip,rk3188

    3.
    root@slitaz:~# ls /proc/device-tree

    #address-cells nandc
    #size-cells pinctrl@20008000
    adc@2006c000 pmu@20004000
    aliases pwm@20030000
    amba pwm@20030010
    ap0-vcc-domain pwm@20050020
    ap1-vcc-domain pwm@20050030
    backlight rga@10114000
    bootram@10080000 rk_screen
    bootrom@10120000 rksdmmc@10214000
    cache-controller@10138000 rksdmmc@10218000
    chosen rksdmmc@1021C000
    cif-vcc-domain rockchip,sram
    clocks rockchip-hdmi-i2s
    clocks-init rockchip-hdmi-spdif
    codec-hdmi-i2s rockchip-i2s@0x1011a000
    codec-hdmi-spdif rockchip-spdif@0x1011e000
    compatible rockchip_suspend
    cpu_axi_bus serial@10124000
    cpus serial@10126000
    dvfs serial@20064000
    dwc-control-usb@200080ac serial@20068000
    fb spi@20070000
    fiq-debugger spi@20074000
    flash-vcc-domain sram@10080020
    hsic@10240000 timer@20038000
    i2c@2002d000 timer@20038020
    i2c@2002f000 timer@20038040
    i2c@20056000 timer@20038060
    i2c@2005a000 timer@20038080
    i2c@2005e000 timer@200380a0
    interrupt-controller@1013d000 twd-wdt@1013c620
    interrupt-parent usb@10180000
    ion usb@101c0000
    lcdc0-vcc-domain vccio0-vcc-domain
    lcdc1-vcc-domain vccio1-vcc-domain
    lcdc@1010c000 vmac-phy
    lcdc@1010e000 vmac@10204000
    memory wdt@2004c000
    name wireless-wlan

    4.
    root@slitaz:~# cat /proc/device-tree/compatible
    rockchip,rk3188root@slitaz:~#

    root@slitaz:~# cat /proc/device-tree/chosen/bootargs
    clk_ignore_unused console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p2 rw rootfstype=ext4 init=/sbin/init mac_addr=de:ad:de:ad:be:ef initrd=0x62000000,0x003E0000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot) bootver=2013-12-02#2.08 firmware_ver=4.2.2

    root@slitaz:~# cat /proc/device-tree/wireless-wlan/compatible
    wlan-platdataroot@slitaz:~#

    

    Attachments

    1. radxa-slitaz-devicetree.jpg (144.4 KB, 1,523 downloads) 10 years old

    Posted 10 years ago #
12. 

    devl547
    

    offline

    ~ # cook my_life

    >Radxa Rock - device-tree
    >Linux version 3.10.37

    Yarrr!!! I have a Minix Neo X7 as my home server (currently using gentoo).
    Too bad there is no devicetree and 3.10 kernel support for it. And AFAIK I cannot use internal NAND storage (only SD).

    And you also have 3D working...
    Man, can you please write a short guide for installing slitaz on raxda (kernel, drivers, etc)?

    Posted 10 years ago #
13. 

    alanyih
    

    offline

    Administrator

    Ref:

    Ubuntu 14.04 and Slitaz on Radxa Rock
    http://www.cnx-software.com/2014/05/18/ubuntu-14-04-and-slitaz-on-radxa-rock/

    First download boot-slitaz-20140517.img (kernel + slitaz ramdisk), then follow the 「Flashing Ubuntu to Radxa Rock」 section in my getting started guide for Radxa Rock to flash boot.img. It is simply one line:

    upgrade_tool di -b /path-to/boot-slitaz-20140517.img

    Simply login with root username, and root password to access the command line. It might also be possible to use a more up-to-date rootfs from http://arm.slitaz.org/rpi/, but it is only armel.

    [Update: Alanyih has also been given me the build instructions for his Slitaz image:

    git clone -b wip/lsk-android-14.04-radxa-rock https://github.com/linux-rockchip/kernel_rockchip.git

    make radxa_rock_defconfig

    make zImage rk3188-radxa-rock.dtb

    cat arch/arm/boot/zImage arch/arm/boot/dts/rk3188-radxa-rock.dtb > zImage-lsk

    mkbootimg --kernel zImage-lsk --ramdisk slitaz-ramdisk.gz -o boot-slitaz-20140517.img

    ]

    Both Ubuntu 14.04 and Slitaz should be able to run on any Rockchip RK3188 device thanks to the device tree and multi-platform enabled Linux kernel, as long as you can somehow come up with the right device file for your device, which may not always be an easy task.

    boot-slitaz-20140517.img (kernel + slitaz ramdisk)
    http://goo.gl/Mc7L4q

    Posted 10 years ago #

RSS feed for this topic

Reply

You must log in to post.