Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

68010's still need an MMU for virtual memory. So do 68020's, now that I think of it.


It might have been the 68030 that I was thinking of.


I see some evidence that an MMU is optional: https://news.ycombinator.com/item?id=7684824


MMU is optional, unless you want virtual memory. The 68010 fixes a bug in the 68000 whereby it didn’t stack enough information to recover from an address or bus error, but you still need an MMU if you want to actually do virtual memory in any performant fashion.


My understanding was the 68010 had "support" for virtual memory when used with an MMU due to improved exception recovery handling. For example, when accessing an invalid / unmapped memory address. See https://en.wikipedia.org/wiki/Motorola_68010 68000's didn't have that capability. An MMU of some sort would still be needed to implement the virtual-to-physical mapping of memory addresses.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: