From: Sape Mullender <sape@plan9.bell-labs.com>
To: rs_rlab@mail.ru, 9fans@cse.psu.edu
Subject: Re: [9fans] usb or lp
Date: Tue, 30 Nov 2004 15:21:32 -0500 [thread overview]
Message-ID: <b4e9b0fad5e56087e8e6626d1fec6605@plan9.bell-labs.com> (raw)
In-Reply-To: <14816809671.20041130210859@mail.ru>
> New usb driver not configure file epXdata for writing or inputing, old
> driver do this. Why this happen?
>
> When I run usb/usbd -v -d I can see this:
>
> .... maxpkt 64 interval 0ms [OUT] [Bulk] #usbd know about direction on this endpoint
> .... maxpkt 64 interval 0ms [IN] [Bulk]
I saw that too yesterday. I'll look into it tonight. Hopefully you'll have
an update tomorrow.
Sape
next prev parent reply other threads:[~2004-11-30 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 8:54 Sergey Reva
2004-11-29 2:29 ` Kenji Okamoto
2004-11-29 3:00 ` Russ Cox
2004-11-29 13:21 ` Sergey Reva
2004-11-30 0:56 ` Kenji Okamoto
2004-11-30 15:07 ` Sape Mullender
2004-11-30 16:28 ` Sape Mullender
2004-11-30 19:08 ` Sergey Reva
2004-11-30 20:21 ` Sape Mullender [this message]
2004-12-01 17:20 ` Sape Mullender
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=b4e9b0fad5e56087e8e6626d1fec6605@plan9.bell-labs.com \
--to=sape@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
--cc=rs_rlab@mail.ru \
/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 NNTP newsgroup(s).