- openSUSE ARM

[opensuse-arm] unexpected reloc type 0x03 for libxml2
by Guillaume Gardet 07 May '12

07 May '12

Hi, On my BeagleBoard xM, I did a zypper up and while installing libgdk_pixbuf-2_0-0-2.26.0-1.2 I got this warning/error: ******************************************************************************** Installing: libgdk_pixbuf-2_0-0-2.26.0-1.2 [done] Additional rpm output: g_module_open() failed for /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: /usr/lib/libxml2.so.2: unexpected reloc type 0x03 ******************************************************************************** Is it a known problem? I think it may lead to problems for apps using this lib. Regards, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 2

[opensuse-arm] ARM JeOS-* images are missing ld-linux.so.3
by Guillaume Gardet 06 May '12

06 May '12

Hi, armv7l use hard float, so it uses now ld-linux-armhf.so.3, no more ld-linux.so.3. So ARM JeOS-* images are broken. Guillaume -- 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] [Fwd: [fedora-arm] Fwd: [PATCH 2/2] ARM: audit: use only AUDIT_ARCH_ARM regardless of endianness]
by Andrew Wafaa 04 May '12

04 May '12

Could we also get this applied to our kernels, please? -------- Forwarded Message -------- From: Jon Masters <jonathan(a)jonmasters.org> To: arm <arm(a)lists.fedoraproject.org>, kernel(a)lists.fedoraproject.org Subject: [fedora-arm] Fwd: [PATCH 2/2] ARM: audit: use only AUDIT_ARCH_ARM regardless of endianness Date: Fri, 04 May 2012 13:24:34 -0400 Please apply to our Fedora kernels. -------- Original Message -------- Subject: [PATCH 2/2] ARM: audit: use only AUDIT_ARCH_ARM regardless of endianness Date: Fri, 4 May 2012 17:53:52 +0100 From: Will Deacon <will.deacon(a)arm.com> To: patches(a)arm.linux.org.uk CC: stable(a)vger.kernel.org The machine endianness has no direct correspondence to the syscall ABI, so use only AUDIT_ARCH_ARM when identifying the ABI to the audit tools in userspace. Cc: stable(a)vger.kernel.org Signed-off-by: Will Deacon <will.deacon(a)arm.com> KernelVersion: 3.4-rc5 --- arch/arm/kernel/ptrace.c | 8 +------- 1 files changed, 1 insertions(+), 7 deletions(-) diff --git a/arch/arm/kernel/ptrace.c b/arch/arm/kernel/ptrace.c index d8dbe9c..9650c14 100644 --- a/arch/arm/kernel/ptrace.c +++ b/arch/arm/kernel/ptrace.c @@ -906,12 +906,6 @@ long arch_ptrace(struct task_struct *child, long request, return ret; } -#ifdef __ARMEB__ -#define AUDIT_ARCH_NR AUDIT_ARCH_ARMEB -#else -#define AUDIT_ARCH_NR AUDIT_ARCH_ARM -#endif - asmlinkage int syscall_trace(int why, struct pt_regs *regs, int scno) { unsigned long ip; @@ -919,7 +913,7 @@ asmlinkage int syscall_trace(int why, struct pt_regs *regs, int scno) if (why) audit_syscall_exit(regs); else - audit_syscall_entry(AUDIT_ARCH_NR, scno, regs->ARM_r0, + audit_syscall_entry(AUDIT_ARCH_ARM, scno, regs->ARM_r0, regs->ARM_r1, regs->ARM_r2, regs->ARM_r3); if (!test_thread_flag(TIF_SYSCALL_TRACE)) -- 1.7.4.1 -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html _______________________________________________ arm mailing list arm(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F

1 0

[opensuse-arm] [Fwd: [fedora-arm] Fwd: [PATCH 1/2] ARM: audit: fix treatment of saved ip register during syscall tracing]
by Andrew Wafaa 04 May '12

04 May '12

