From: Harald Welte <laforge@gnumonks.org>
To: David Brownell <david-b@pacbell.net>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: [BUG] oops while completing async USB via usbdevio
Date: Wed, 1 Jun 2005 00:12:58 +0200 [thread overview]
Message-ID: <20050531221258.GI29780@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <200505311153.24747.david-b@pacbell.net>
[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]
On Tue, May 31, 2005 at 11:53:24AM -0700, David Brownell wrote:
> I'm still hoping that one of the folk who want make an interesting and
> useful contribution to Linux will take the hint. It goes slowly. :)
I've pondered about three times whether to start or not. I'd rather
not, since I'm already having problems keeping up with all my other
projects :(
> > meanwhile, the current usbfs aio handling is the only way how to deal
> > with delivery of interrupt pipe URB's to userspace drivers.
>
> Other than tying up the file descriptor with a blocking read, that is.
you're probably using that same file descriptor for reading/writing
from/to bulk endpoints at the same time. I don't see how a 'blocking
read' would help.
> > Wouldn't it help to associate the URB with the file (instaed of the
> > task), and then send the signal to any task that still has opened the
> > file? I'm willing to hack up a patch, if this is considered a sane fix.
>
> Sounds reasonable, except that not all such tasks will want the signal.
> Though I guess the infrastructure to filter the signal out already exists,
> so the main missing piece is that urb-to-file binding.
Ok, I'll get something coded shortly.
--
- Harald Welte <laforge@gnumonks.org> http://gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-31 22:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 19:44 Harald Welte
2005-05-30 21:26 ` Harald Welte
2005-05-30 22:55 ` [linux-usb-devel] " David Brownell
2005-05-30 23:09 ` Oliver Neukum
2005-05-30 23:12 ` David Brownell
2005-05-31 8:04 ` Harald Welte
2005-05-31 8:48 ` Harald Welte
2005-05-31 11:45 ` Oliver Neukum
2005-05-31 18:53 ` David Brownell
2005-05-31 22:12 ` Harald Welte [this message]
2005-06-06 16:05 ` Harald Welte
2005-06-06 16:24 ` Alan Stern
2005-06-06 16:50 ` Harald Welte
2005-05-30 23:07 ` Oliver Neukum
2005-05-31 8:06 ` Harald Welte
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=20050531221258.GI29780@sunbeam.de.gnumonks.org \
--to=laforge@gnumonks.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.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
all inboxes | Powered by JetHome®