[EMAIL PROTECTED] writes:
> Okay, I understand the above. But, when I looked at kernel 2.3.6, I saw
> the following section of code. It differs from 2.2.10, and follows
> along the lines of how Phil told me to modify 2.2.10:
>
> @ r0 = syscall number
> @ r1 = syscall r0
> @ r5 = syscall r4
> @ ip = syscall table
> SYMBOL_NAME(sys_syscall):
> mov r6, r0
> eor r6, r6, #OS_NUMBER << 20
> cmp r6, #NR_syscalls @ check range
> movgt r0, #-ENOSYS
> movgt pc, lr
> add sp, sp, #4 @ take of the save of our r4
> ldmib sp, {r0 - r4} @ get our args
> str r4, [sp, #-4]! @ Put our arg on the stack
> ldr pc, [ip, r6, lsl #2]
>
> So, if I follow this route in 2.2.10, things work as expected.
I've just checked my code, and it's not changed. I don't know where
this has come from - sounds like someone is distributing rogue
patches.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King [EMAIL PROTECTED] --- ---
| | | | http://www.arm.linux.org.uk/~rmk/armlinux.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
