From: Dan Cross <crossd@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] new usb stack and implicit timeouts
Date: Mon, 20 Jul 2009 11:07:05 -0400 [thread overview]
Message-ID: <aa7e41150907200807o50ea6c0dn2305033766f6a38b@mail.gmail.com> (raw)
In-Reply-To: <599f06db0907200012p3c3c09d1k6e9f50c38fb7a2c0@mail.gmail.com>
Pardon me if this is totally ignorant, but can't we just have a ctl
message to control a timeout, which applications may then set on their
own?
On Mon, Jul 20, 2009 at 3:12 AM, Gorka Guardiola<paurea@gmail.com> wrote:
> On Sun, Jul 19, 2009 at 5:58 PM, Francisco J Ballesteros<nemo@lsub.org> wrote:
>> On Sun, Jul 19, 2009 at 5:46 PM, <cinap_lenrek@gmx.de> wrote:
>>> http://www.beyondlogic.org/usbnutshell/usb6.htm#SetupPacket
>>>
>>
>> IIRC, I think the host controller is responsible for timing out
>> requests sent to the device (I refer to setup packets), but my uchi
>> does not. In any case, I don't think anyone wants to remove timeouts
>> from ctl requests.
>>
>>
>
> I am unsure I would remove timeouts even from bulk endpoints.
> It is true that some devices (the usb/serial for example) need to
> read for an undefined time waiting for data, but I don't think that is
> an issue as long
> as the timeouts are long enough, doing polling is quite easy. There is
> polling in the
> lower levels anyway.
>
> On the other hand, I think smart card readers go for
> lunch on a read and may never come
> back if there is no timeout. Of course alarm() can be used, but
> a timeout makes it simpler. I prefer having to poll on some
> cases than having to use signals on others.
>
> --
> - curiosity sKilled the cat
>
>
next prev parent reply other threads:[~2009-07-20 15:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-19 7:16 cinap_lenrek
2009-07-19 7:21 ` Bruce Ellis
2009-07-19 7:54 ` cinap_lenrek
2009-07-19 9:07 ` Francisco J Ballesteros
2009-07-19 11:05 ` Richard Miller
2009-07-19 11:30 ` Francisco J Ballesteros
2009-07-19 11:51 ` Richard Miller
2009-07-19 11:56 ` Francisco J Ballesteros
2009-07-19 13:40 ` erik quanstrom
2009-07-19 13:53 ` erik quanstrom
2009-07-19 14:03 ` Richard Miller
2009-07-19 14:32 ` erik quanstrom
2009-07-19 15:14 ` Francisco J Ballesteros
2009-07-19 15:46 ` cinap_lenrek
2009-07-19 15:58 ` Francisco J Ballesteros
2009-07-20 7:12 ` Gorka Guardiola
2009-07-20 15:07 ` Dan Cross [this message]
2009-07-20 16:25 ` Francisco J Ballesteros
2009-07-20 18:10 ` Lyndon Nerenberg
2009-07-20 19:51 ` Dan Cross
2009-07-21 8:51 ` Francisco J Ballesteros
2009-07-19 15:36 ` Richard Miller
2009-07-19 11:41 ` Charles Forsyth
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=aa7e41150907200807o50ea6c0dn2305033766f6a38b@mail.gmail.com \
--to=crossd@gmail.com \
--cc=9fans@9fans.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 NNTP newsgroup(s).