linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Kwansuk Kim <kskim@neowave.co.kr>
Cc: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Using gdbserver...
Date: Thu, 28 Dec 2000 15:00:48 -0500	[thread overview]
Message-ID: <3A4B9BF0.EDC73E37@mvista.com> (raw)
In-Reply-To: NEBBKFENMLEDKDHMEHPJIECCCCAA.kskim@neowave.co.kr


Kwansuk Kim wrote:

> I used ethernet on SCC1, and it worked very well except Ctrl-C interrupt.
>
> It didn't worked.

Yep.  That part is missing from the serial port driver.  I finally
got it working in the 8260 sources in 2.3/2.4 and I will shortly update
all of the drivers.  I have lots of KGDB updates for many processor/board
combinations (all slightly different of course), and I am trying to
find some better/common PowerPC KGDB support.

All you can do right now is ensure you have some breakpoints set that
are known to be hit before you type 'continue'.


	-- Dan

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

      reply	other threads:[~2000-12-28 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-28  2:46 Using gdbserver Kwansuk Kim
2000-12-28 20:00 ` Dan Malek [this message]

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=3A4B9BF0.EDC73E37@mvista.com \
    --to=dan@mvista.com \
    --cc=kskim@neowave.co.kr \
    --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 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).