|
![](/i/fill.gif) |
Orchid XP v8 wrote:
> Like I said, it seems there's a relationship between capacity and speed,
> such that by the time you get to this size, there wouldn't be much speed
> advantage to putting it on-chip.
In all the cases I know about, the problem was not that, but that there was
a concern that there was a cap on the amount of memory.
Either you need X meg of memory to do what your chip is designed to do, or
you want an arbitrary "lots" of memory. (E.g., you're either building a
phone that doesn't run apps not installed when you built it, or you want to
run as many apps at once as you want.) If you ever want to add RAM, you
need to have the interface stuff for it anyway. If you don't ever want to
add RAM, chances are you don't need more than a few hundred meg to support
your single-chip application.
--
Darren New, San Diego CA, USA (PST)
Eiffel - The language that lets you specify exactly
that the code does what you think it does, even if
it doesn't do what you wanted.
Post a reply to this message
|
![](/i/fill.gif) |