From: Daniel Jacobowitz <dan@debian.org>
To: Mark and Janice Juszczec <juszczec@hotmail.com>
Cc: kevink@mips.com, linux-mips@linux-mips.org
Subject: Re: gdbserver and Re: hardware questions
Date: Mon, 29 Dec 2003 11:08:22 -0500 [thread overview]
Message-ID: <20031229160822.GA14229@nevyn.them.org> (raw)
In-Reply-To: <Law10-F22bcHeTHOF2m00063144@hotmail.com>
On Mon, Dec 29, 2003 at 03:31:36PM +0000, Mark and Janice Juszczec wrote:
>
> Kevin, et al
>
>
> >
> >If you want more of a "large format" mipsel platform
> >to experiment with, you might be able to find an old
> >"RISC PC" from Siemens or NEC with an R4000
> >configured little-endian to run NT. Maybe Ralf has
> >one in his attic he'd care to sell you. ;o)
> >
>
> Ralf?
>
> >I don't know that it's the root of your problem, but
> >you should definitely get getty/shells off of whatever
> >serial port you're trying to use for debug.
>
> If I have no shell running on the serial port, how would I start gdbserver?
> Would I have to hard code it into the kernel somehow?
Try changing /etc/inittab to disable the getty, and starting gdbserver
from the system startup scripts in /etc/rc*. I'm assuming you have
some other way than that shell on ttyS0 to modify the filesystem :)
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-12-29 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 15:31 gdbserver and Re: hardware questions Mark and Janice Juszczec
2003-12-29 16:08 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-29 16:27 Mark and Janice Juszczec
2003-12-29 14:09 Mark and Janice Juszczec
2003-12-29 14:18 ` Kevin D. Kissell
2003-12-29 14:18 ` Kevin D. Kissell
2003-12-29 18:11 ` Ralf Baechle
2003-12-29 19:41 ` Karsten Merker
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=20031229160822.GA14229@nevyn.them.org \
--to=dan@debian.org \
--cc=juszczec@hotmail.com \
--cc=kevink@mips.com \
--cc=linux-mips@linux-mips.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