Could we also get this applied to our kernels, please? -------- Forwarded Message -------- From: Jon Masters <jonathan(a)jonmasters.org> To: arm <arm(a)lists.fedoraproject.org>, kernel(a)lists.fedoraproject.org Subject: [fedora-arm] Fwd: [PATCH 1/2] ARM: audit: fix treatment of saved ip register during syscall tracing Date: Fri, 04 May 2012 13:24:04 -0400 Please apply to our Fedora kernels. -------- Original Message -------- Subject: [PATCH 1/2] ARM: audit: fix treatment of saved ip register during syscall tracing Date: Fri, 4 May 2012 17:52:02 +0100 From: Will Deacon <will.deacon(a)arm.com> To: patches(a)arm.linux.org.uk CC: stable(a)vger.kernel.org The ARM audit code incorrectly uses the saved application ip register value to infer syscall entry or exit. Additionally, the saved value will be clobbered if the current task is not being traced, which can lead to libc corruption if ip is live (apparently glibc uses it for the TLS pointer). This patch fixes the syscall tracing code so that the why parameter is used to infer the syscall direction and the saved ip is only updated if we know that we will be signalling a ptrace trap. Cc: stable(a)vger.kernel.org Cc: Eric Paris <eparis(a)redhat.com> Reported-and-tested-by: Jon Masters <jcm(a)jonmasters.org> Signed-off-by: Will Deacon <will.deacon(a)arm.com> KernelVersion: 3.4-rc5 --- arch/arm/kernel/ptrace.c | 16 ++++++++-------- 1 files changed, 8 insertions(+), 8 deletions(-) diff --git a/arch/arm/kernel/ptrace.c b/arch/arm/kernel/ptrace.c index 80abafb..d8dbe9c 100644 --- a/arch/arm/kernel/ptrace.c +++ b/arch/arm/kernel/ptrace.c @@ -916,14 +916,7 @@ asmlinkage int syscall_trace(int why, struct pt_regs *regs, int scno) { unsigned long ip; - /* - * Save IP. IP is used to denote syscall entry/exit: - * IP = 0 -> entry, = 1 -> exit - */ - ip = regs->ARM_ip; - regs->ARM_ip = why; - - if (!ip) + if (why) audit_syscall_exit(regs); else audit_syscall_entry(AUDIT_ARCH_NR, scno, regs->ARM_r0, @@ -936,6 +929,13 @@ asmlinkage int syscall_trace(int why, struct pt_regs *regs, int scno) current_thread_info()->syscall = scno; + /* + * IP is used to denote syscall entry/exit: + * IP = 0 -> entry, =1 -> exit + */ + ip = regs->ARM_ip; + regs->ARM_ip = why; + /* the 0x80 provides a way for the tracing parent to distinguish between a syscall stop and SIGTRAP delivery */ ptrace_notify(SIGTRAP | ((current->ptrace & PT_TRACESYSGOOD) -- 1.7.4.1 -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html _______________________________________________ arm mailing list arm(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F

1 0

[opensuse-arm] Ideas to improve ARM in openSUSE
by Guillaume Gardet 04 May '12

04 May '12

Hi, Just some ideas. It would be nice to: * Have some non-JeOS images : Desktop with Xfce, LXDE, E17, JWM or IceWM or something else which is light) (and server in text mode?) * Improve kernel configs and maybe have a system to follow and update ARM configs (common/specific options) (a (wiki) table, a spreadsheet, or something else which is easily editable and easy to use). Maybe some tools already exist? * Have some pages on the wiki which tell users how to use openSUSE images for their ARM board. * Have some pages on the wiki which tell users (and developpers) what is the support level of a given board (USB OK, Ethernet KO, etc.). I started some wiki things on my user page: http://en.opensuse.org/User:Guillaume_G Feel free to edit it if needed. I will move it to real wiki pages once there are enough infos. Is there a preferred wiki structure or namespace? Or only use Category:ARM and links from Portal:ARM are enough? It would be interesting to know who use which board to have a good start for supported hardware. Maybe add support for raspberry Pi could be interesting even if it is an ARMv6. What must be done to add armv5 kernel configs and maybe kiwi image? If you have more ideas, please share! Cheers, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 7

[opensuse-arm] no gcc acceleration atm
by Adrian Schröter 03 May '12

03 May '12

JFYI, I removed the gcc binaries from qemu-accel-arm package again, because current binaries have wrong compiled in include paths. That leaded to compilation errors. So, we have no accelerated build until we have fixed gcc packages. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- 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] Fwd: [opensuse-kernel] master armv7l configs
by Guillaume Gardet 30 Apr '12

30 Apr '12

Here is a mail received on -kernel list about ARM configs. Guillaume -------- Message original -------- Sujet: [opensuse-kernel] master armv7l configs Date : Fri, 27 Apr 2012 10:32:23 -0400 De : Jeff Mahoney <jeffm(a)suse.de> Pour : openSUSE Kernel <opensuse-kernel(a)opensuse.org> Copie à : Andrew Wafaa <awafaa(a)opensuse.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all - When I merged 3.4-rc1, I disabled ARM builds. I'd like to re-enable them now, but have no idea what the ARM guys want for config options. Can someone go through and sync the configs up and send a patch/pull request for the new configs that also enable armv7l in config.conf? Thanks. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPmq33AAoJEB57S2MheeWy2poP/2TF3CWppk2dvZdN9Sahoceu D2Z6I2FTUzyAHpMcl/vEkKRoE9PyOwqRJT+bS1UX2uHqGrO4Sf3RP8RyAmflpTws zAs5ESdCho0u6bwUxEmx5erMAfvFwIH5IFXhmPpuWDymym9xxMxzrK24+toUwCAt u8e6sLETqW5jqD7kStA1xTRu5/jrB6Nu8/AkAZDG9GEm8gr2lEg0cfUMUOPbmk2l 42c1QjwHLlJNhSAXAgHpxFwjht4JuviJEraDpSFJlnk4yozMiI3cTkAeuY/iBRmu 9j5e4M6FHuWCjUOoZ6M2nBBmEz/FMSdtRmgg7vfYTOgkNc1Bire4M2SIcnlXihES jNs/i/AgD37fFGUyGsUrQ7pp35lMi1xTQr4dfzYiYn5vWEHFD1Dv0hP9SNQjrQrm 0JreL5GZdxE3tcnOP95Tt/jMxgITOZe4EqB/rci7HbU5o4Z+oxkFlYRb+v+FSD63 MksZUS5WzCBsIXz2sgUyj1+9TP75ujBgT359KFCzOyXiMZD2416+kS7as9adG4AU axxTavEUDETE5fiKPsBuX8cp5Ctyw3dAKF5hCC/OVjcBGY4qNnt5DTZYR42moh+9 a8vG/DVO4UiOrJh6F7AwBSH7PWwwNNVjsZaToKakThbCqwX3XDcVxCjsLiIQqbgF YhL/Zn7sN9dUvy2ku45b =PrwQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 9

[opensuse-arm] Interview of the ARM team
by Kim Leyendecker 29 Apr '12

29 Apr '12

Howdy y'all, maybe you know about "People of openSUSE", a series of the news team to introduce openSUSE people to our users and news-readers. As ARM is one of the buzz words in the IT world this year, it might be interesting to hear something about our ARM team and what your doing in general. I planned to to a People of openSUSE special, and if you're interested, I'd be very glad to send you some questions to answer. kind regards, -- Kim Leyendecker, openSUSE Wiki Team GPG Key: 664265369547B825 | leyendecker(a)opensuse.org http://www.opensuse.org - Linux for open minds -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 7

[opensuse-arm] dovercot12 and ARM
by Joop Boonen 29 Apr '12

29 Apr '12

Hi all, I see that davocot12 fails to build for arm. The newer version of dovecot dovecot20 builds without a problem. I wonder if I also can use "ExcludeArch: %arm" for dovecot12, as a newer working alternative exists. Regards, Joop. -- 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] gcc < 4.6 build for ARM
by Joop Boonen 27 Apr '12

27 Apr '12

Hi all, I wonder if it wouldn't be better to disable building all gcc compilers < 4.6 for ARM. I see that they fail to build and they use build capacity. I don't think these compilers won't be fixed for ARM anyway? I don't think that they will be used? Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 3

[opensuse-arm] v8 for openSUSE:Factory:ARM fails while the openSUSE:Factory version is OK
by Joop Boonen 26 Apr '12

26 Apr '12

Hi all, I've just checked out why v8 fails for ARM. If fails with the following rpmlint error: <quote> RPMLINT report: =============== (none): E: badness 10000 exceeds threshold 1000, aborting. libv8-3.armv7l: E: shlib-policy-name-error (Badness: 10000) libv8preparser3 Your package contains a single shared library but is not named after its SONAME. </quote> For the x86 factory build it doesn't, the packages are created without a problem. Might it mean that the rpmlint for ARM is different for ARM? Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

[opensuse-arm] ARM Build failure
by Guillaume Gardet 24 Apr '12

24 Apr '12

Hi, Builds from my home project fail. With a simple build (gcc devmem2.c -o devmem2), I get the following error: |gcc: error trying to exec 'cc1': execvp: No such file or directory| Maybe due to errors while gcc 4.7 switch? Or incomplete rebuild? Regards, 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] Fwd: [Android-virt] [ANNOUNCE] [OFFTOPIC] Xvisor ARM with and/or without virtualization extensions
by Alexander Graf 24 Apr '12

24 Apr '12

That sounds like a great way to use real ARM boards for OBS. Does anyone feel like giving it a try? :) Alex Begin forwarded message: > From: Anup Patel <anup(a)brainfault.org> > Subject: [Android-virt] [ANNOUNCE] [OFFTOPIC] Xvisor ARM with and/or without virtualization extensions > Date: 24. April 2012 15:36:34 MESZ > To: linux-arm-kernel(a)lists.infradead.org, linux-kernel(a)vger.kernel.org, android-virt(a)lists.cs.columbia.edu, beagleboard(a)googlegroups.com, xen-arm(a)lists.xensource.com > > Xvisor (eXtensible Versatile hypervISOR) is an open source bare-metal > monolithic hypervisor, which aims towards providing virtualization solution, > which is light-weight, portable, and flexible with small memory foot print > and less overhead. It is distributed under GNU Public License (GPLv2). > > Xvisor has most of the features expected from a modern full-fledged hypervisor, > such as: > - Tree based configuration > - Tickless and high resolution timekeeping > - Wall-clock for tracking real-time > - Threading framework > - Host device driver framework > - CPU virtualization > - Address space virtualization > - IO device emulation framework > - Pass through hardware access > - Dynamic guest creation/destruction > - Serial port virtualization > - Management terminal > > The ARM port of Xvisor (or Xvisor ARM) supports a wide range of ARM processors > namely: > - ARM9 (Boards: VersatilePB) > - Cortex-A8 (Boards: Realview-PB-A8) > - OMAP3 (Boards: BeagleBoard-xM) > - Cortex-A9 (UP) (Boards: Vexpress-A9) > - Cortex-A15 (UP) Without VE (Boards: Vexpress-A15) > - Cortex-A15 (UP) With VE (Boards: Vexpress-A15) > > For all supported ARM processors Xvisor ARM is able to boot multiple unmodified > Linux-3.0.4 guest with a fairly interactive and smooth Busybox 0.19.2 console. > > On real hardware specifically BeagleBoard-xM (OMAP3 @ 600 MHz) we get near > native CPU performance (i.e. Native Linux 3.0.4 gives 1120 DMIPS whereas Linux > 3.0.4 running as guest on Xvisor ARM gives 960 DMIPS) > > Please try out our Xivsor Cortex-A15 demo on ARM Fast Models 7.0 and/or > Linaro QEMU (2.02 or higher). To download the demo tarball visit: > https://docs.google.com/open?id=0B0ABS_s60oP_WjNQQ0QtUzNmdmc > > Xvisor is currently hosted on Github, to clone or download source code please > visit following links: > Wiki: https://github.com/xvisor/xvisor/wiki > Mainline Repository: https://github.com/xvisor/xvisor > Stagging Repository: https://github.com/avpatel/xvisor-next > > Our developer mailing list is xvisor-devel[at]googlegroups[ > dot]com, please feel free to post your queries or join our development > mailing list. > > _______________________________________________ > Android-virt mailing list > Android-virt(a)lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/android-virt -- 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] WLAN support for Pandaboard (ES)
by endym 22 Apr '12

22 Apr '12

After booting my Pandaboard ES (image "LimeJeOS-openSUSE-Factory-ARM-panda.armv7l-1.12.1-Build10.1.raw") there is no wlan0 device. Regarding to the information here <http://elinux.org/Panda_How_to_kernel_3_2_rcx> there should be a wl12xx driver, but "modprobe -l" does not list such a driver. Is this a known issue? Regards endym -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 3

[opensuse-arm] YaST Network Settings error
by endym 22 Apr '12

22 Apr '12

Hello, I use the image "LimeJeOS-openSUSE-Factory-ARM-panda.armv7l-1.12.1-Build10.1.raw" on my Pandaboard ES. To configure the WLAN I have installed YaST with "zypper in patterns-openSUSE-yast2_basis". Starting the YaST Network Settings with "yast2 lan" results in the error message "Error while creating client module lan". I don't think, that this is an arm issue, however maybe someone has an idea? I have done a google search, but didn't found a solution. Regards, endym -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

[opensuse-arm] ARM gcc47 build issue
by Joop Boonen 22 Apr '12

22 Apr '12

