The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)


Search results

From Mer Wiki
Jump to: navigation, search

Page title matches

  • = ARM in Mer = Mer uses and discusses ARM technology extensively - however the terminology is complex and certainly c
    3 KB (503 words) - 12:38, 24 January 2012

Page text matches

  • 12) For arm, repeat steps 8) to 11), replacing i586 with armv7hl. For step 9)
    21 KB (3,315 words) - 12:08, 6 December 2011
  • .../etc/sysconfig/obs-server are well commented. One that needs to be set for ARM builds is:
    9 KB (1,352 words) - 13:56, 24 April 2012
  • To compile the kernel for the touchpad you should have an arm cross compiler environnement set up and use the following comamnds : mkimage -A arm -O Linux -T ramdisk -n 'Meego boot initrd' -C none -e 0 -a 0 -d initramfs.c
    3 KB (533 words) - 00:24, 13 January 2013
  • cat /proc/sys/fs/binfmt_misc/arm 17:22] <Stskeeps> arc_mat: ls -l /usr/bin/qemu-arm
    1 KB (208 words) - 10:53, 8 February 2012
  • # Set this to 1 if there are x86 cross- binaries in the arm/mips repos ...is needed for building non-native (ARM/MIPS) packages that need to execute ARM binaries.
    8 KB (1,253 words) - 21:34, 27 June 2016
  • = ARM in Mer = Mer uses and discusses ARM technology extensively - however the terminology is complex and certainly c
    3 KB (503 words) - 12:38, 24 January 2012
  • The old approach was similar to what was developed in the MeeGo project for ARM cross compilation, injecting X86 binaries into the build environment. With which successfully compiles all the Mer core packages for these ARM architectures.
    13 KB (2,027 words) - 11:51, 22 October 2014
  • X86 side into ARM side and not like we have now, where glibc effectively gets injected from ARM side for a cross compiler to be made.
    1 KB (206 words) - 20:08, 16 December 2011
  • * cp ../nook_kernel/arch/arm/boot/uImage <mount target>
    6 KB (974 words) - 16:28, 11 November 2012
  • ==== When compiling kernel for ARM with Mer 0.20110105.1 or newer ==== ==== When compiling arm kernels < 2.6.36 ====
    2 KB (313 words) - 13:00, 29 January 2013
  • creating arm images needs 'qemu-arm' os 'qemu-arm-static' command available, and creating vdi or vmdk images needs 'vboxmanag ===ARM related issues===
    28 KB (4,317 words) - 20:33, 10 June 2014
  • Booting any random ARM device you typically have u-boot as boot-loader, some guidance on setting u
    14 KB (2,171 words) - 16:51, 27 June 2013
  • * ``arm:`` - arm platform - arm:pkg-need-in-arm-image
    14 KB (1,828 words) - 17:44, 10 August 2013
  • * #TODO: kickstart files for arm
    3 KB (408 words) - 10:35, 1 February 2012
  • * Boot with 128M/128M memory split (128M for the ARM, 128M for the GPU) ... creating a ''target'' (an unpacked rootfs) and using sb2 to "emulate" the ARM device.
    9 KB (1,384 words) - 23:46, 16 February 2014
  • sb2-init -d -L "--sysroot=/" -C "--sysroot=/" -c /usr/bin/qemu-arm-dynamic -m sdk-build -n -N -t / mer-target-armv7hl /opt/cross/bin/armv7hl-m sb2-init -L "--sysroot=/" -C "--sysroot=/" -c /usr/bin/qemu-arm-dynamic -m sdk-build -n -N -t / TARGETNAME /opt/cross/bin/armv7hl-meego-lin
    15 KB (2,448 words) - 11:35, 23 May 2014
  • ==ARM==
    1 KB (162 words) - 17:43, 5 September 2016
  • If you need to build for ARM too then you can add a suitable target just before the </project> :
    5 KB (713 words) - 09:56, 23 March 2014
  • ...pm-files to the one directory. If you just build them with 'osc build' for arm, directory is '''/var/tmp/build-root/home/abuild/rpmbuild/RPMS/armv7hl/'''
    631 B (107 words) - 13:27, 3 August 2012
  • ... creating a ''target'' (an unpacked rootfs) and using sb2 to "emulate" the ARM device. ...it -A armv7hl -M armv7hl -d -L --sysroot=/ -C --sysroot=/ -c /usr/bin/qemu-arm-dynamic -m sdk-build -n -N -t / tegra3 /opt/cross/bin/armv7hl-meego-linux-g
    3 KB (479 words) - 14:06, 5 February 2013

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Views
Personal tools