From: "Marko Mlinar" <Marko.Mlinar@campus.fri.uni-lj.si>
To: <jtc@redback.com>
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 22:15:00 -0000 [thread overview]
Message-ID: <005f01c0d1fd$cd241940$c64902c1@Javor> (raw)
In-Reply-To: <5mhez69uqr.fsf@jtc.redback.com>
> 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.
We would really appreciate that. And, like Damjan said -- parallel ports
are becomming more and more used.
> 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.
Our interface is designed in a way, that it needs 8 outputs and 3 inputs.
This can be accomplished by centronics (oldest parallel port mode) and
is fully supported by IOCTLs (LP driver).
But, this kind of interface would be pretty slow. It would be much better
if we use INP and OUTP, where port addresses and interface is same
for all parallel ports. It would be nice if this faster option would be
available
for at least most popular hosts (Linux, win, sun).
Looking it long term for GDB - parallel port can be much faster (especially
bidirectional - EPP or ECP) than serial ports or ethernet, so many vendors
may choose it as a base for their remote protocol.
Marko
prev parent reply other threads:[~2001-04-30 22:15 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
2001-04-30 10:49 ` Damjan Lampret
2001-04-30 18:07 ` Andrew Cagney
2001-04-30 22:15 ` Marko Mlinar [this message]
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='005f01c0d1fd$cd241940$c64902c1@Javor' \
--to=marko.mlinar@campus.fri.uni-lj.si \
--cc=gdb@sources.redhat.com \
--cc=igorm@opencores.org \
--cc=johan.rydberg@netinsight.se \
--cc=jtc@redback.com \
--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