From: Momchil Velikov <velco@fadata.bg>
To: Dan Malek <dan@netx4.com>
Cc: Shuangjun Zhu <r44089@email.sps.mot.com>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Kernel debug about Linux for PowerPC
Date: Tue, 07 Mar 2000 17:45:31 +0100 [thread overview]
Message-ID: <38C5322B.3BF6B11B@fadata.bg> (raw)
In-Reply-To: 38C51F12.3E6A0E08@netx4.com
Dan Malek wrote:
>
> Momchil Velikov wrote:
>
> > You have to write these functions yourself.
>
> No, you don't. Just download the kernel sources for
> linuxplanet-2.2.13 from MontaVista (ftp.mvista.com).
> It has the kgdb support.
Yep, you don't have to, iff some kind soul has already written
these for your particular device on your particular board ;-)
Regards,
-velco
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-07 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-07 3:35 Kernel debug about Linux for PowerPC Shuangjun Zhu
2000-03-07 10:04 ` Momchil Velikov
2000-03-07 15:24 ` Dan Malek
2000-03-07 16:45 ` Momchil Velikov [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-03-08 3:14 Shuangjun Zhu
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=38C5322B.3BF6B11B@fadata.bg \
--to=velco@fadata.bg \
--cc=dan@netx4.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=r44089@email.sps.mot.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).