Loving the new avatar
We now have an even better rap name for him "robini". Thats rather sweet.........
And dont you just love it when he is talking dirty.
tut
"On Tue, 23 Feb 1999 robini at icecube-consulting.com wrote:
> 1. Current target is an old 486SX-50 laptop using grub-0.5/1.44Mb
> floppy to boot.
> * I had to manually #ifdef out the floating point setup code in
> _CPU_Initialize in order to bypass the hard wired floating
> point assembler in there (causes exception on my machine).
> Was there a better way to avoid this problem?
RTEMS is based on the concept of CPU families and CPU models. The
pc386 BSP is currently targetting an i386/i387 combination. Other
BSPs (gen68360, mvme162, etc) use a concept of "BSP models" to use
the same BSP with different CPU models. This allows you to (1)
optimize code for a specific CPU model, (2) avoid illegal
instructions, (3) take into account minor hardware variations.
This concept needs to be applied to the pc386 BSP so there are some
variants like pc486sx or (better) pc386sx. This would change the
CPU model, CPU_CFLAGS, and standard libraries for the BSP to avoid
FP."
And dont you just love it when he is talking dirty.
tut
"On Tue, 23 Feb 1999 robini at icecube-consulting.com wrote:
> 1. Current target is an old 486SX-50 laptop using grub-0.5/1.44Mb
> floppy to boot.
> * I had to manually #ifdef out the floating point setup code in
> _CPU_Initialize in order to bypass the hard wired floating
> point assembler in there (causes exception on my machine).
> Was there a better way to avoid this problem?
RTEMS is based on the concept of CPU families and CPU models. The
pc386 BSP is currently targetting an i386/i387 combination. Other
BSPs (gen68360, mvme162, etc) use a concept of "BSP models" to use
the same BSP with different CPU models. This allows you to (1)
optimize code for a specific CPU model, (2) avoid illegal
instructions, (3) take into account minor hardware variations.
This concept needs to be applied to the pc386 BSP so there are some
variants like pc486sx or (better) pc386sx. This would change the
CPU model, CPU_CFLAGS, and standard libraries for the BSP to avoid
FP."