From: jtc@redback.com (J.T. Conklin)
To: "Marko Mlinar" <Marko.Mlinar@campus.fri.uni-lj.si>
Cc: <gdb@sources.redhat.com>,
"Damjan Lampret" <lampret@opencores.org>, <igorm@opencores.org>,
"Johan Rydberg" <johan.rydberg@netinsight.se>
Subject: Re: gdb port to or1k
Date: Mon, 30 Apr 2001 10:13:00 -0000 [thread overview]
Message-ID: <5mhez69uqr.fsf@jtc.redback.com> (raw)
In-Reply-To: <004b01c0cee8$5617aaa0$e54902c1@Javor>
>>>>> "Marko" == Marko Mlinar <Marko.Mlinar@campus.fri.uni-lj.si> writes:
>> Many host systems that GDB supports don't even have parallel ports.
>> Those that do don't suport the same set of capabilites (other than
>> open/close and write, those are pretty standard :-).
Marko> We are only interested to add debugging support for host that
Marko> will be really used e.g. we don't have any interest at all to
Marko> use arm host. So we can assume, host should be able to print
Marko> and thus have printer port.
Please note that it is a GDB goal (or at least one of my my goals as
a GDB hacker) that features be available on as many host machines as
possible. While there have been back ends which have been integrated
into GDB that need a special vendor-supplied DLL which ties it to a
single host platform (ie. windows), I'd rather avoid this if at all
possible.
If I understand your intentions, you intend to use a bi-directional
parallel port to bit-bang a JTAG like interface. This limits the
feature to machines with bi-directional parallel hardware running
OS's that allow user-level programs access to the individual lines.
I think this is OK.
Marko> Do you perhaps know if this will work for SUN? And HP machines?
Marko> Is there any way to easily configure this, if platforms use
Marko> different IOCTL numbers? (not to include #ifdefs)
I believe that Andrew Cagney mentioned the ser-* abstraction GBD uses
for serial ports. It may be necessary to do something equivalent for
parallel ports.
Since the ioctl's used by serial tty's is much more standardized on
UNIX and UNIX-like systems (e.g. sgtty, termio or termios), support
for all is located in one source file ser-unix.c. For parallel, we
might need par-hp.c, par-sun.c, etc. It won't be a requirement for
you to supply implementations for all platforms, just that the scheme
be extensible and not preclude other people adding support for their
platforms.
Marko> And on the other hand we don't wan't to use special driver for
Marko> every platform...
I don't think this is as bad as you think. If you make the split
correctly, the bulk will be host independent.
--jtc
--
J.T. Conklin
RedBack Networks
next prev parent reply other threads:[~2001-04-30 10:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 11:17 Marko Mlinar
2001-04-26 15:04 ` J.T. Conklin
2001-04-27 0:04 ` Marko Mlinar
2001-04-27 12:56 ` Andrew Cagney
2001-04-27 23:07 ` Marko Mlinar
2001-04-30 9:45 ` Andrew Cagney
2001-04-30 10:44 ` J.T. Conklin
2001-04-30 10:13 ` J.T. Conklin [this message]
2001-04-30 10:49 ` Damjan Lampret
2001-04-30 18:07 ` Andrew Cagney
2001-04-30 22:15 ` Marko Mlinar
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=5mhez69uqr.fsf@jtc.redback.com \
--to=jtc@redback.com \
--cc=Marko.Mlinar@campus.fri.uni-lj.si \
--cc=gdb@sources.redhat.com \
--cc=igorm@opencores.org \
--cc=johan.rydberg@netinsight.se \
--cc=lampret@opencores.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