From: "Peter Ryser" <Peter.Ryser@xilinx.com>
To: Peter Reilley <micrio@mv.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: ser-ocd.c gone! What now?
Date: Wed, 01 Aug 2001 09:29:00 -0000 [thread overview]
Message-ID: <3B682F5A.88AB5CDE@xilinx.com> (raw)
In-Reply-To: <001101c11a35$7926a850$05d145cc@ppro>
[..]
> The newer release for the Intel Xscale
> processor uses the remote daemon. The source is there as well.
Probably, I am looking in the wrong place. I cannot find the source code for
OCDemon. All I can find are the modified source files for GDB (
http://www.ocdemon.com/gdb_mods.tgz ).
[..]
> As to GPL, the law is more than just what is written, it is also
> precedent. In this case the precedent is clearly that GDB interfaces
> with proprietary debug monitors, propriarity drivers, and propriarity
> hardware. The world is simply not black and white.
I agree. But - unfortunately - this seems not to be the general opinion...
[..]
> I have done the Linux and Solaris work for Macraigor and that includes the
> 405.
Probably, I am looking in the wrong places again, but I cannot find support for
the 405 neither in the GDB main branch nor in the GDB modifications mentioned
above. The register set for the 405 is different than for the 403. I see no 405
specific register set.
- Peter
next prev parent reply other threads:[~2001-08-01 9:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-31 19:56 Peter Reilley
2001-08-01 9:29 ` Peter Ryser [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-31 10:53 Peter Ryser
2001-07-31 14:11 ` DJ Delorie
2001-07-31 18:39 ` Peter Ryser
2001-08-01 7:03 ` DJ Delorie
2001-07-31 20:06 ` Steven Johnson
2001-08-01 6:50 ` Quality Quorum
2001-08-01 9:01 ` Peter Ryser
2001-08-01 10:06 ` Quality Quorum
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=3B682F5A.88AB5CDE@xilinx.com \
--to=peter.ryser@xilinx.com \
--cc=gdb@sourceware.cygnus.com \
--cc=micrio@mv.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