On Tue, 4 Oct 2005, Kevin D. Kissell wrote: > FWIW, the 4KSc is a strict superset of the 4Kc (anticipating > *some* of the Release 2 features, but not requiring them to be > used) and the 4KSd is a strict superset of the 4KE. I would > not recommend configuring CPU_MIPS32_R2 for the 4KSc. Well, the patch asked GCC to use the instruction set of the "4kec" CPU for both (and also the "mips32r2" ISA, but that's overridden by the former), so it must have been incorrect in the first place -- I have only referred to this. > They also have some physical security and cryptography accelleration > features, some of which use extended CPU state that would > require some kernel context management support if anyone wanted > to actually use them in Linux applications. The real point of > having a CPU_4KSC config flag would be to enable building-in > such support. This would make sense, but I'm afraid the proposal was far from that... Maciej
