From: Thomas Sailer <sailer@scs.ch>
To: jcwren@jcwren.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: USBDEVFS_URB_TYPE_INTERRUPT
Date: Wed, 06 Jun 2001 11:01:48 +0200 [thread overview]
Message-ID: <3B1DF17C.124B1135@scs.ch> (raw)
In-Reply-To: <NDBBKBJHGFJMEMHPOPEGGEICCIAA.jcwren@jcwren.com>
John Chris Wren schrieb:
> I don't really want to write a full-up kernel mode driver for this device,
> but interrupt type messages are the preferred method for communicating,
> since once a message needs to be sent, it should be timely (whereas control
> messages could be delayed a significant amount on a busy USB channel).
If you critically depend on tight timing you'll need a kernel driver
anyway, as your usermode task might be delayed on a busy machine too.
Otherwise you can use bulk ins timed from userspace
Tom
next prev parent reply other threads:[~2001-06-06 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-06 5:54 USBDEVFS_URB_TYPE_INTERRUPT John Chris Wren
2001-06-06 9:01 ` Thomas Sailer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-06 5:31 USBDEVFS_URB_TYPE_INTERRUPT John Chris Wren
2001-06-06 5:36 ` USBDEVFS_URB_TYPE_INTERRUPT Greg KH
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=3B1DF17C.124B1135@scs.ch \
--to=sailer@scs.ch \
--cc=jcwren@jcwren.com \
--cc=linux-kernel@vger.kernel.org \
--cc=t.sailer@alumni.ethz.ch \
/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