public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Stephane Carrez <Stephane.Carrez@worldnet.fr>
To: gdb@sourceware.cygnus.com
Subject: Monitor support in machine -tdep.c file?
Date: Wed, 06 Sep 2000 13:53:00 -0000	[thread overview]
Message-ID: <39B6CBFB.9462A94E@worldnet.fr> (raw)

Hi!

I'm adding the support for Buffalo monitor for 68hc11 in Gdb (using the CME11E9
board from Axiom Manufacturing). I'm using the Gdb generic monitor framework.

Is it acceptable to put such monitor support in my m68hc11-tdep.c file?

For other monitors, it's true that a separate file is defined for each kind
of monitor.  But I would like to avoid introducing a new file in Gdb for
something that will always be there for 68hc11.

I understand that in the past the various monitors were selected based on
the configury stuff.  With the multi-arch, it seems to me we should always
have those monitors.  In that context, do we really need to separate the
monitor from the machine specific part? (most monitors are machine specific).

Thanks for any opinions about that,

	Stephane

-----------------------------------------------------------------------
         Home                               Office
E-mail: stcarrez@worldnet.fr               Stephane.Carrez@sun.com
WWW:    http://home.worldnet.fr/stcarrez   http://www.sun.com
Mail:   17, rue Foucher Lepelletier        6, avenue Gustave Eiffel
        92130 Issy Les Moulineaux          78182 Saint Quentin en Yvelines
        France

             reply	other threads:[~2000-09-06 13:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-06 13:53 Stephane Carrez [this message]
2000-09-07 12:17 ` J.T. Conklin

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=39B6CBFB.9462A94E@worldnet.fr \
    --to=stephane.carrez@worldnet.fr \
    --cc=gdb@sourceware.cygnus.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).