On Thu, 2007-03-22 at 12:41 +0100, Sam Ravnborg wrote: > Yep - realized this when I took a closer look. > One thing striked my mind. It is correct that new things gets added > to i386 first these days?
Personally I tend to do PowerPC first, but most others seem to do i386, yes. There are still system calls being added to i386 and not x86_64... init/missing_syscalls.h:947:3: warning: #warning syscall getcpu not implemented init/missing_syscalls.h:950:3: warning: #warning syscall epoll_pwait not implemented init/missing_syscalls.h:953:3: warning: #warning syscall lutimesat not implemented init/missing_syscalls.h:956:3: warning: #warning syscall revokeat not implemented init/missing_syscalls.h:959:3: warning: #warning syscall frevoke not implemented > To me it looks like x86_64 is growing larger than i386 among the > developers these days so using asm-x86_64/unistd.h could be a better > choice? Or perhaps the union of i386, x86_64 and powerpc. But I think i386 is good enough for now. -- dwmw2 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
