public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed

From: Matt Porter <mmporter@cox•net>
To: linuxppc-dev@lists•linuxppc.org
Subject: Move kgdb init code?
Date: Mon, 24 Jun 2002 22:10:20 -0700	[thread overview]
Message-ID: <20020624221020.A14330@home.com> (raw)


Hi all,

I've created a generic ns16550 binding to kgdb in hopes of making
enabling kgdb support less of a per-board hack.  It utilizes the
information populated in rs_table to configure the UARTs (code
stolen from a number of our other polled 16550 code areas).  The
only problem is that for systems that use early_serial_init() to
configure serial port usage, the current location of the kgdb
init code is not suitable.  early_serial_init() is run during
during a port's ppc_md.setup_arch if it is being used and so
requires the the kgdb initialization be performed after
ppc_md.setup_arch runs.

Since I don't personally use kgdb on a day-to-day basis, I'm
wondering what most people use it for.  I would guess that it
is not typically used for board bringup since it is available
so late in init code (and progress messages are available even
earlier if one can't/won't use a hardware debugger).  If most
people are using it for device driver debug, then it doesn't
seem that moving the init code after ppc_md.setup_arch would
be a problem.  It would enable kgdb in a more general purpose
way with the generic 16550 support, and somebody doing new
bringup could always move the init code earlier for their
specific case.

Any objections or alternatives?

Thanks,
--
Matt "I use a BDI2000" Porter
porter@cox•net
This is Linux Country. On a quiet night, you can hear Windows reboot.

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

next             reply	other threads:[~2002-06-25  5:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-25  5:10 Matt Porter [this message]
2002-06-25 16:19 ` Move kgdb init code? Frank Rowand
2002-06-25 20:50   ` Matt Porter
2002-06-25 21:02     ` Frank Rowand
2002-06-25 22:05     ` Dan Malek
2002-06-25 22:39       ` Matt Porter
2002-06-26  2:50         ` Dan Malek
2002-06-26  8:25           ` Matt Porter
2002-06-26 14:47             ` Dan Malek

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=20020624221020.A14330@home.com \
    --to=mmporter@cox$(echo .)net \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox