Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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: Fri, 27 Apr 2001 00:04:00 -0000	[thread overview]
Message-ID: <004b01c0cee8$5617aaa0$e54902c1@Javor> (raw)
In-Reply-To: <5mhezbmi6i.fsf@jtc.redback.com>

> 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 :-).
We are only interested to add debugging support for host that
will be really used e.g. we don't have any interest at all to use arm host.
So we can assume, host should be able to print and thus have printer port.
Do you perhaps know if this will work for SUN? And HP machines?
Is there any way to easily configure this, if platforms use different IOCTL
numbers? (not to include #ifdefs)
And on the other hand we don't wan't to use special driver for every
platform...
Well, in any case we can write centronics parallel port "compatible" drivers
for those hosts we want to have supported.

> I don't have enough bandwidth free to directly contribute, but I'll be
> available to advise when the time comes.  I suspect that many of the GDB
> hackers are in the same boat, but I'll let them speak for themselves.
Thanks.

Marko


  reply	other threads:[~2001-04-27  0:04 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 [this message]
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

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='004b01c0cee8$5617aaa0$e54902c1@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