From: Jim Blandy <jimb@redhat.com>
To: "Kevin McGrath" <kevinmcgrath2003@hotmail.com>
Cc: sachin@multitech.co.in, insight@sources.redhat.com
Subject: Re: USB support for GDB
Date: Tue, 07 Oct 2003 16:31:00 -0000 [thread overview]
Message-ID: <vt265j1t3gv.fsf@zenia.home> (raw)
In-Reply-To: <Law9-F52wNHlwywSfcq00003a42@hotmail.com>
"Kevin McGrath" <kevinmcgrath2003@hotmail.com> writes:
> Would you use Micosofts WDM DDK, to assist in the development of the
> device drivers for the particular target system. Would the device
> driver be wrote at a layer below GDB & then use Win32 API calls to
> communicate with the Device Driver which in turn would communicate
> with the target device
If I were working on Windows? I don't know much about Windows
development, so I couldn't say. Sachin said he was using Linux, and
already had a sample driver.
next prev parent reply other threads:[~2003-10-07 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 12:58 Kevin McGrath
2003-10-07 16:31 ` Jim Blandy [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-06 6:16 Sachin Bharadwaj
2003-10-06 18:34 ` Jim Blandy
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=vt265j1t3gv.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=insight@sources.redhat.com \
--cc=kevinmcgrath2003@hotmail.com \
--cc=sachin@multitech.co.in \
/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).