This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
wince, dcache, and memory region attributes
- To: cgf at cygnus dot com
- Subject: wince, dcache, and memory region attributes
- From: jtc at redback dot com (J.T. Conklin)
- Date: 13 Nov 2000 12:34:05 -0800
- Cc: gdb at sourceware dot cygnus dot com
- Reply-To: jtc at redback dot com
The dcache is usually disabled when GDB starts, but the wince target
enables it with a call to set_dcache_state(1).
I am trying to get a bit of backround about why the wince target does
this. In my experience with other embedded systems/OSs, a GDB user
generally wouldn't want GDB caching memory because of memory mapped
I/O devices. Is there something about Win-CE or the typical Win-CE
developer that is different?
The reason I ask is that after the memory region attribute code is
committed, a GDB user will be able to define regions of memory and
specify the cache / nocache attribute separately for each one. But
when a user does not define regions, or accesses are made to memory
that is not within a defined region, the "default" set of attributes
are used. At present, the default attributes has the nocache set.
Will this make things difficult for Win-CE users? I'd rather not
provide knobs that change the default memory attributes depending on
what targets are linked into GDB.
--jtc
--
J.T. Conklin
RedBack Networks