From: Greg KH <greg@kroah.com>
To: nardelli <jnardelli@infosciences.com>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] [PATCH] visor: Fix Oops on disconnect
Date: Fri, 21 May 2004 15:30:24 -0700 [thread overview]
Message-ID: <20040521223024.GA7399@kroah.com> (raw)
In-Reply-To: <40AE7CFE.5060805@infosciences.com>
On Fri, May 21, 2004 at 06:04:46PM -0400, nardelli wrote:
>
> Maybe I spoke too soon here. We have 1 bulk in, 2 bulk out, and 1 interrupt
> in endpoint, which by the logic in usb-serial, translates to 2 ports. Only
> one of those ports can have a read_urb associated with it, unless we want to
> do some really fancy juggling. This means that we're going to have a port
> that does not have a valid read_urb associated with it, even after open().
But the call to open() fails, which prevents any of the other tty calls
from happening on that port. That's why we don't need to make that
check anywhere else.
> I'm at a loss why this device has an uneven number of bulk in and bulk out
> endpoints.
Stupid hardware engineers? Who really knows...
thanks,
greg k-h
next prev parent reply other threads:[~2004-05-21 22:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 23:08 [PATCH] visor: Fix Oops on disconnect nardelli
2004-05-21 4:30 ` [linux-usb-devel] " Greg KH
2004-05-21 5:03 ` Pete Zaitcev
2004-05-21 14:52 ` nardelli
2004-05-21 14:48 ` nardelli
2004-05-21 15:05 ` Alan Stern
2004-05-21 17:08 ` nardelli
2004-05-21 15:41 ` Greg KH
2004-05-21 19:51 ` nardelli
2004-05-21 20:01 ` jkroon
2004-05-21 20:22 ` nardelli
2004-05-21 20:44 ` Greg KH
2004-05-21 21:44 ` nardelli
2004-05-21 21:56 ` Greg KH
2004-05-21 22:04 ` nardelli
2004-05-21 22:30 ` Greg KH [this message]
2004-05-24 17:20 ` nardelli
2004-05-24 19:38 ` nardelli
2004-05-24 20:06 ` Greg KH
2004-05-24 20:21 ` nardelli
2004-05-25 13:15 ` nardelli
2004-05-24 20:08 ` Greg KH
2004-05-24 21:42 ` nardelli
2004-05-25 18:30 ` Greg KH
2004-05-25 18:55 ` nardelli
2004-05-21 4:31 ` 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=20040521223024.GA7399@kroah.com \
--to=greg@kroah.com \
--cc=jnardelli@infosciences.com \
--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