All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ibon Gotxi Garcia <igotxi@jazzfree.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Linux PPC embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: kgdb and console output
Date: 20 Mar 2003 15:05:18 +0000	[thread overview]
Message-ID: <1048172718.4458.15.camel@muse> (raw)
In-Reply-To: <20030314172536.GF6421@ip68-0-152-218.tc.ph.cox.net>


On Fri, 2003-03-14 at 17:25, Tom Rini wrote:
> On Fri, Mar 14, 2003 at 11:49:50AM +0000, Ibon Gotxi Garcia wrote:
>
> [snip]
> > INIT: INIT: NIT: IT: T: : version 2.78 bootingersion 2.78 bootingrsion
> > 2.78 bootingsion 2.78 bootingon 2.78 booting
> >

>
> It's related to the 'console' support inside of the serial driver / kgdb
> stub.  The best way, IMHO, around this is to use the 'kgdb_demux'
> script.  I don't have the URL handy, but google knows.

I have found it in
http://linux.junsun.net/porting-howto/src/kdmx-1.02.tar.gz

but I'm still unable of making it work. I seems fine when the kernel is
loading, but it begins to do funny thing when we move to userland.

I think the hole point is character scape: GDB packets are
$data#checksum, so when some output (no debug output, just normal one)
is made to the console having '$', '#' or even '+' and '-', the kdmx
script goes mental.

I'm thinking in two possible solutions:

1.- Wait till kgdb has LAN support (gdb packets over udp, instead of
over the serial port).
2.- Patch the console driver (no idea how) to avoid printing '$' or '#'.
Probably a terrible hack, but perhaps useful for development.

Any idea about this?


Cheers.
Ibon.

>
> --
> Tom Rini
> http://gate.crashing.org/~trini/
>
--
Ibon Gotxi Garcia <igotxi@jazzfree.com>


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

  reply	other threads:[~2003-03-20 15:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14 11:49 kgdb and console output Ibon Gotxi Garcia
2003-03-14 17:25 ` Tom Rini
2003-03-20 15:05   ` Ibon Gotxi Garcia [this message]
2003-03-20 15:09     ` 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=1048172718.4458.15.camel@muse \
    --to=igotxi@jazzfree.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 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.