On 12-Mar-00 Kevin D. Kissell wrote:
> The R3900 is quite different in a number of details from the R3900A.
> It has a different ISA (MIPS II+ instead of MIPS I), a different pipeline
> and a different CP0 implementation. And the R3912 has its rather
> peculiar set of on-chip peripherals with, if memory serves, a somewhat
> obnoxious memory map. Do you have a set of documentation for the
> R3912? I do, but I don't know when I will have time to check it against
> the R3000 Linux code.
Yes, I have documentation for the R3912. In fact, if I am allowed to say
this, I wrote most of the R3000 and all of the R3912 code so far in Linux 8)
>>Kevin, please forgive me this question, but has the Linux integration of
>>the FPU emulation code been tested on MIPS CPUs without FPU?
> Yes. Of course. What kind of amateur fire-and-forget hacker do you take
> me for?!! ;-) Specifically, we've run it on the MIPS 4Kc core. Both big
> and little endian. We also ran it on R4400 Indys and R5260 Algorithmics
> platforms with the FPUs disabled in software.
That's exactly what I am wondering about. Does it make a difference for the
emulator if the CPU has an FPU (disabled, obviously) or not?
Personally, I don't have any idea why the emulator works perfectly on an R3000
but not on an R3912.
> I'm not saying that it's perfect - I know it cannot be - but the emulator
> does not get invoked until very late in the boot process, just before init
> fires up, so if you're dieing early on, whatever it is, it ain't the
> emulator, and it isn't the lack of FP. Even without an emulator, the
> 2.2.12 kernel will get as far as trying to run init on an FPU-less
Oh I see, I should have made myself more clear. I have a root filesystem on a
CF card based on declinuxroot (a cut down RedHat 5.1) and my Mobilon boots all
the way through to the login prompt if I delete the fsck from the initscripts.
Booting into single user mode I can easily verify that tools like df or e2fsck
are bombing out with floating point exeptions. My "tests" with the emulator
have been so far: Does df survive? What does fsck do? and things like that.
Well, with the emulator all these tools make the Mobilon crash. Hard. So hard
that even the reset button doesn't work.
Anyway, it looks like we will going to have a fully functional serial driver
soon and that should make debugging somewhat easier.