Hi all, An ARM build issue exists. I see: /emul/x86_64-for-arm/lib64:/emul/x86_64-for-arm/usr/lib64 Is still gcc 4.6.3. Form the config.log of for instance binutils I see it tries to compile against gcc4.6.3 <quote> Thread model: posix gcc version 4.6.3 (SUSE Linux) configure:4018: $? = 0 configure:4007: gcc -V >&5 gcc: error: unrecognized option '-V' gcc: fatal error: no input files compilation terminated. </quote> instead of 4.7. Which is installed correctly in: drwxr-xr-x 3 root root 4.0K Apr 20 18:30 armv7l-suse-linux-gnueabi lrwxrwxrwx 1 root root 7 Apr 21 11:10 ./build-root/usr/bin/gcc -> gcc-4.7 lrwxrwxrwx 1 root root 10 Apr 21 11:08 ./build-root/usr/lib64/gcc -> ../lib/gcc These are gcc 4.6.3 binaries. lrwxrwxrwx 1 root root 12 Apr 21 11:08 ./build-root/emul/x86_64-for-arm/usr/lib/gcc -> ../lib64/gcc -rwxr-xr-x 1 root root 322K Apr 20 10:29 ./build-root/emul/x86_64-for-arm/usr/bin/gcc >From package: qemu-accel-arm ( qemu-accel-arm-0.2-8.5.x86_64.rpm ) Package: openSUSE:Factory:ARM qemu-accel cant be rebuild due to: openSUSE:Factory:ARM cross-armv7l-binutils for x86_64 ( qemu_accel ) Will enabling this build resolve this issue? I don't see a spec file for: cross-armv7l-binutils only cross-arm-binutils I've just build this package locally without a problem: osc build --alternative-project=openSUSE:Factory:ARM qemu_accel x86_64 cross-arm-binutils.spec Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 4

Re: [opensuse-arm] ARM gcc47 build issue
by Joop Boonen 21 Apr '12

21 Apr '12

On Sat, April 21, 2012 3:45 pm, Adrian Schröter wrote: > Am Samstag, 21. April 2012, 11:45:00 schrieb Joop Boonen: >> Hi all, >> >> An ARM build issue exists. >> >> I see: >> /emul/x86_64-for-arm/lib64:/emul/x86_64-for-arm/usr/lib64 >> >> Is still gcc 4.6.3. > > I tried to fix it by enabling the build of cross-armv7l-binutils for x86_64 again > , which is the reason why qemu-accel is in unresolvable and can't be build. I saw that this indeed the problem. I copied over cp -p /var/tmp/build-root/usr/bin/gcc-4.7 /var/tmp/build-root/emul/x86_64-for-arm/usr/bin/gcc After this the build was OK. And I saw the correct gcc version 4.7 . <quote> + ls -al /usr/bin/gcc lrwxrwxrwx 1 root root 7 Apr 21 09:58 /usr/bin/gcc -> gcc-4.7 + ls -alH /usr/bin/gcc -rwxr-xr-x 1 root root 396888 Apr 20 16:36 /usr/bin/gcc + ls -al /usr/bin/gcc-4.7 -rwxr-xr-x 1 root root 396888 Apr 20 16:36 /usr/bin/gcc-4.7 + /usr/bin/gcc -v Using built-in specs. COLLECT_GCC=/usr/bin/gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/armv7l-suse-linux-gnueabi/4.7/lto-wrapper Target: armv7l-suse-linux-gnueabi Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib --enable-languages=c,c++,objc,fortran,obj-c++,java --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.7 --enable-ssp --disable-libssp --disable-libitm --disable-plugin --with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --disable-libgcj --disable-libmudflap --with-slibdir=/lib --with-system-zlib --enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-version-specific-runtime-libs --enable-linker-build-id --program-suffix=-4.7 --enable-linux-futex --without-system-libunwind --with-arch=armv7-a --with-tune=cortex-a9 --with-float=hard --with-mode=thumb --with-abi=aapcs-linux --with-fpu=vfpv3-d16 --disable-sjlj-exceptions --build=armv7l-suse-linux-gnueabi Thread model: posix gcc version 4.7.0 20120413 [gcc-4_7-branch revision 186417] (SUSE Linux) + /usr/bin/gcc-4.7 -v Using built-in specs. COLLECT_GCC=/usr/bin/gcc-4.7 COLLECT_LTO_WRAPPER=/usr/lib/gcc/armv7l-suse-linux-gnueabi/4.7/lto-wrapper Target: armv7l-suse-linux-gnueabi Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib --enable-languages=c,c++,objc,fortran,obj-c++,java --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.7 --enable-ssp --disable-libssp --disable-libitm --disable-plugin --with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --disable-libgcj --disable-libmudflap --with-slibdir=/lib --with-system-zlib --enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-version-specific-runtime-libs --enable-linker-build-id --program-suffix=-4.7 --enable-linux-futex --without-system-libunwind --with-arch=armv7-a --with-tune=cortex-a9 --with-float=hard --with-mode=thumb --with-abi=aapcs-linux --with-fpu=vfpv3-d16 --disable-sjlj-exceptions --build=armv7l-suse-linux-gnueabi Thread model: posix gcc version 4.7.0 20120413 [gcc-4_7-branch revision 186417] (SUSE Linux) </quote> The package isn't build as cross-armv7l-binutils.changes cross-armv7l-binutils.spec and cross-armv5tel-binutils.changes cross-armv5tel-binutils.spec are missing. I've created them in home:worldcitizen:branches:openSUSE:Factory:ARM cross-armv7l-binutils . Maybe these ( cross-armv5tel-binutils.changes cross-armv5tel-binutils.spec cross-armv7l-binutils.changes cross-armv7l-binutils.spec ) can be copied over and committed in openSUSE:Factory:ARM ? I don't know what the standard is. Should both spec files reside in this project/package (binutils)? > > I will have a look later again (but I forgot the power supply for my notebook at home, > so it might not happen before monday or sunday evening). > > sorry > adrian > > -- > Adrian Schroeter > SUSE Linux Products GmbH > email: adrian(a)suse.de > > -- 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] Re: [opensuse-factory] GCC 4.7
by Joop Boonen 20 Apr '12

20 Apr '12

On Fri, April 20, 2012 1:28 pm, Dominique Leuenberger a.k.a DimStar wrote: > > Hi everybody, > > Just a heads-up this time: This morning, GCC 4.7 was switched to be > the default compiler in Factory. > AS far as we're concerned, most packages should be fixed by now (at > least in their devel projects). So if you see package failures due to > this, please make sure to sync your devel projects up. > > There is a small amount of packages that is still failing, and there > is a possibility that we (the informal team of hackers fixing GCC 4.7 > fallouts) missed some packages. > > If so, please feel free to > > a) Check with upstreams for a fix... most maintained things are fixed > by now (Fedora to the thanks here) > b) Fix the package (most of the time it's missing includes and the like > c) ping us here and/or IRC for assistance. As with all other packages, > we'll try to help to resolve the build failures. > > Looking forward to a full build of Factory! I assume and hope that openSUSE:Factory:ARM and is also using gcc47 as the default compiler. > > Dominique Regards, Joop. -- 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] New glibc in Base:System with changed dynamic linker
by Andreas Jaeger 18 Apr '12

18 Apr '12

HI, I'm submitting now a new glibc to Base:System that has the new changed dynamic linker - but still works with binaries using the old one. I'll push this to Factory soonish and wanted to give you 24hours advanced warning. For me everything looked fine, I build using qemu... Richard, could you include in your next gcc47 submission the patch from http://sourceware.org/ml/libc-ports/2012-04/msg00060.html thanks, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 3

[opensuse-arm] Building with kvm broken?
by Andreas Jaeger 18 Apr '12

18 Apr '12

I tried building with osc --vm-type=kvm \ --alternative-project=openSUSE:Factory:ARM standard armv7l glibc.spec and this failed with: mount -o rw,acl,user_xattr -t ext4 /dev/sda /root replacing /etc/mtab with symlink to /proc/self/mounts mount: binfmt_misc, /proc/sys/fs/binfmt_misc: No such device /proc/sys/fs/binfmt_misc/register: write: fails test [ 4.352745] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 [ 4.352747] [ 4.354297] Rebooting in 1 seconds..No buildstatus set, either the packager broke the base system (glibc/bash/perl) or the build host has a kernel or hardware problem, OBS server will retry... The buildroot was: /abuild/osc/buildroot_standard-armv7l/.mount I'm using the packages from openSUSE:Tools:Unstable. Any ideas what's wrong? Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 5

[opensuse-arm] Bad kernel-omap2plus package ?
by Guillaume Gardet 17 Apr '12

17 Apr '12

