May 2014 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] Re: [opensuse-kernel] [PATCH] ARM: update armv7 default config - master branch
by Guillaume Gardet 11 Jun '14

11 Jun '14

CC'ing -arm ML Le 03/04/2014 13:48, Alexander Graf a écrit : > > On 03.04.14 13:47, Guillaume Gardet wrote: >> Le 03/04/2014 13:39, Alexander Graf a écrit : >>> On 02.04.14 20:48, Guillaume Gardet wrote: >>>> Hi, >>>> >>>> please find in attachment an ARMv7 -default config update to fix Ethernet and HDMI output on iMX6 SABRE Lite board. It also add initial support to USB on this board. >>>> >>>> This patch is against master branch. >>>> >>>> Signed-off-by: Guillaume GARDET <guillaume.gardet(a)opensuse.org> >>> Moving modules from =m to =y is the wrong answer usually. Why don't the modules work as modules? >> I do not know. >> Modules are loaded with no error but they do not work. The fact is switching FEC and SDMA from =m to =y fix the problems. It is true for 13.1 and master branches. > > Yes, I've spent some time myself to fix FEC as a module on i.MX53 a while ago. We really don't want to even start going into the game of enabling random devices as =y on the default config, otherwise we'll end up with a 30MB kernel on all boards. I agree, but the fact is we have no board which works really fine ATM. See: http://en.opensuse.org/openSUSE:Supported_ARM_boards#13.1 There are only RPi and Chromebook which have a correct support (and they use _downstream_ kernels). But chromebook boot only once and need a hack to boot then (I am on it, Marcus gave me some hints to fix that using kiwi hooks) and had a lot of X stability problems (random freezes, X crash when switching VT). Raspberry Pi is not booting at all as is (kiwi partitioning bug) and need a hack to get a bootable image: http://en.opensuse.org/HCL:Raspberry_Pi#Known_Issues Maybe Beaglebone or Beaglebone black have a good support? (I do not have such devices and there is no feedback on our wiki) Now, SABRE Lite is the only board where I got graphics working with upstream kernel. The last blocking problem on this board is USB which is not working, even with imx_v6_v7_defconfig. The main things to do for boards support are : 1) Get boards booting Linux (should be a minimum). 2) Have a maximum number of supported devices (USB, sound, video, etc.) on each board (even if it does mean to have '=y' instead of '=m'). 3) Clean-up / fix our kernel / kernel configs to use modules (=m) instead of built-in (=y) when it is possible. I think we should use again our Trello board or setup a wiki page or something to write down what must be done for each board and who is taking care of each task. What do you think about that? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 5

[opensuse-arm] kernel-default 3.15-rc5 build failing on armv7l
by Andreas Färber 05 Jun '14

05 Jun '14

Hello, And another build failure: [ 7576s] CC [M] drivers/gpu/drm/msm/msm_fbdev.o [ 7578s] /home/abuild/rpmbuild/BUILD/kernel-default-3.15.rc5/linux-3.15-rc5/drivers/gpu/drm/msm/msm_fbdev.c: In function 'msm_fbdev_create': [ 7578s] /home/abuild/rpmbuild/BUILD/kernel-default-3.15.rc5/linux-3.15-rc5/drivers/gpu/drm/msm/msm_fbdev.c:108:2: error: passing argument 3 of 'msm_gem_get_iova_locked' from incompatible pointer type [-Werror] [ 7578s] msm_gem_get_iova_locked(fbdev->bo, 0, &paddr); [ 7578s] ^ [ 7578s] In file included from /home/abuild/rpmbuild/BUILD/kernel-default-3.15.rc5/linux-3.15-rc5/drivers/gpu/drm/msm/msm_fbdev.c:18:0: [ 7578s] /home/abuild/rpmbuild/BUILD/kernel-default-3.15.rc5/linux-3.15-rc5/drivers/gpu/drm/msm/msm_drv.h:153:5: note: expected 'uint32_t *' but argument is of type 'dma_addr_t *' [ 7578s] int msm_gem_get_iova_locked(struct drm_gem_object *obj, int id, [ 7578s] ^ [ 7578s] cc1: all warnings being treated as errors [ 7578s] /home/abuild/rpmbuild/BUILD/kernel-default-3.15.rc5/linux-3.15-rc5/scripts/Makefile.build:334: recipe for target 'drivers/gpu/drm/msm/msm_fbdev.o' failed [ 7578s] make[6]: *** [drivers/gpu/drm/msm/msm_fbdev.o] Error 1 [ 7578s] /home/abuild/rpmbuild/BUILD/kernel-default-3.15.rc5/linux-3.15-rc5/scripts/Makefile.build:495: recipe for target 'drivers/gpu/drm/msm' failed [ 7578s] make[5]: *** [drivers/gpu/drm/msm] Error 2 [ 7578s] /home/abuild/rpmbuild/BUILD/kernel-default-3.15.rc5/linux-3.15-rc5/scripts/Makefile.build:495: recipe for target 'drivers/gpu/drm' failed [ 7578s] make[4]: *** [drivers/gpu/drm] Error 2 [ 7578s] /home/abuild/rpmbuild/BUILD/kernel-default-3.15.rc5/linux-3.15-rc5/scripts/Makefile.build:495: recipe for target 'drivers/gpu' failed [ 7578s] make[3]: *** [drivers/gpu] Error 2 [ 7578s] /home/abuild/rpmbuild/BUILD/kernel-default-3.15.rc5/linux-3.15-rc5/Makefile:904: recipe for target 'drivers' failed [ 7578s] make[2]: *** [drivers] Error 2 [ 7578s] Makefile:148: recipe for target 'sub-make' failed [ 7578s] make[1]: *** [sub-make] Error 2 [ 7578s] Makefile:26: recipe for target 'all' failed [ 7578s] make: *** [all] Error 2 I guess disabling the msm DRM module would be the easiest workaround. Won't get around to it right away myself. Guillaume? Also, can anyone drop x86_64 from "ARM" repository in Kernel:HEAD? https://build.opensuse.org/project/repositories/Kernel:HEAD Similarly, why is armv6l selected for "Ports" but not armv7l? Would've expected it the other way around. Regards, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

6 10

[opensuse-arm] vexpress
by Matwey V. Kornilov 02 Jun '14

02 Jun '14

Hi, Why kernel/initrd tarball is not published for Factory? Is there a way to boot the image in qemu from .raw? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 1

[opensuse-arm] barebox bootloader
by Matwey V. Kornilov 29 May '14

29 May '14

Hi, What do you think about supporting barebox as arm-bootloader in parallel with u-boot? Is it going to be successor of u-boot? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] Factory signing key(s) expired
by Andreas Färber 22 May '14

22 May '14

Hello, Both for ARMv6 and for ARMv7 I've been getting the warning that the signing key of the Factory repository has expired on May 4th. Warnung:The gpg key signing file 'content' has expired. Repository: openSUSE-Factory-repo-oss Key Name: openSUSE Project Signing Key <opensuse(a)opensuse.org> Key Fingerprint: 22C07BA534178CD02EFE22AAB88B2FD43DBDC284 Key Created: Fr 07 Nov 2008 15:10:07 CET Key Expires: So 04 Mai 2014 17:01:33 CEST (ABGELAUFEN) Rpm Name: gpg-pubkey-3dbdc284-49144c3f Is anyone aware of that and working on a fix? Thanks, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 6

[opensuse-arm] kernel-default 3.15-rc5 working on Raspberry Pi
by Andreas Färber 20 May '14

20 May '14

