All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Dan Malek <dan@mvista.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: gdb load address and KERNELLOAD
Date: Wed, 04 Apr 2001 17:54:14 +0200	[thread overview]
Message-ID: <20010404155419.8B369281DB@denx.denx.de> (raw)
In-Reply-To: Your message of "Wed, 04 Apr 2001 11:30:56 EDT." <3ACB3E30.E17CC550@mvista.com>


In message <3ACB3E30.E17CC550@mvista.com> Dan Malek wrote:
>
> > The BDM4GDB  project  at  sourceforge  (see  bdm4gdb.sourceforge.net)
> > provides all necessary information to build a home-made parallel port
> > adapter  (schematics, source extension to GDB) which allows to do the
> > same.
>
> Really?  Like it handles all of the memory mapping details, too?

In fact the BDM4GDB had an implementation of MMU support  before  the
BDI200  had  it - credits to Frank Przybylski, who did all (and still
does most of) the work.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
I often quote myself; it adds spice to my conversation.  - G. B. Shaw

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-04-04 15:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-04  0:57 gdb load address and KERNELLOAD Wang Yong
2001-04-04  2:05 ` Dan Malek
2001-04-04  6:42   ` Wolfgang Denk
2001-04-04 15:30     ` Dan Malek
2001-04-04 15:54       ` Wolfgang Denk [this message]
2001-04-05  4:13         ` how to get the physival address jerry
2001-04-05  5:58           ` Dan Malek
2001-04-05  6:28             ` jerry
2001-04-05  6:30               ` Dan Malek
2001-04-05  9:16             ` Gabriel Paubert
  -- strict thread matches above, loose matches on Subject: below --
2001-04-04  3:04 gdb load address and KERNELLOAD Hua Ji

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=20010404155419.8B369281DB@denx.denx.de \
    --to=wd@denx.de \
    --cc=dan@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.