[Gta04-owner] debian armhf + linux 3.1

Johannes Schauer j.schauer at email.de
Tue Oct 25 09:22:02 CEST 2011


On Sun, Oct 23, 2011 at 02:22:21AM +0200, Johannes Schauer wrote:
> So one of my goals was, to get debian armhf running on the gta04.
> There seems to be a problem with udev with the 2.6.32 kernel though
> and I think it is this bug that I reported a few months ago:
> http://bugs.debian.org/625752 But I didnt investigate more and also
> didnt want to go for the old kernel but rather try out bleeding edge
> stuff.

So it turned out, that it was really this bug and after applying a small
patch to the .32 kernel source debian unstable booted properly


diff --git a/arch/arm/include/asm/unistd.h b/arch/arm/include/asm/unistd.h
index 4e506d0..8f32b6b 100644
--- a/arch/arm/include/asm/unistd.h
+++ b/arch/arm/include/asm/unistd.h
@@ -391,6 +391,8 @@
 #define __NR_pwritev                   (__NR_SYSCALL_BASE+362)
 #define __NR_rt_tgsigqueueinfo         (__NR_SYSCALL_BASE+363)
 #define __NR_perf_event_open           (__NR_SYSCALL_BASE+364)
+#define __NR_recvmmsg                  (__NR_SYSCALL_BASE+365)
+#define __NR_accept4                   (__NR_SYSCALL_BASE+366)
  * The following SWIs are ARM private.
diff --git a/arch/arm/kernel/calls.S b/arch/arm/kernel/calls.S
index 9314a2d..1dff6a0 100644
--- a/arch/arm/kernel/calls.S
+++ b/arch/arm/kernel/calls.S
@@ -375,6 +375,7 @@
 /* 365 */      CALL(sys_recvmmsg)
+               CALL(sys_accept4)
 #ifndef syscalls_counted
 .equ syscalls_padding, ((NR_syscalls + 3) & ~3) - NR_syscalls
 #define syscalls_counted


One also has to change the line for the serial tty in /etc/inittab back
from /dev/ttyO2 to /dev/ttyS2.

With these changes debian unstable will boot happily with the .32

> One of the still remaining issues is the display which seems to try to
> show a 640x480 image instead of 480x640. Is this maybe a kernel bug?
> Any idea how to fix it?

When taking a "screenshot" with fbgrab with the 3.1 kernel it indeed
seems that Xorg assumes 640x480 resolution:


lev, is this a known problem of 3.1?

cheers, josch

More information about the Gta04-owner mailing list