[vmips] Re: TLB question

[Cable Guy]

I just wanted to add that the only filesystem in use is the initial 4
MB ramdisk (initrd) that is embedded into the kernel and mounted
read-write on "/".  It's approx. 70% full.  There is no swap partition
so pages are either in memory or they're not.  It is physically
impossible for them to be swapped out anywhere and then paged back in
at some later point.  With a total VMIPS RAM address space of 32 MB I
don't see how memory constraints could cause the page containing
0x440534 to be loaded into memory and then very soon after that find
the page containing 0x440538 is not accessible.  Of course, the first
location is never actually accesssible either, so it's just a strange
situation.  I found an interesting page describing the R3000 TLB
Structure at http://www.vyomworld.com/gate/cs/os/11.asp  but, as I
said, off the top of my head I could only describe the process in very
general terms.  I suppose it's something I'm about to learn a lot more
about, like it or not, in the very near future :)


On Sun, 16 Jan 2005 04:24:00 -0500, Cable Guy <donimus at gmail.com> wrote:
> After rebuilding BusyBox and VMIPS roms at least a hundred times over
> the last few weeks I think I'm very close now to getting Linux working
> on VMIPS.  Here's my setup:
> 
> Linux stock 2.4.28 kernel
> uClibc 0.9.27 (built without debugging symbols)
> busybox-1.00 (built with debugging symbols and linked statically)
> gcc 3.0.4 MIPS EL cross-compiler with software floating point enabled
> binutils 2.13
> VMIPS 1.3
... <snip> ...