From: Pete Zaitcev <zaitcev@redhat.com>
To: Duncan Sands <baldrick@free.fr>
Cc: marcelo.tosatti@cyclades.com, linux-kernel@vger.kernel.org
Subject: Re: USB 2.4.30: fix modem_run
Date: Thu, 3 Mar 2005 23:52:52 -0800 [thread overview]
Message-ID: <20050303235252.6b0dc51b@localhost.localdomain> (raw)
In-Reply-To: <1108116980.7400.0.camel@localhost.localdomain>
On Fri, 11 Feb 2005 11:16:20 +0100 Duncan Sands <baldrick@free.fr>
wrote:
> On Thu, 2005-02-10 at 16:11 -0800, Pete Zaitcev wrote:
> > I entered a patch which adds "exclusive_access" lock into 2.4.29,
> > to fix devices which cannot handle simultaneous accesses. This
> > caused a regression with European ADSL modems. An ioctl
> > USBDEVFS_REAPURB allows a process to enter the kernel and wait for
> > USB I/O to finish. Naturally, this should not take
> > exclusive_access, or nothing will ever finish.
>
> How does this compare with the locking in 2.6 kernels?
In 2.6, there is no locking whatsoever. Instead, rules for queueing are
relaxed for all HCs. If the device chokes when it receives a control
together with a data exchange (on a bulk endpoint, usually), kernel
does not interfere. Users (libusb & drivers) are supposed to know when
not to do it. Obviously, it's not the case of usb-storage. To help that,
descriptor strings are cached in latest Greg's trees, since a week ago
or so. This way at least "cat /proc/bus/usb/devices" won't interfere.
-- Pete
prev parent reply other threads:[~2005-03-04 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 0:11 USB 2.4.30: fix modem_run Pete Zaitcev
2005-02-11 10:16 ` Duncan Sands
2005-03-04 7:52 ` Pete Zaitcev [this message]
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=20050303235252.6b0dc51b@localhost.localdomain \
--to=zaitcev@redhat.com \
--cc=baldrick@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.