From: Wolfgang Denk <wd@denx.de>
To: Richard Danter <richard.danter@windriver.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 750/107 CHRP question
Date: Fri, 01 Aug 2003 14:17:35 +0200 [thread overview]
Message-ID: <20030801121740.1D9ADC602D@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 01 Aug 2003 10:02:46 BST." <3F2A2CB6.4030104@windriver.com>
Dear Richard,
in message <3F2A2CB6.4030104@windriver.com> you wrote:
>
> > My understanding is that more than just a static mapping is needed
> > for full MMUP support.
>
> You are correct. Only the kernel and drivers statically linked can be
> easily debugged. It could be possible to debug modules but since the
> addresses change every time you load them it would not be practical. You
> would have to edit the symbol files (*.ab) each time.
Thanks for confirming this.
> For complete MMU handling the debugger would need to know where to find
> the mapping tables and remap it's symbol info. None of our debuggers can
> do that yet.
Are there any plans to add such support?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Intuition, however illogical, is recognized as a command prerogative.
-- Kirk, "Obsession", stardate 3620.7
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-08-01 12:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030801082845.A38F6C602D@atlas.denx.de>
2003-08-01 9:02 ` 750/107 CHRP question Richard Danter
2003-08-01 12:17 ` Wolfgang Denk [this message]
2003-08-01 12:24 ` Richard Danter
2003-07-31 16:54 Richard Danter
2003-07-31 21:07 ` Matt Porter
2003-07-31 21:41 ` Richard Danter
2003-07-31 22:48 ` Matt Porter
2003-07-31 23:32 ` Wolfgang Denk
2003-08-01 8:16 ` Richard Danter
2003-08-01 4:34 ` Sangmoon Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030801121740.1D9ADC602D@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=richard.danter@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).