Author: Kai Germaschewski <kai@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 15 Dec 2000 13:41:32 +0100 (CET)
Some people are planning to use the ISDN code in the linux kernel on their MIPS port. They ran into some problems with alignment, and use the following patch to fix their problems. diff -ur isdn-HEAD
Aligning data is the driver's responsibility. The kernel should not fail though even when it is misaligned, only be slow because of misalignment traps. This is needed because the driver can not alway
Without the above fix of aligning skb->data on a 4-byte boundary, the packet would get dropped later on. Question is: Is this the right way to handle this problem, or should netif_rx be smarter and t
The ia64 port cannot handle unaligned memory accesses in kernel mode: arch/ia64/kernel/unaligned.c: /* * Unaligned references in the kernel could come from unaligned * arguments to system calls. We f
Author: Kai Germaschewski <kai@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Sun, 17 Dec 2000 15:30:45 +0100 (CET)
I think they're doing their own port to some special hardware - anyway, I take it they have to fix it to handle the unaligned accesses. Thanks to everyone. --Kai
Nobody apparently tried to use IPX on IA64 yet (due to a different ethernet header length it usually has to deal with an misaligned header) With this there are also plenty of ways to crash an IA64 bo
However, I can't imagine we've made it this long without this being a problem so there must be something I'm missing. It only happens when you use non-{ipv4,ipv6} protocols or devices which do not se
I have been thinking about adding mis-word-aligned read/write macros to the networking code for this reason. Ie. less generic macros that will load half words and merge them instead of the very gene