Motorola Mocks-up MRAM
zakath writes "EETimes.com has an article on Motorola's successful presentation of 256-kilobit MRAM at ISSCC this week (Instant-on PCs anyone?). While they're still far from commercial production (2004 is their target) its nice to see some progress being made. Please tell me RAMBUS has no patents for this tech..."
I see a lot of posters here saying that "If they double their capacity every x months, that's only 8MB in 4 years" or something...
When working on a new technology, having a 256kbit chip is just as useful as a 256mbit chip, when all you're doing is proving the technology out. They have no reason to be trying to produce massive dies yet, because all that will do is reduce their yields... and when they're making one-off runs of these to test them, that's a killer.
I'm certain that by the time they go into production, the capacity will be impressive.
However, I don't think one would need to save the entire state of system memory for this to be useful. Aside from embedded systems, consider the possibility of an OS that uses a proper swap system and just makes sure the entire physical memory is written to swap when the system suspends. If the MRAM is sufficient to keep the core kernel state and information about the swap pages, your restart would just need to flag all the physical memory as free pages, with everything currently swapped out. Sure it wouldn't be "instant on", but it would be far closer than I've seen to date.
On the flip side, you could probably do something similar with Linux by putting in a boot patch that checks the swap space for a signature indicating it should reload the memory from the swap space instead of going through a full boot process. You'd still have the usual issues of needing to reset hardware, but it would probably be faster than a full boot.
I do not fail; I succeed at finding out what does not work.
Solid state, eh? I can FINALLY get rid of that vacuum tube ram... man my power bill will go so far down.
-
I've had enough abrasive sigs. Kittens are cute and fuzzy.
Now, if you use a decent OS, like Windows, the kernel can have suitable protection mechanisms, such as security through obscurity. In Linux, a virus knows exactly where to put itself, but in Windows, the kernel is like a maze of twisty little functions, all alike. As you can see, if you're gonna use instant-on technology, you should use a suitable OS.