Hi, I installed the latest raw image for BeagleBoard xM and then "zypper refresh && zypper up" and I get a lot of warnings (check attachment). Especially for kernel installation: ******************************************************************************** Installing: kernel-omap2plus-3.3.0-1.1 [done] Additional rpm output: WARNING: /etc/depmod.d/00-system.conf line 1: ignoring bad line starting with '4683/tcp' WARNING: /etc/depmod.d/00-system.conf line 2: ignoring bad line starting with 'spike' WARNING: /etc/depmod.d/00-system.conf line 4: ignoring bad line starting with 'rfid-rp1' WARNING: /etc/depmod.d/00-system.conf line 5: ignoring bad line starting with 'rfid-rp1' WARNING: /etc/depmod.d/00-system.conf line 7: ignoring bad line starting with 'autopac' WARNING: /etc/depmod.d/00-system.conf line 8: ignoring bad line starting with 'autopac' WARNING: kernel image for 3.3.0-1-omap2plus not found! ******************************************************************************** And a ls /boot show this: ******************************************************************************** -rw-r--r-- 1 root root 1,3K 20 mars 11:52 boot.readme -rw-r--r-- 1 root root 697 1 janv. 2000 boot.scr -rw-r--r-- 1 root root 625 1 janv. 2000 boot.script -rw-r--r-- 1 root root 81K 22 mars 12:50 config-3.3.0-1-omap2plus drwxr-xr-x 2 root root 1,0K 1 janv. 2000 grub lrwxrwxrwx 1 root root 24 23 févr. 02:11 initrd -> initrd-3.3.0-1-omap2plus -rw-r--r-- 1 root root 22M 13 mars 14:50 initrd.uboot -rw-r--r-- 1 root root 3,9M 13 mars 14:50 linux.vmx drwx------ 2 root root 12K 13 mars 14:50 lost+found -rwxr-xr-x 1 root root 29K 1 mars 00:37 MLO -rw-r--r-- 1 root root 73K 22 mars 13:43 symvers-3.3.0-1-omap2plus.gz -rw-r--r-- 1 root root 234 22 mars 13:43 sysctl.conf-3.3.0-1-omap2plus -rw-r--r-- 1 root root 1,9M 22 mars 13:32 System.map-3.3.0-1-omap2plus -rw-r--r-- 1 root root 331K 1 mars 11:27 u-boot.bin lrwxrwxrwx 1 root root 24 23 févr. 02:11 uImage -> uImage-3.3.0-1-omap2plus -rw-r--r-- 1 root root 4,0M 22 mars 13:43 uImage-3.3.0-1-omap2plus -rw-r--r-- 1 root root 4,9M 22 mars 13:37 vmlinux-3.3.0-1-omap2plus.gz ******************************************************************************** So, no initrd (except a broken link and the initrd.u-boot). Moreover, when I try to boot, u-boot is still looking for uImage-3.2.0-2-omap2plus which is no more here. (same for initrd). So I think something is broken somewhere! Guillaume

3 9

[opensuse-arm] Rebuild trigger request for openSUSE:Factory:ARM gdk-pixbuf
by Joop Boonen 17 Apr '12

17 Apr '12

Hi all, Can the package openSUSE:Factory:ARM gdk-pixbuf please be rebuild, as this package isn't up to date any more. package libtiff-devel where this package depends on has been rebuild. Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

[opensuse-arm] Fwd: ARM hard-float linker path - consensus
by Andreas Jaeger 16 Apr '12

16 Apr '12

FYI, Adrian asked me to participate in the call and here's the result. Once we have a glibc patch, let's fix both gcc and glibc - and add a compatibility symlink for now until rebuilding of the whole distro succeeded... Andreas -------- Original Message -------- Subject: ARM hard-float linker path - consensus Date: Fri, 13 Apr 2012 18:37:11 +0100 From: Steve McIntyre <steve.mcintyre(a)linaro.org> To: cross-distro(a)lists.linaro.org CC: gcc-patches(a)gcc.gnu.org, libc-ports(a)sourceware.org Hi folks, As promised, here's minutes from the call we had this afternoon. Spoiler: the result we've agreed is /lib/ld-linux-armhf.so.3 And here's a transcription of the minutes from https://wiki.linaro.org/OfficeofCTO/HardFloat/LinkerPathCallApr2012 ======================================== Meeting: 13th April 2012, 15:00 UTC Agenda ------ * Debian/Ubuntu have so far built using /lib/arm-linux-gnueabihf/ld-linux.so.3 * Some other distros (Fedora, OpenSUSE) are still using /lib/ld-linux.so.3 option which matches the older soft-float ABI * Some people are proposing /libhf/ld-linux.so.3 or /libhfp/ld-linux.so.3 (multilib) * Some people proposed /lib/ld-arm-linux-gnueabihf.so.3 (similar to x86_64, libs still in /lib, from Michael Hope) * What should we do as a community? Present ------- Name Affiliations Steve McIntyre ARM, Debian, Linaro Wookey ARM, Debian, Linaro Richard Earnshaw ARM, gcc Jeff Law Fedora, Red Hat, gcc, glibc Jon Masters Fedora, Red Hat Andrew Haley Fedora, Red Hat, gcc Andreas Jaeger SUSE, openSUSE, glibc Carlos O'Donnell Mentor, gcc Steve Langasek Canonical, Ubuntu, Debian Dann Frazier Canonical, Ubuntu, Debian Adam Conrad Canonical, Ubuntu, Debian Matthias Klose Canonical, Ubuntu, Debian Mike Frysinger Gentoo Dennis Gilmore Fedora, Red Hat Discussion ---------- We started with a couple of questions up front to establish the grounds for discussion: * We believed that decision makers were present for all the important parties, i.e. all the arm hard-float distros, plus toolchain developers. This meant that a decision taken at the meeting could be implemented without needing further arguments/negotiations. * All the people present understood the importance of cross-distro binary compatibility, and they all wanted it. This led to agreement that we needed to agree on a standard path for the runtime linker for ARM hard-float Linux binaries. Debian and Ubuntu had so far been using the "multi-arch" path of /lib/arm-linux-gnueabihf/ld-linux.so.3. Fedora and OpenSUSE were thus far using /lib/ld-linux.so.3, the same as the soft-float ABI. Others had proposed alternative paths such as /libhf/ld-linux.so.3 or /libhfp/ld-linux.so.3 (multilib) or /lib/ld-arm-linux-gnueabihf.so.3. Discussion showed that none of these were found to be universally acceptable. Two parties were likely to be soon affected by an agreement here: 1. Ubuntu 12.04 (releasing with armhf in ~2 weeks) Adam/Steve L agreed that all efforts would be put in to switch the compilers in Ubuntu to a new path before release. Default things like gcc would be correct, but less common tools might still be targetting the old path /lib/arm-linux-gnueabihf/ld-linux.so. at release. They could be fixed in the longer term and would not stop progress here. 2. Mentor (Codebench due for release in ~1 week) Carlos mentioned this - Codebench has been using /lib/ld-linux.so.3 for hard-float binaries for some time and it was too late to change that for this upcoming release. Next release due in October. Suggested and accepted that this should be mentioned in release notes: if people want to use Codebench on some systems (Debian/Ubuntu and derivatives), they'll need to tweak their system setup. He may be able to do the linker change and rebuild in a point release in a few weeks. It was briefly suggested that the soft-float linker should be renamed away from /lib/ld-linux.so.3 as well at this time, but that idea was quickly shot down. Proposal #1: /lib/ld-armhf.so.3 (not generally liked) Proposal #2: /lib/ld-linux-armhf.so.3 (not favourite, but considered an acceptable compromise by all) No need to go any further. Conclusion ---------- All the people in the meeting agreed: the new runtime linker path for ARM hard-float Linux binaries was to be /lib/ld-linux-armhf.so.3 ACTION: People at the meeting to present this decision to their companies / communities and get the appropriate changes made. Further discussion ------------------ General unhappiness with the mess that led to this meeting. Future planning needs to be better between the various groups for the next time we have a new CPU/ABI/whatever. ACTION: Jon Masters to talk to the Linux Foundation about setting up a forum for such discussions. In the meantime, strong consensus to use the cross-distro(a)lists.linaro.org mailing list for any more conversations now we have people in contact. ACTION: Steve McIntyre to write up the minutes and circulate. Include an updated linker path patch for gcc to match the decision made here. More discussion about triplets and naming, but nothing came of it in the end. Distro folks have already decided what they're using and have patched various software to build appropriately. Richard wants to move gcc's config.guess to use arm-linux-gnueabihf; no strong objections to that. Linker path patch for gcc ------------------------- Adapted from earlier work by Dann Frazier <dann.frazier(a)canonical.com> and Michael Hope <michael.hope(a)linaro.org> 2012-04-13 Steve McIntyre <steve.mcintyre(a)linaro.org> * config/arm/linux-eabi.h (GLIBC_DYNAMIC_LINKER_HARD_FLOAT): Define. (GLIBC_DYNAMIC_LINKER): Redefine to use the hard float path. diff --git a/gcc/config/arm/linux-eabi.h b/gcc/config/arm/linux-eabi.h index 80bd825..8c9d2e7 100644 --- a/gcc/config/arm/linux-eabi.h +++ b/gcc/config/arm/linux-eabi.h @@ -62,7 +62,11 @@ /* Use ld-linux.so.3 so that it will be possible to run "classic" GNU/Linux binaries on an EABI system. */ #undef GLIBC_DYNAMIC_LINKER -#define GLIBC_DYNAMIC_LINKER "/lib/ld-linux.so.3" +#define GLIBC_DYNAMIC_LINKER_SOFT_FLOAT "/lib/ld-linux.so.3" +#define GLIBC_DYNAMIC_LINKER_HARD_FLOAT "/lib/ld-linux-armhf.so.3" +#define GLIBC_DYNAMIC_LINKER \ + "%{mfloat-abi=hard:" GLIBC_DYNAMIC_LINKER_HARD_FLOAT "} \ + %{!mfloat-abi=hard:" GLIBC_DYNAMIC_LINKER_SOFT_FLOAT "}" /* At this point, bpabi.h will have clobbered LINK_SPEC. We want to use the GNU/Linux version, not the generic BPABI version. */ Post-meeting on IRC ------------------- Suggested that Richard should push the change into gcc trunk ASAP. Steve McIntyre agreed to work on that with Richard. Also suggested that we want to get a patch into glibc too to change the installation path for ARM hard-float. Andrew agreed to push glibc upstream for that. Cheers, -- Steve McIntyre steve.mcintyre(a)linaro.org <http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs _______________________________________________ cross-distro mailing list cross-distro(a)lists.linaro.org http://lists.linaro.org/mailman/listinfo/cross-distro -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- 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] Beaglebaord xM - USB is broken
by Guillaume Gardet 16 Apr '12

