Drew Northup wrote: > There is a reason that we didn't use the ones in the kernel. It is that > we need to have portability to other platforms. (There are other issues > too...., but for the moment, that is the most important.)
The most important actually is that the nexus functions need to be present in *both* the Linux host address space and the monitor address space. So simply calling a routine from the Linux kernel is right out ... We must be extremely careful what can be used in those places, the best thing would be not to have any external dependecies at all. It probably happens to work because memset and memcopy are actually implemented as inline functions, but this is quite fragile. If you want optimized routines, I'd suggest to copy over a version from some (presumably LGPL'd) package like glibc and put them inline, making sure they work in all required constellations (i.e. no external dependecies, position independent code, ...). Bye, Ulrich -- Dr. Ulrich Weigand [EMAIL PROTECTED]
