From: Alex Shnitman <alexsh@hectic.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: kgdb/Sandpoint -- patch & help needed
Date: Wed, 20 Sep 2000 15:34:16 +0300 [thread overview]
Message-ID: <20000920153415.A5494@hectic.net> (raw)
In-Reply-To: <39C79BBF.5D34BD5E@mvista.com>; from dan@mvista.com on Tue, Sep 19, 2000 at 01:00:47PM -0400
Hi, Dan!
On Tue, Sep 19, 2000 at 01:00:47PM -0400, you wrote the following:
> > Right, but before calling setup_arch, it prints the linux kernel
> > banner! Here's the code:
>
> The kernel "prints" lots of stuff, and it all goes into a buffer,
> to emerge quite late in the boot process when the (serial)
> console port is initialized for real use by applications.
Ooh,, I didn't know that. Thanks.
> > And I don't see the banner. Did you see it when you encountered this?
>
> You should see a 20 character (or so) ASCII string of coded information
> appear on the serial port used for GDB. The system stops at this
> point, waiting to hear from GDB (as you have already discovered).
Still no dice.. I started minicom on the second serial port, and it
doesn't show anything when I boot the kernel. I can't find any obvious
reason for that. Perhaps someone with a Sandpoint should try it out?
--
Alex Shnitman | http://www.debian.org
alexsh@hectic.net, alexsh@linux.org.il +-----------------------
http://alexsh.hectic.net UIN 188956 PGP key on web page
E1 F2 7B 6C A0 31 80 28 63 B8 02 BA 65 C7 8B BA
For Sale: Parachute. Only used once, never opened, small stain.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-20 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alexsh@hectic.net>
2000-09-18 14:16 ` kgdb/Sandpoint -- patch & help needed Alex Shnitman
2000-09-19 3:39 ` Murray Jensen
2000-09-19 16:39 ` Alex Shnitman
2000-09-19 17:00 ` Dan Malek
2000-09-20 12:34 ` Alex Shnitman [this message]
2000-09-19 17:40 ` Mark A. Greer
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=20000920153415.A5494@hectic.net \
--to=alexsh@hectic.net \
--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.