[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [dsdp-dd-dev] Memory view and addressable size
|
On Wed, Jun 21, 2006 at 09:11:28AM -0500, John Cortell wrote:
> So, yes, I'd initially thought a debugger backend could use the
> target memory description to automatically "do the right thing", but
> I've been told that in some architectures, reading a chunk of memory
> with different access sizes intentionally produces different results.
> For example, read 0x10000 as a byte, and the peripheral will give you
> a set of status bits; read it as 16 bits, and it will provide you
> data.
OK, that's what I had in mind and was interested in. I still think we
could do this without user interface for it (by providing those two as
"different" memory mapped registers, and the memory mapped register
description indicating the access width), but that's much weaker than
"there's always one right answer".
> I've been told this sort of thing is more typical in systems
> with a constrained memory space.
... Wouldn't that be contrained address space or bus space? It's not
memory-backed, but it might save you a few gates. Well, off-topic
for here.
--
Daniel Jacobowitz
CodeSourcery