16 Apr '12

Hi, I tried the latest beagle raw image (10.7) and USB is broken (so no Ethernet which is connected on USB internally, no USB stick). USB errors I get: (output of "dmesg | grep -i usb") ******************************************************************************** [ 0.092529] usbhs_omap: alias fck already exists [ 0.107055] usbcore: registered new interface driver usbfs [ 0.107177] usbcore: registered new interface driver hub [ 0.107391] usbcore: registered new device driver usb [ 0.171813] usbhs_omap usbhs_omap: xclk60mhsp1_ck set parentfailed error:-22 [ 0.171813] usbhs_omap usbhs_omap: xclk60mhsp2_ck set parentfailed error:-22 [ 1.666625] usbcore: registered new interface driver asix [ 1.672393] usbcore: registered new interface driver cdc_ether [ 1.678619] usbcore: registered new interface driver smsc95xx [ 1.684722] usbcore: registered new interface driver net1080 [ 1.690734] usbcore: registered new interface driver cdc_subset [ 1.697021] usbcore: registered new interface driver zaurus [ 1.702972] usbcore: registered new interface driver cdc_ncm [ 1.709228] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.716278] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 1.729431] drivers/usb/core/inode.c: creating file 'devices' [ 1.729461] drivers/usb/core/inode.c: creating file '001' [ 1.729766] ohci-omap3 ohci-omap3.0: new USB bus registered, assigned bus number 1 [ 1.821533] usb usb1: default language 0x0409 [ 1.821594] usb usb1: udev 1, busnum 1, minor = 0 [ 1.821594] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.828765] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.836334] usb usb1: Product: OMAP3 OHCI Host Controller [ 1.841979] usb usb1: Manufacturer: Linux 3.3.0-omap2plus+ ohci_hcd [ 1.848571] usb usb1: SerialNumber: ohci-omap3.0 [ 1.853973] usb usb1: usb_probe_device [ 1.854003] usb usb1: configuration #1 chosen from 1 choice [ 1.854034] usb usb1: adding 1-0:1.0 (config #1, interface 0) [ 1.854217] hub 1-0:1.0: usb_probe_interface [ 1.854217] hub 1-0:1.0: usb_probe_interface - got id [ 1.854248] hub 1-0:1.0: USB hub found [ 1.862457] hub 1-0:1.0: no power switching (usb 1.0) [ 1.862945] drivers/usb/core/inode.c: creating file '001' [ 1.863220] usbcore: registered new interface driver cdc_wdm [ 1.869201] Initializing USB Mass Storage driver... [ 1.874481] usbcore: registered new interface driver usb-storage [ 1.880767] USB Mass Storage support registered. [ 1.885742] usbcore: registered new interface driver libusual [ 1.891876] usbcore: registered new interface driver usbtest [ 2.173339] usbcore: registered new interface driver usbhid [ 2.179229] usbhid: USB HID core driver ******************************************************************************** Previous USB related dmesg (beagle raw image 10.6): ******************************************************************************** [ 0.074829] usbcore: registered new interface driver usbfs [ 0.074981] usbcore: registered new interface driver hub [ 0.075195] usbcore: registered new device driver usb [ 3.407592] usbcore: registered new interface driver asix [ 3.413391] usbcore: registered new interface driver cdc_ether [ 3.419616] usbcore: registered new interface driver smsc95xx [ 3.425720] usbcore: registered new interface driver net1080 [ 3.431701] usbcore: registered new interface driver cdc_subset [ 3.437988] usbcore: registered new interface driver zaurus [ 3.447296] usbcore: registered new interface driver cdc_ncm [ 3.453613] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 5.478576] /home/abuild/rpmbuild/BUILD/kernel-omap2plus-3.2.0/linux-3.2/drivers/usb/core/inode.c: creating file 'devices' [ 5.478607] /home/abuild/rpmbuild/BUILD/kernel-omap2plus-3.2.0/linux-3.2/drivers/usb/core/inode.c: creating file '001' [ 5.479034] ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1 [ 5.503753] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00 [ 5.509948] usb usb1: default language 0x0409 [ 5.510009] usb usb1: udev 1, busnum 1, minor = 0 [ 5.510009] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 5.517150] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 5.524749] usb usb1: Product: OMAP-EHCI Host Controller [ 5.530334] usb usb1: Manufacturer: Linux 3.2.0-2-omap2plus ehci_hcd [ 5.536987] usb usb1: SerialNumber: ehci-omap.0 [ 5.542297] usb usb1: usb_probe_device [ 5.542297] usb usb1: configuration #1 chosen from 1 choice [ 5.542358] usb usb1: adding 1-0:1.0 (config #1, interface 0) [ 5.542541] hub 1-0:1.0: usb_probe_interface [ 5.542572] hub 1-0:1.0: usb_probe_interface - got id [ 5.542572] hub 1-0:1.0: USB hub found [ 5.551300] /home/abuild/rpmbuild/BUILD/kernel-omap2plus-3.2.0/linux-3.2/drivers/usb/core/inode.c: creating file '001' [ 5.581848] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 5.594787] /home/abuild/rpmbuild/BUILD/kernel-omap2plus-3.2.0/linux-3.2/drivers/usb/core/inode.c: creating file '002' [ 5.595123] ohci-omap3 ohci-omap3.0: new USB bus registered, assigned bus number 2 [ 5.685668] usb usb2: default language 0x0409 [ 5.685699] usb usb2: udev 1, busnum 2, minor = 128 [ 5.685729] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [ 5.692871] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 5.700439] usb usb2: Product: OMAP3 OHCI Host Controller [ 5.706115] usb usb2: Manufacturer: Linux 3.2.0-2-omap2plus ohci_hcd [ 5.712799] usb usb2: SerialNumber: ohci-omap3.0 [ 5.718170] usb usb2: usb_probe_device [ 5.718170] usb usb2: configuration #1 chosen from 1 choice [ 5.718231] usb usb2: adding 2-0:1.0 (config #1, interface 0) [ 5.718414] hub 2-0:1.0: usb_probe_interface [ 5.718414] hub 2-0:1.0: usb_probe_interface - got id [ 5.718444] hub 2-0:1.0: USB hub found [ 5.726654] hub 2-0:1.0: no power switching (usb 1.0) [ 5.727142] /home/abuild/rpmbuild/BUILD/kernel-omap2plus-3.2.0/linux-3.2/drivers/usb/core/inode.c: creating file '001' [ 5.727478] usbcore: registered new interface driver cdc_wdm [ 5.733459] Initializing USB Mass Storage driver... [ 5.738739] usbcore: registered new interface driver usb-storage [ 5.745056] USB Mass Storage support registered. [ 5.750030] usbcore: registered new interface driver libusual [ 5.756195] usbcore: registered new interface driver usbtest [ 5.902160] usb 1-2: new high-speed USB device number 2 using ehci-omap [ 6.061004] usbcore: registered new interface driver usbhid [ 6.066894] usbhid: USB HID core driver [ 6.142974] usb 1-2: udev 2, busnum 1, minor = 1 [ 6.143035] usb 1-2: New USB device found, idVendor=0424, idProduct=9514 [ 6.150115] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 6.158172] usb 1-2: usb_probe_device [ 6.158203] usb 1-2: configuration #1 chosen from 1 choice [ 6.158477] usb 1-2: adding 1-2:1.0 (config #1, interface 0) [ 6.158691] hub 1-2:1.0: usb_probe_interface [ 6.158691] hub 1-2:1.0: usb_probe_interface - got id [ 6.158721] hub 1-2:1.0: USB hub found [ 6.189483] /home/abuild/rpmbuild/BUILD/kernel-omap2plus-3.2.0/linux-3.2/drivers/usb/core/inode.c: creating file '002' [ 6.386688] usb 1-2: link qh256-0001/c24aa4e0 start 1 [1/0 us] [ 6.472656] usb 1-2.1: new high-speed USB device number 3 using ehci-omap [ 6.598022] usb 1-2.1: udev 3, busnum 1, minor = 2 [ 6.598052] usb 1-2.1: New USB device found, idVendor=0424, idProduct=ec00 [ 6.605316] usb 1-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 6.628997] usb 1-2.1: usb_probe_device [ 6.629028] usb 1-2.1: configuration #1 chosen from 1 choice [ 6.631408] usb 1-2.1: adding 1-2.1:1.0 (config #1, interface 0) [ 6.631622] smsc95xx 1-2.1:1.0: usb_probe_interface [ 6.631652] smsc95xx 1-2.1:1.0: usb_probe_interface - got id [ 6.721282] smsc95xx 1-2.1:1.0: eth0: register 'smsc95xx' at usb-ehci-omap.0-2.1, smsc95xx USB 2.0 Ethernet, c2:7a:cd:e3:cb:21 [ 6.746002] /home/abuild/rpmbuild/BUILD/kernel-omap2plus-3.2.0/linux-3.2/drivers/usb/core/inode.c: creating file '003' [ 152.115692] usb 1-2.1: link qh8-0001/d96d52e0 start 2 [1/0 us] ******************************************************************************** It seems there is no EHCI detection. It may be due to bad clock? Do you have this problem on Beagleboard (original, not xM) and on pandaboard also or is it a BB xM only problem? Any idea to solve the problem? Cheers, 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] openSUSE on Pandaboard ES
by endym_linux＠ymail.com 16 Apr '12

