<x-flowed>At 03:08 AM 12/23/2000 -0500, George Metz wrote:
>Random question here, which I figure maybe David, Charles, or one or two
>others might have thought of. Does anyone know if, in practice, there's a
>problem with using the same modules for different architectures?
>
>More specifically, is there going to be a module conflict if I use the
>same modules for the i486 kernel and the i486-NoFPU kernels? What about
>486 and Pentium, or Pentium and 5x86? Thoughts on this? The majority of
>the compile time is taken up with recompiling the modules, so if there's
>no need to do so...
The FPU vs FPU lib is a non issue and has been since the 8086-8087 days. A
given program will effectively never know if it is using FPU hardware or a
FPU library. IIRC on a non FPU computer, a FPU instruction generates a
fault. This is effectively a subroutine call to the FPU library which then
performs the FPU instruction in software.
>As I recall, most 486 kernel tarballs include a standard kernel and a
>NoFPU kernel, so I'm assuming that this won't cause module conflicts. What
>about the rest though? Thoughts? Docs?
I've reached about the same conclusion. I have not seen any docs on this,
either. I have thought about doing a file compare to check for differences
between modules compiled with different options. Maybe some day...
>On a related subject, I now have the kernel tarballs and 2.2.18 1680k
>image up on sourceforge, along with a small bit of HTML to make it nicer
>and not hide the full tarball name. I still can't scp to shell1, but I'm
>able to scp while logged into shell1, so that's good enough.
I came up with a similar work around to get files there. Hope ssh doesn't
break. ;)
>--
>George Metz
>Commercial Routing Engineer
>[EMAIL PROTECTED]
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/leaf-devel
</x-flowed>
