May 2012 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] Packages to be removed from openSUSE:Factory:ARM i.e. to use the openSUSE:Factory version
by Joop Boonen 15 May '12

15 May '12

Hi all, I saw that the major part of the openSUSE:Factory:ARM is done with gcc47. Some Images also have been build. I' checking out which unmodified packages of openSUSE:Factory build for openSUSE:Factory:ARM. I saw that bash, i4l-base are OK. Can these packages please be removed from openSUSE:Factory:ARM? Or are they there for a specific reason? 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] Can the current openSUSE:Factory:ARM now be published?
by Joop Boonen 15 May '12

15 May '12

Hi, Most packages have been build for openSUSE:Factory:ARM but they haven't been pushed yet (latest publish date April 24). Is it possible to force the publish of the current packages. The everyone can start testing the gcc47 ARM build (for all compiled packages). 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] Display on ARM devices
by Guillaume Gardet 08 May '12

08 May '12

Hi, During the last ARM config update I enabled framebuffer for all devices. I also enabled some DRM drivers (for omap for example) to be able to choose between FB and DRM. What is the best way: Framebuffer or DRM? Maybe it depends on the board used. It may also have a V4L display on some boards. DRM should autoselect configuration (resolution, etc.) depending on the monitor/TV used. But it seems you cannot lower the resolution to gain in responsiveness. Framebuffer must be configured to have a given config. Without config it uses 640x480 as default (at least for omapfb) which is a very low resolution which cannot be displayed on most TV. Maybe we should configure all our boards to have a higher default resolution such as 800x600 or 1024x768 to be able to use a monitor or a TV. I think we should have both as modules (to let the final user to have the choice) and add a config file to load one (framebuffer?) as default. 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 3

[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