16 Apr '12

Hello again! I run the image LimeJeOS-openSUSE-Factory-ARM-panda.armv7l-1.12.1-Build10.1.raw from <http://download.opensuse.org/repositories/openSUSE:/Factory:/ARM/images/> on the new Pandaboard ES. After zypper ref && zypper up the following error occures on boot: ************************************ USB EHCI 1.00 scanning bus for devices... The request port(2) is not configured The request port(2) is not configured 4 USB Device(s) found scanning bus for storage devices... 0 Storage Device(s) found scanning bus for ethernet devices... 1 Ethernet Device(s) found Waiting for Ethernet connection... done. BOOTP broadcast 1 *** Unhandled DHCP Option in OFFER/ACK: 28 *** Unhandled DHCP Option in OFFER/ACK: 42 *** Unhandled DHCP Option in OFFER/ACK: 28 *** Unhandled DHCP Option in OFFER/ACK: 42 DHCP client bound to address 192.168.1.116 missing environment variable: pxeuuid missing environment variable: ethaddr missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-2e-60-1a-38-4e-01 Waiting for Ethernet connection... done. Using sms0 device TFTP from server 192.168.1.1; our IP address is 192.168.1.116 Filename 'pxelinux.cfg/01-2e-60-1a-38-4e-01'. Load address: 0x86000000 Loading: EHCI timed out on TD - token=0x88008d80 T EHCI timed out on TD - token=0x8008d80 T EHCI timed out on TD - token=0x88008d80 T EHCI timed out on TD - token=0x88008d80 T EHCI timed out on TD - token=0x8008d80 T EHCI timed out on TD - token=0x88008d80 T EHCI timed out on TD - token=0x8008d80 T EHCI timed out on TD - token=0x88008d80 T EHCI timed out on TD - token=0x88008d80 T EHCI timed out on TD - token=0x8008d80 T EHCI timed out on TD - token=0x88008d80 Retry count exceeded; starting again Waiting for Ethernet connection... done. EHCI timed out on TD - token=0x88008d80 Using sms0 device TFTP from server 192.168.1.1; our IP address is 192.168.1.116 Filename 'pxelinux.cfg/01-2e-60-1a-38-4e-01'. Load address: 0x86000000 Loading: EHCI timed out on TD - token=0x88008d80 T EHCI timed out on TD - token=0x88008d80 T EHCI timed out on TD - token=0x8008d80 T EHCI timed out on TD - token=0x88008d80 T EHCI timed out on TD - token=0x8008d80 T EHCI timed out on TD - token=0x88008d80 T EHCI timed out on TD - token=0x88008d80 T EHCI timed out on TD - token=0x8008d80 T EHCI timed out on TD - token=0x88008d80 T EHCI timed out on TD - token=0x8008d80 T EHCI timed out on TD - token=0x88008d80 Retry count exceeded; starting again ... ************************************ The boot process is in an endless loop now. Is this a factory problem or is "zypper up" the wrong way? There is also a similar thread for the Beagleboard xM (http://lists.opensuse.org/opensuse-arm/2012-04/msg00006.html) Maybe it's the same issue... Regards, endym -- 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] Multimedia support for ARM (kernel configs)
by Guillaume Gardet 15 Apr '12

15 Apr '12

Hi, Is there any reason to not have enabled multimedia support on ARM (except on default config)? I think it would be nice to enable it (especially V4L support) for ARM boards. I know OMAP have capture and display drivers for V4L. I suppose others (IMX51, Tegra, ...) have similar things. Cheers, Guillaume -- 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] Re: [opensuse-buildservice] [PATCH] [build] Map Debian ARM arches to OBS
by Adrian Schröter 15 Apr '12

15 Apr '12

Am Mittwoch, 28. März 2012, 04:49:01 schrieb Adrian Schröter: > Am Dienstag, 27. März 2012, 22:43:35 schrieb Hector Oron: > > Hello Adrian, > > > > On 27/03/12 22:32, Adrian Schröter wrote: > > > Am Dienstag, 27. März 2012, 20:55:41 schrieb Hector Oron: > > >> Debian ARM arches: > > >> - Debian 'armel', which defaults to ARMv4t (soft) maps to armv[4567]l > > >> - Debian 'armhf', which defaults to ARMv7 (hard-float) maps to armv7hl > > >> > > >> Note Ubuntu 'armel' deprecated after 'precise' release, defaults to ARMv7 > > >> (softfp). So Ubuntu 'armel' should really map armv7l, but its out of scope > > >> for this patch. > > > > > > Hm, doesnt it make sense to map armv7l and armv7hl to armhf ? AFAIK there are no > > > arm cpus on v7 level without hardware fp. > > > > > > On the other hand this is about optimization level here and not hardware capabilities... > > > > As I understand armv7hl is hard-float ABI, hence 'armhf'. > > > > armv7l can be ARMv7/softfp as Ubuntu was doing on their ARM port > > (armel), hence makes sense to me to map armv7l to 'armel'. > > > > OTOH, Debian armel can run on any of those platforms, armv[4567]l, maybe > > armv[4567]el should be added to the list. In other words, if I am > > building armv7l debian packages I would expect them to use 'armel' > > dependencies, while if I am building armv7hl, I would expect to build > > against 'armhf' dependencies. > > > > As a side note, I also see 'armv8el', I think that one comes from MeeGo, > > and it should be deprecated and mapped in the future to aarch64 (64-bit > > ARM architecture). > > That one is pure fantasy and will have nothing in common with real upcomming armv8, I think. > > But also architectures like armv7hl or armhf are fantasy when it comes to the linux > kernel. They are just a hack in the packagemanagement to avoid to handle ABI compatibility > on dependency level. But it makes for example impossible to install static binaries armv7l > on armv7hl and vice versa. Even though it would run on real hardware. > > Or it would be thinkable to have also an entire set of packages with softfp on hardfp and vice > versa. For that reason I selected just "armv7l" for our hardfp optimized distribution. > But I agree that we seems to be special in the arm world with that way (so in worst case > we need to switch to armv7hl as well and need to make armv7l and armv7hl as equivalent to avoid > the describe problems) :/ > > In any case we have the problem now that we can not detect the ABI from the architecture now... > > We can take your patch now, but armhf will not be selected right in our default settings. > > I would be happy, if anyone has a better proposal here. Thinking again on the way to work about it, I think the following is the right approach: 1) Take your patch as is (done) ;) 2) Keep schedulers running on armv7l only, because we have just one pool of systems to build for. The same machines can handle armv7 softfp and hardfp (is this right?, I am no expert in arm hardware) For our openSUSE arm distro: 3) Define default _cpu_target as armv7hl, so we get also .armv7hl.rpm packages 4) Trim our rpm on arm to handle armv7l and armv7hl as equivalent. 5) extend library depend&provides handling with a "(hf)" extension to be able to distinguish between hardfp and softfp packages on the same installation. Note: The last point 5) would make our rpms incompatible with the ones from Fedora. But it is IMHO the only way to handle mixed installations and the fedora way is IMHO technical just wrong. I would be happy to hear some more opinions on this. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 2

[opensuse-arm] efika networking
by Peter Czanik 15 Apr '12

15 Apr '12

Hello, After yesterdays updates, networking does not work any more on the EFIKA. I still use the old Genesi kernel, as it arrived in the EFIKA image (2.6.31.14.26-efikamx) from http://lizards.opensuse.org/2012/01/21/opensuse-arm-image/ The non working wifi is definitely related to udev, there were related e-mails on the factory list also for x86, that firmware for Intel wifi can't be loaded either. But Ethernet on the smart top also does not work: it receives an initial IP address from the DHCP server, but after that there is no networking, even the DHCP server can't be reached again. Networking from Ubuntu works fine fine on the same machines. Any idea how to fix this? Bye, CzP -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

[opensuse-arm] Unable to login on Beagleboard xM with latest image
by Guillaume Gardet 15 Apr '12

15 Apr '12

