From: Stelian Pop <stelian@popies.net>
To: Tom Rini <trini@kernel.crashing.org>
Cc: kgdb-bugreport@lists.sourceforge.net,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Amit S. Kale" <amitkale@emsyssoft.com>,
ganzinger@mvista.com
Subject: Re: [Kgdb-bugreport] [KGDB] Make kgdb get in sync with it's I/O drivers for the breakpoint
Date: Tue, 6 Apr 2004 16:51:02 +0200 [thread overview]
Message-ID: <20040406145102.GQ2718@deep-space-9.dsnet> (raw)
In-Reply-To: <20040405233058.GV31152@smtp.west.cox.net>
On Mon, Apr 05, 2004 at 04:30:58PM -0700, Tom Rini wrote:
> Hello. The following interdiff, vs current kgdb-2 CVS makes kgdb core
> and I/O drivers get in sync in order to cause a breakpoint. This kills
> off the init/main.c change, and makes way for doing things much earlier,
> if other support exists.
And it works perfectly for me too (with the pcmcia net card, debug
started by sysrq+g).
There are however a couple of cleanups and a compile fix attached.
> What would be left, tangentally, is some sort
> of queue to register with, so we can handle the case of KGDBOE on a
> pcmcia card. George? Amit? Comments ?
Maybe this could be done in a more kgdb-independent way in the
netpoll layer. There is already some code there who waits for
the carrier on a net card. Maybe this could be extended to also
wait for the network card to appear...
Stelian.
--- drivers/serial/kgdb_8250.c.ORIG 2004-04-06 12:44:01.000000000 +0200
+++ drivers/serial/kgdb_8250.c 2004-04-06 12:50:13.000000000 +0200
@@ -63,6 +63,9 @@
static atomic_t kgdb8250_buf_in_cnt;
static int kgdb8250_buf_out_inx;
+/* forward decl */
+struct kgdb_serial kgdb8250_serial_driver;
+
/* Determine serial information. */
static struct serial_state state = {
.magic = SSTATE_MAGIC,
@@ -131,7 +134,7 @@
/*
* Wait until the interface can accept a char, then write it.
*/
-void
+static void
kgdb_put_debug_char(int chr)
{
while (!(serial_inb(kgdb8250_port + (UART_LSR << reg_shift)) &
@@ -170,7 +173,7 @@
* Empty the receive buffer first, then look at the interface hardware.
*/
-int
+static int
kgdb_get_debug_char(void)
{
int retchr;
@@ -393,7 +396,7 @@
}
module_init(kgdb8250_hookup_irq);
-int
+static int
kgdb_hook_io(void)
{
/* If we've already been initialized, return. */
--
Stelian Pop <stelian@popies.net>
next prev parent reply other threads:[~2004-04-06 14:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 23:30 [KGDB] Make kgdb get in sync with it's I/O drivers for the breakpoint Tom Rini
2004-04-06 14:51 ` Stelian Pop [this message]
2004-04-06 14:57 ` [Kgdb-bugreport] " Tom Rini
2004-04-06 15:30 ` Stelian Pop
2004-04-06 20:58 ` George Anzinger
2004-04-06 21:04 ` Tom Rini
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=20040406145102.GQ2718@deep-space-9.dsnet \
--to=stelian@popies.net \
--cc=amitkale@emsyssoft.com \
--cc=ganzinger@mvista.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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