From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] usb ohci question
Date: Tue, 22 Feb 2011 17:50:38 +0100 [thread overview]
Message-ID: <AANLkTikP9hODfcrqKEJsJQx-HrksY=dWCvM+qDJ_iRje@mail.gmail.com> (raw)
In-Reply-To: <20110222164458.C9F1665D3E@server.hemiola.co.uk>
In general, there are more ilocks than needed, out of paranoia.
I don't have the code here now, but you might be right.
thanks
On Tue, Feb 22, 2011 at 5:42 PM, <rod@hemiola.co.uk> wrote:
>
>>But I think you found a bug.
>
> Ok, so maybe the first ilock/iunlock pair isn't needed? The controller
> can't see the task descriptors that have been chained on to the
> endpoint until the "tail" element of the endpoint descriptor is set,
> so any potential interrupts during the sequence won't affect anything.
>
> rod
>
>
next prev parent reply other threads:[~2011-02-22 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 15:10 rod
2011-02-22 15:30 ` Francisco J Ballesteros
2011-02-22 16:42 ` rod
2011-02-22 16:50 ` Francisco J Ballesteros [this message]
2011-02-22 15:31 ` Philippe Anel
2011-02-22 15:45 ` Philippe Anel
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='AANLkTikP9hODfcrqKEJsJQx-HrksY=dWCvM+qDJ_iRje@mail.gmail.com' \
--to=nemo@lsub.org \
--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).