I tried a zypper dup today but it broke my board (unable to boot since kernel file name in /boot did not match anymore and no initrd was present.) So, I wanted to boot the latest raw image but trying to log in with root/linux but I get this error: *************************************************************** linux login: root Password: Permissions on the password database may be too restrictive *************************************************************** I looked at the /etc/shadow file which seems strange to me: *************************************************************** Event # Greg Bailey <gbailey&lxpro.com> February 2002 biolink-auth 3411/tcp # BioLink Authenteon server biolink-auth 3411/udp # BioLink Authenteon server # BioLink Support <reginfo&biolinkusa.com> February 2002 xmlblaster 3412/tcp # xmlBlaster xmlblaste *************************************************************** Replaced by my /etc/shadow from my running PC and I am able to login (with the password from my PC of course). Could you please fix it ? Guillaume -- 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] Runtime linker path for ARM v7 hard-float
by Steve McIntyre 11 Apr '12

11 Apr '12

Hey guys, There's been a *lot* of discussion about this in the last few days on the cross-distro list (and elsewhere), but I've not noticed anybody from opensuse joining in. It's very important for sane cross-distro compatibility that we agree on the location of the runtime linker. We're trying to organise a conf call to get this sorted *now* before anybody releases a stable arm-hf distro. Who from the opensuse team would like to join in? If you can join us on irc, freenode #linaro-armhf to help schedule a call ASAP that would be lovely. Cheers, -- Steve McIntyre steve.mcintyre(a)linaro.org <http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

[opensuse-arm] omap2plus - Update config for 3.4-rc2 + misc improvements/fixes
by Guillaume Gardet 10 Apr '12

10 Apr '12

Hi, I sent a patch to opensuse-kernel: http://lists.opensuse.org/opensuse-kernel/2012-04/msg00027.html to update config for omap2plus for 3.4-rc2 and some improvements/fixes: * Add TWL4030 and TWL6030 USB support * Add Multimedia support * Disable egalax touchscreen to fix compilation error Is someone able to ack the patch, please? Regards, Guillaume -- 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] iMX51 - Update config for 3.4-rc2 + enable Multimedia support
by Guillaume Gardet 10 Apr '12

10 Apr '12

Please find in attachment a patch for the iMX51 config. I took the config from kernel-source/config/armv7l/imx51 and I added Multimedia support via menuconfig. It compiles (uImage + modules) but I haven't tested it since I have no iMX51 board. Regards, Guillaume

1 0

[opensuse-arm] DSP on OMAP3
by Guillaume Gardet 10 Apr '12

10 Apr '12

Hi, I can get the DSP working on OMAP3 (BB xM) with the latest beagle raw image (10.7). Install needed packages and load needed drivers: zypper in dsp-tools tidsp-binaries modprobe mailbox_mach modprobe bridgedriver base_img=/lib/dsp/baseimage.dof Then you can try some dsp tools: dsp-probe which returns: *** device: /codec device: /mixer device: /acdn device: /eteedn device: /mmmdn task: DASFTASK_TI task: SYNCCLOCK_TI task: dummy *** dsp-test which returns: *** copied 1000 times successfully *** I have not tested gstreamer DSP plugin yet but I will keep you up-to-date once done! I have 1 question related to module loading. Why mailbox_mach and bridgedriver are not loaded on boot? Do we need some udev rules? Cheers, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 1

Re: [opensuse-arm] build failure due to ldd error?
by Guillaume Gardet 09 Apr '12

09 Apr '12

Le 07/04/2012 00:34, Tomas Cech a écrit : > Hi, > > First, thanks for your answer. > > On Fri, Apr 06, 2012 at 11:17:26AM +0200, Guillaume Gardet wrote: >> Hi, >> >> Le 05/04/2012 22:51, Tomas Cech a écrit : >>> Hi, >>> >>> I enabled compilation of E17 for armv7l and got strange error: >>> >>> /usr/bin/edje_cc: error while loading shared libraries: >>> /usr/lib/liblua-5.1.so: unexpected reloc type 0x03 >>> >>> Full log is accessible with: >>> >>> osc rbl X11:Enlightenment:Nightly emotion openSUSE_Factory_ARM armv7l >>> >>> I believe that this doesn't seem to be packager issue... Any ideas? >>> >>> Best regards, >>> >>> Tomas Cech >>> >> >> I think the liblua you are using was compiled without -fPIC option. > > I added -fPIC to CFLAGS, but the problem is the same. > >> Can you try liblua from openSUSE:Factory:ARM? Or recompile liblua with -fPIC option? > > Unfortunatelly no, E17 still depends on lua 5.1 as there were API > changes... Acording to: osc rbl X11:Enlightenment:Nightly lua51 openSUSE_Factory_ARM armv7l RPM lit reports: ******************************************************************************** lua51-libs.armv7l: W: shlib-with-non-pic-code /usr/lib/liblua-5.1.so The listed shared libraries contain object code that was compiled without -fPIC. All object code in shared libraries should be recompiled separately from the static libraries with the -fPIC option. Another common mistake that causes this problem is linking with ``gcc -Wl,-shared'' instead of ``gcc -shared''. ******************************************************************************** So something get wrong. maybe try to do CFLAGS+=-fPIC instead of CFLAGS=-fPIC or use MYCFLAGS. Have a look at the following links for used option and maybe patches for lua: https://build.opensuse.org/package/view_file?file=lua.spec&package=lua&proj… http://git.buildroot.net/buildroot/tree/package/lua Regards, Guillaume -- 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] build failure due to ldd error?
by Tomas Cech 06 Apr '12

06 Apr '12

Hi, I enabled compilation of E17 for armv7l and got strange error: /usr/bin/edje_cc: error while loading shared libraries: /usr/lib/liblua-5.1.so: unexpected reloc type 0x03 Full log is accessible with: osc rbl X11:Enlightenment:Nightly emotion openSUSE_Factory_ARM armv7l I believe that this doesn't seem to be packager issue... Any ideas? Best regards, Tomas Cech

2 1

[opensuse-arm] ARM TechCon
by Andrew Wafaa 05 Apr '12

05 Apr '12

ARM TechCon is where 3,500 system and software engineers dedicated to designing ARM IP-based designs gather, and is one of the most influential ARM related conferences. ARM would like it if openSUSE and SUSE could attend, preferably with a talk or two ;-) They are now accepting abstracts for ARM® TechCon™. This year's event will be held October 30 - November 1, 2012 at the Santa Clara Convention Center in Santa Clara, CA. Deadline to Submit: Friday, April 27, 2012 ARM TechCon will again have dedicated themes for each day of the event providing a comprehensive curriculum. The 2012 tracks are listed below with a separate submission for Day 1 and Days 2 & 3. Chip Design Day[0] October 30, 2012 *SoC Architecture & Analysis * SoC Design & Verification * SoC Design for Power & Performance * SoC IP Submit Your Abstract[1] Software & Systems Design Days[2] October 31 - November 1, 2012 * Android / Open Source * Computing Platforms * Developing & Debugging * Low Power Design * Microcontroller and Programmable Platforms * Multimedia Processing: Graphics, Audio & Video * Networking & Connectivity * Safety & Security * Software Optimization on ARM-Powered Systems * The Fundamentals of ARM Submit Your Abstract[3] There is a possibility that we can get some sponsorship from the openSUSE travel committee, but I make no guarantees. There is only one item that could be an issue with openSUSE or even SUSE attending the event, SUSE will need to ensure it has enrolled into ARM Connect befor we can attend. ARM will be speaking directly to SUSE about this shortly, so it shouldn't be any real issue. Please let me know if you would be happy to attend and as such present too. There's no free ticket here - if you want to mingle you need to earn it :-) Regards, Andy 0 - http://newsletters.eetimes.com/portal/wts/cemciv2dnP-6ed7eqq6D-D6f4z4cfc 1 - http://newsletters.eetimes.com/portal/wts/cemciv2dnP-6ed7eqq6D-D-f4z4cfc 2 - http://newsletters.eetimes.com/portal/wts/cemciv2dnP-6ed7eqq6D-DDf4z4cfc 3 - http://newsletters.eetimes.com/portal/wts/cemciv2dnP-6ed7eqq6D-Eef4z4cfc -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F -- 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] Fix ARM kernel-default and kernel-u8500
by Guillaume Gardet 02 Apr '12

02 Apr '12

Hi, kernel-default and kernel-u8500 fail to build because eGalax touchscreen is enabled and use the function irq_to_gpio which is not available for default and u8500 kernels. Attached patches solve the problem by disabling the eGalax support for both kernels. Can anyone modify the default and u8500 config files accordingly, please? Guillaume

3 6

[opensuse-arm] armv5 progress
by Bernhard M. Wiedemann 30 Mar '12

