For our (non-linux) embedded systems, if we're going to run from
flash, we store the executable in flash uncompressed. Price is an
issue which favors RAM, but speed issues no longer favor RAM - the new
intel burst flash is faster than RAM in one of our systems.
isn't it only faster for burst reads tho? that sort of speed increase
doesn't really help when running code..
Rob
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
quoted
For our (non-linux) embedded systems, if we're going to run from
flash, we store the executable in flash uncompressed. Price is an
issue which favors RAM, but speed issues no longer favor RAM - the new
intel burst flash is faster than RAM in one of our systems.
Rob Taylor writes:
isn't it only faster for burst reads tho? that sort of speed increase
doesn't really help when running code..
I think you might be mistaken here. Code accesses tend to be very linear, and
since the Instruction cache loads entire lines at a time, burst accesses are a
big win for code.
Regards,
Graham
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/