Hello, I have succeeded in booting our newly built kernel-default package from Kernel:HEAD on the Raspberry Pi model B with Factory and 3.15-rc2+. Here's a quick how-to: In yast, add Kernel:HEAD repository: http://download.opensuse.org/repositories/Kernel:/HEAD/ARM/ Install the kernel package: # zypper in kernel-default-3.15.rc5 Prepare initrd settings in /etc/sysconfig/kernel: INITRD_MODULES="sdhci-bcm2835" Create an initrd: # mkinitrd -v -k zImage-3.15.0-rc5-6.g923c7d2-default \ -i initrd-3.15.0-rc5-6.g923c7d2-default Make the files accessible to U-Boot: # cd /boot # ln -sf zImage-3.15.0-rc5-6.g923c7d2-default zImage # ln -sf initrd-3.15.0-rc5-6.g923c7d2-default initrd In your boot.scr make sure that the initrd is loaded as well, e.g.: setenv bootargs 'console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p3 rootfstype=ext4 rw rootwait dwc_otg.lpm_enable=0' ext2load mmc 0:2 ${kernel_addr_r} zImage ext2load mmc 0:2 ${fdt_addr_r} dtb/bcm2835-rpi-b.dtb ext2load mmc 0:2 ${ramdisk_addr_r} initrd bootz ${kernel_addr_r} ${ramdisk_addr_r}:0x${filesize} ${fdt_addr_r} # mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n Boot-Script \ -d boot.script .../boot.scr Now what's still missing for a proper JeOS image is the QEMU problem with partitioning in Kiwi, and right now the build is unresolvable. Cheers, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 3

[opensuse-arm] Chromebook boot fixed, please accept SR #234660
by Guillaume Gardet 19 May '14

19 May '14

Hi, I fixed Chromebook boot after fisrt boot repartition with Marcus help. Please accept SR #234660 I also removed eth0 configuration for chromebook and added a wlan0 interface. That way, the wireless interface show up by default in YaST lan module. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 5

[opensuse-arm] kernel-exynos 3.15-rc5 build failure
by Andreas Färber 19 May '14

19 May '14

Hi, kernel-exynos is failing as follows: [22654s] drivers/built-in.o: In function `exynos_drm_attach_lcd_bridge': [22654s] /home/abuild/rpmbuild/BUILD/kernel-exynos-3.15.rc5/linux-3.15-rc5/drivers/gpu/drm/exynos/exynos_dp_core.c:1004: undefined reference to `ptn3460_init' [22669s] /home/abuild/rpmbuild/BUILD/kernel-exynos-3.15.rc5/linux-3.15-rc5/Makefile:882: recipe for target 'vmlinux' failed [22669s] make[2]: *** [vmlinux] Error 1 [22669s] Makefile:148: recipe for target 'sub-make' failed [22669s] make[1]: *** [sub-make] Error 2 [22669s] Makefile:26: recipe for target 'all' failed [22669s] make: *** [all] Error 2 https://build.opensuse.org/package/live_build_log/Kernel:HEAD/kernel-exynos… Anyone any insights how to resolve? Regards, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 5

Re: [opensuse-arm] Installing on semi-custom OK210 board.....
by Isaac Martinez G. 19 May '14

19 May '14

Thank you very much for bringing some light into this... I got the files from the manufacturer.... They built U-boot, then the linux kernel...then the created the image for flashing the board... Everything in Ubuntu Now, I am trying to do it on opensuse.... 1.-Building U-boot.. I get the following: make: arm-none-linux-gnueabi-gcc: Command not found I got the ARM crosscompiler in opensuse... cross-armv7hl-gcc47-icecream-backend - The GNU C Compiler and Support Files Is that the equivalent of the gnueabi??? I tried to find some answer online, but everything is for another distribution... not Suse... How can it be done using the suse x-compiler??? On Sunday, May 18, 2014 10:15 AM, Andreas Färber <afaerber(a)suse.de> wrote: Hi, Am 17.05.2014 20:22, schrieb Isaac Martinez G.: > > I got an ARM board on Ebay from Forlinx embedded. > Nice piece of hardware and planing to use to control an exotic piece of laboratory equipment. > > OK210 (you can search on Ebay for it) > > Architecture: Cortex-A8 > Processor: Samsung S5PV210 chip > 512MB of DDRII > 1GB of flash > > 1GHZ clock > > I took a look a the wiki... given that the board is obviously not on the list. > I downloaded the files (still deciding which one to use): > > openSUSE-13.1-ARM-JeOS.armv7-rootfs.armv7l-1.12.1-Build33.1.tbz > > and > > openSUSE-13.1-ARM-JeOS.armv7-rootfs.armv7l-1.12.1-Build33.1.tbz Those two look identical to me? ;) For a beginner, 13.1 is a safe choice, in case you were considering Factory as alternative (pretty usable recently, but you never know). > The instructions and wiki are not exactly great for non hardcore programmers. > > "And make your own SD card to boot on, with first bootloader > (manufacturer specific), U-Boot (configured for your board) and a kernel > (configured for your board) if openSUSE does not provide it" > > Could anybody explain or point out where I can get more information on actually how to do it???? The point is that there are no generic instructions, it does highly depend on the board. Usually the manufacturer's website has either instructions how to do it or a downloadable image that you can peek at using parted etc. Finding that information or figuring it out is the biggest obstacle in adding board support... Which bootloader(s) are required for the board? While I don't know the OK210, I have access to a board with an S5PV210: The armStoneA8 uses a preinstalled proprietary firmware NBoot in flash, which then loads U-Boot - also in flash. Other boards load U-Boot from an offset inside an unformatted first partition on the SD card, the Raspberry Pi even from a FAT partition. How can your bootloader load the kernel? U-Boot imposes how to further set up your partitions - in the best case your U-Boot is upstream and/or supports (or can be patched to support) ext4, then you can do one big ext4 partition with rootfs and kernel. Otherwise you'll have to prepend another partition for kernel/initrd, with preference from ext3, ext2 down to fat - I usually take ~100MB. Preference is usually for booting from SD card because of flexibility to fix on another machine or to some day exchange it in case of wear. Other boot options might include USB, SATA, TFTP and NFS. Which kernel format to choose? If bootz command is available in U-Boot, use a zImage; otherwise use a uImage (bootm command). Device trees S5PV210 does still not support the multi v7 kernel config upstream, so you can likely ignore anything you read about .dtb files for now. Graphics Note that the S5PV210 has a PowerVR SGX540 GPU, for which no real Open Source driver exists today: http://powervr.gnu.org.ve/doku.php HTH, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] Installing on semi-custom OK210 board.....
by Isaac Martinez G. 18 May '14

18 May '14

Hello everybody: Ok, I am a total beginner when it comes to install Suse on an embedded board. I got an ARM board on Ebay from Forlinx embedded. Nice piece of hardware and planing to use to control an exotic piece of laboratory equipment. OK210 (you can search on Ebay for it) Architecture: Cortex-A8 Processor: Samsung S5PV210 chip 512MB of DDRII 1GB of flash 1GHZ clock I took a look a the wiki... given that the board is obviously not on the list. I downloaded the files (still deciding which one to use): openSUSE-13.1-ARM-JeOS.armv7-rootfs.armv7l-1.12.1-Build33.1.tbz and openSUSE-13.1-ARM-JeOS.armv7-rootfs.armv7l-1.12.1-Build33.1.tbz The instructions and wiki are not exactly great for non hardcore programmers. "And make your own SD card to boot on, with first bootloader (manufacturer specific), U-Boot (configured for your board) and a kernel (configured for your board) if openSUSE does not provide it" Could anybody explain or point out where I can get more information on actually how to do it???? I am sort of clueless..... willing to share all what I get done on this little board. Thank you "Do not spend too much time in the lab, or you will get a one pack!!" (Instead of a six pack abs!!) "Do not spend too much time in the lab, or you will get a one pack!!" (Instead of a six pack abs!!) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1