A little theory first. As you may know, we've got FPU on board on every router. To be more precisely, it's not a real FPU, it's a FPU emulator. Which means every FPU command is been «atomized» on-the-fly down to simple arithmetic operations which can be executed on CPU. I don't know how this emulator becomes a standard part of MIPS SoCs, may be it's a part of some spec like MIPS R3000. So, every program can be compiled for using FPU or not: hard-float and soft-float code respectively. I found some floating points operations can be executed twice faster when FPU emulator is not used. I know we can't recompile whole Tomato code as a soft-float due to proprietary Broadcom binaries, but we may use soft-float code for any user-space software. You may do your own tests on Tomato using any of two Entware feed you want: * a hard-float feed (which was available all time): wget -O - http://entware.wl500g.info/binaries/entware/installer/entware_install.sh | sh * a soft-float feed (which was created for DD-WRT and Zyxel Keenetic guys, who's using soft-float code for their kernels): wget -O - http://entware.wl500g.info/binaries/mipselsf/installer/entware_install.sh | sh There is no any barriers for using soft-float repo on hard-float based firmware (including Tomato) but not vice versa: on soft-float firmware you'll get "Bus error" when trying to use hard-float repo.