From: "Siegfried Schaefer" <s.schaefer@schaefer-edv.de>
To: "Nick - eCos Developer" <n_ecos@targus.net>
Cc: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] RE: USB-Device support
Date: Thu, 25 Jan 2001 04:12:00 -0000 [thread overview]
Message-ID: <002101c086ae$31c68860$1746a8c0@schaeferedv.de> (raw)
Hello,
i have been offline the last to days, so excuse my late answering. I haven't
had a look at the bulk-mode drivers yet. I have played with the hid-mode
drivers and now i am sticking with the iso-mode drivers. One problem i had
with this example driver was for example that you have to insert a 0x42 in
front of a DATA0-Packet answering a Control SETUP-packet to get this packet
through the USBD-stack. Perhaps i haven't understand the usb-protocol
correctly, but till now i haven't find any hint in the spec why this should
be the case. After studying various example codes i just saw that i need
this 0x42 - and all works.
Have fun, Siegfried Schaefer
Schaefer EDV-Dienstleistungen und Softwareentwicklungen
reply other threads:[~2001-01-25 4:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='002101c086ae$31c68860$1746a8c0@schaeferedv.de' \
--to=s.schaefer@schaefer-edv.de \
--cc=ecos-discuss@sources.redhat.com \
--cc=n_ecos@targus.net \
/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).