30 Mar '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I made progress on the arm5 side of things (to get openSUSE to run on my two openRDs) disassembling some of the non-working programs had shown earlier that there were floating point instructions while Debian's gcc produced function calls in those places. I tried to compile the kernel with floating-point emulation without effect. Reading http://wiki.debian.org/ArmEabiPort I found mention of the __SOFTFP__ macro and that paradoxically it is not set by -mfloat-abi=softfp checking with :| gcc -dM -E -x c -|grep SOFT I found that this is set on Debian, but not on openSUSE. our gcc46.spec had in the armv5 section - --with-float=softfp which I changed to =soft for a local build (OBS does not let me branch a broken package). And it made gcc work finally for armv5 - yay! so please apply this patch: - --- gcc46.spec (revision b6148fab8499be9d98ff39bdabb170ec) +++ gcc46.spec (working copy) @@ -1697,7 +1719,7 @@ %endif %if "%{TARGET_ARCH}" == "armv5tel" --with-arch=armv5te \ - - --with-float=softfp \ + --with-float=soft \ --with-mode=arm \ --with-abi=aapcs-linux \ --disable-sjlj-exceptions \ When I tried to build locally on ARM, I also hit another strange bug, that I only saw on Factory ARM: # (cd /tmp/ ; sudo id ; echo $?) 143 - -- _=======.=======_ _---|____________\/ (____/ /\ _/ \_ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9ld/wACgkQSTYLOx37oWR+VACgl9PFYgyWYELnN67f5C8OJEZT pJMAoPvf+YIvA6DOgRLmRAU6cYziVR17 =dE2T -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 4

[opensuse-arm] friendlyarm mini2440
by Michael Monnerie 23 Mar '12

23 Mar '12

Hi, I'm going to buy a mini2440 board http://www.friendlyarm.net/products/mini2440 Can somebody tell me if I should try with openSUSE-arm, or is it very intensive work atm? I'm new to embedded and arm, so please forgive my unholy question. It's just I'm a fan of openSUSE, and would like to use it on the mini2440 too. Please answer me directly, I'm not subscribed on this list yet. -- mit freundlichen Grüssen, Michael Monnerie, Ing. BSc it-management Internet Services: Protéger http://proteger.at [gesprochen: Prot-e-schee] Tel: +43 660 / 415 6531

2 1

[opensuse-arm] Kernel omap2plus config - Add TI dsp bridge driver
by Guillaume Gardet 19 Mar '12

19 Mar '12

Hi, would it be possible to enable the TI dspbridge (staging) driver in the omap2plus kernel config, please ? As a module, not as built-in. The var is CONFIG_TIDSPBRIDGE. It will enable the use of the integrated DSP in the Texas Instrument SoC. At least the kernel part. Then we could try to package the userspace part. Regards, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 10

[opensuse-arm] Packaging some ARM packages
by Guillaume Gardet 19 Mar '12

19 Mar '12

Hi, I would like to try to do some RPM for ARM using OBS, but I get an unresolvable problem, telling: "nothing provides cmake, nothing provides gcc, nothing provides gcc46, nothing provides glibc, nothing provides rpm, nothing provides tar, nothing provides patch" Any idea how to solve it? Cheers, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 12

[opensuse-arm] Getting started with opensuse
by Alexjan Carraturo 19 Mar '12

19 Mar '12

Hi to all I would like to try opensuse-ARM on a particolar and almost unknow board produce by ST Microelectronics ( http://www.st.com/internet/mcu/product/251211.jsp ). In order to do this I'm tryng to search if exist some minimal rootfs ready (if it's possibile hardfp armv7), or some installation procedure to start. I search on the opensuse site, but I'm unable to find what I'm looking for (surely my fault). So, could anyone help me? Thanks in advance, regards Alexjan. -- Alexjan Carraturo -- Free Software User Group Italia administrator (http://www.fsugitalia.org) Fedora/openSUSE Ambassador member of FSFE Italian Team Twitter/Facebook/Identica: axjslack Blog: http://axjslack.wordpress.com -- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 3

[opensuse-arm] Patches for Firefox on ARM
by Guillaume Gardet 13 Mar '12

13 Mar '12

Hi, On the OBS Factory:ARM Firefox page [0], it is written: "Before submitting changes please check http://www.rosenauer.org/hg/mozilla/ as fixes are often already made there but not synced to this project." Does it mean that all fixes in this repo will be pushed to Factory and it is not necessary to submit a patch? Guillaume [0]: https://build.opensuse.org/package/show?package=MozillaFirefox&project=open… -- 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] Package license
by Guillaume Gardet 13 Mar '12

13 Mar '12

Hi, I have a question about license in spec file. I packaged some Texas Instrument dsp binaries (which will later be used with the OMAP dsp) in my personal OBS instance but the license is the following: http://e2e.ti.com/cfs-filesystemfile.ashx/__key/CommunityServer-Discussions… What I have to write in the license field for the spec file? Cheers, Guillaume -- 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] orc package
by Guillaume Gardet 08 Mar '12

08 Mar '12

Hi, I made a patch to get the orc package built for ARM. I submitted it directly to multimedia:libs (where it is developed). It has been accepted and applied but Factory and Factory:ARM did not get this last version yet. Is there a process I should start or is it automatically done (pull packages once per week or something like that) and I just need to wait? Cheers, Guillaume -- 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] GSoC: openSUSE ARM
by Dirk Müller 07 Mar '12

07 Mar '12

Hi, does anyone have ideas fora good GSoC project around openSUSE ARM? http://en.opensuse.org/openSUSE:GSOC_2012_Ideas We should come up with ideas for this wiki page ASAP . Thanks, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

6 9

[opensuse-arm] Support for Pandaboard ES?
by endym 07 Mar '12

07 Mar '12

Hello, does the Pandabord image from openSUSE factory support the new Pandaboard ES too? Regards, endym -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

Re: [opensuse-arm] Packaging some ARM packages
by Joop Boonen 07 Mar '12

07 Mar '12

On Wed, March 7, 2012 10:09 am, Guillaume Gardet wrote: > > > Le 06/03/2012 17:44, Andrew Wafaa a Ã©crit : >> On 6 March 2012 16:41, Guillaume Gardet <guillaume.gardet(a)free.fr> wrote: >>> Hi, >>> >>> Le 06/03/2012 17:27, Adrian SchrÃ¶ter a Ã©crit : >>>> Am Dienstag, 6. MÃ¤rz 2012, 16:40:30 schrieb Guillaume Gardet: >>>>> Hi, >>>>> >>>>> I would like to try to do some RPM for ARM using OBS, but I get an unresolvable problem, telling: "nothing provides cmake, nothing provides >>>>> gcc, nothing provides gcc46, nothing provides glibc, nothing provides rpm, >>>>> nothing provides tar, nothing provides patch" >>>>> >>>>> Any idea how to solve it? >>>> Build against openSUSE:Factory:ARM/standard for armv7l... >> Hey Guillaume, >> >>> Thanks, it starts to build now. >>> >>> I am quite new to OBS and RPM build in general. I usually do embedded Linux from sources (from scratch) and/or from buildroot.org. >>> >> Well it's good to see you roll your sleeves up and get stuck in! Not sure if you have seen it yet, but this wiki page [0] is pretty useful. >> >> If you need any help, just shout >> >> Regards, >> >> Andy >> >> 0 = http://en.opensuse.org/openSUSE:ARM_distribution_howto > > Thanks for this page. How do I submit new packages which are for ARM only? Is it the same process, submitting it to the Factory and not Factory:ARM? That correct. You first need to submit to a devel project. After that to Factory. > Is there an internal review (on this list or elsewhere) before submitting a patch? When you sent a submit request it will always be reviewed. > > > Guillaume > > -- > To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org > > Regards, Joop. -- 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] openSUSE on Beagleboard xM
by Guillaume Gardet 06 Mar '12

06 Mar '12

Hi, I downloaded images from : http://download.opensuse.org/repositories/openSUSE:/Factory:/ARM/images/ for the beagleboard xM I managed to boot using this kernel and rootfs but I have no modules loaded and there is nothing in /lib/modules, so I can only use built-in drivers. The thing is I did not used initrd since I am not sure how to handle it. I think initrd has all the kernel modules. Could you tell me how to use the initrd with u-boot, please? Cheers, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 48

[opensuse-arm] efika kernel
by Peter Czanik 05 Mar '12

05 Mar '12

Hello, There is a kernel config patch for the imx51 kernel from Bernhard, which are still not applied ( http://lists.opensuse.org/opensuse-kernel/2012-02/msg00036.html ). It was sent 9th February, and the latest imx51 kernel is a few weeks older: czanik@linux-6965:/tmp> rpm -qp --changelog kernel-imx51-3.2.0-2.2.armv7l.rpm | head warning: kernel-imx51-3.2.0-2.2.armv7l.rpm: Header V3 DSA/SHA1 Signature, key ID a4e5a8f4: NOKEY * Wed Jan 25 2012 dkukawka(a)suse.de - fix NULL pointer dereference in DSS2 VENC sysfs debug attr on OMAP4. - commit 2206a5c * Wed Jan 25 2012 mmarek(a)suse.cz - proc: clean up and fix /proc/<pid>/mem handling (bnc#742279, CVE-2012-0056). - commit 4fb112d Could you apply it? Even without graphics, it's more useful, than the current one... Bye, CzP -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 5