All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Matthias Geissert <matthias.geissert@web.de>,
	Greg KH <greg@kroah.com>, USB list <linux-usb@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Status of Bug 8094 -  ipaq oops on connecting "Vodafone VPA-II" ?
Date: Tue, 22 Sep 2009 01:03:34 +0200	[thread overview]
Message-ID: <4AB80646.6020008@imap.cc> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0909202152420.15304-100000@netrider.rowland.org>

[-- Attachment #1: Type: text/plain, Size: 2328 bytes --]

Am 21.09.2009 03:59 schrieb Alan Stern:
> Here's a patch which ought to fix the oops.  I trust it won't cause 
> any existing devices to start misbehaving.  Tilman and Matthias, please 
> verify that this works okay on your systems.

It does fix the oops for me. The lines:

ipaq 2-2:1.0: usb_probe_interface
ipaq 2-2:1.0: usb_probe_interface - got id
ipaq 2-2:1.0: PocketPC PDA converter detected

are now followed by

ipaq: probe of 2-2:1.0 failed with error -5

and I end up with only a single

usb 2-2: PocketPC PDA converter now attached to ttyUSB0

instead of two (ttyUSB0 and ttyUSB1) previously.

The device still doesn't work because now rndis_host (which without
the patch didn't even get a chance to look at the interface) complains:

rndis_host 2-2:1.0: usb_probe_interface
rndis_host 2-2:1.0: usb_probe_interface - got id
rndis_host: probe of 2-2:1.0 failed with error -16

But that's a different story which I'll investigate a bit further
on my own before (if necessary) starting a discussion here.

So from my point of view the patch is fine.

Thanks,
Tilman

> A better approach might be to test the bInterfaceClass value, but I 
> don't know if that would work; there might be some devices using a 
> strange value.
> 
> Alan Stern
> 
> 
> 
> Index: usb-2.6/drivers/usb/serial/ipaq.c
> ===================================================================
> --- usb-2.6.orig/drivers/usb/serial/ipaq.c
> +++ usb-2.6/drivers/usb/serial/ipaq.c
> @@ -966,6 +966,15 @@ static int ipaq_calc_num_ports(struct us
>  static int ipaq_startup(struct usb_serial *serial)
>  {
>  	dbg("%s", __func__);
> +
> +	/* Some of the devices in ipaq_id_table[] are composite, and we
> +	 * shouldn't bind to all the interfaces.  This test will rule out
> +	 * some obviously invalid possibilities.
> +	 */
> +	if (serial->num_bulk_in < serial->num_ports ||
> +			serial->num_bulk_out < serial->num_ports)
> +		return -ENODEV;
> +
>  	if (serial->dev->actconfig->desc.bConfigurationValue != 1) {
>  		/*
>  		 * FIXME: HP iPaq rx3715, possibly others, have 1 config that
> 

-- 
Tilman Schmidt                    E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

  reply	other threads:[~2009-09-21 23:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-20 13:39 Status of Bug 8094 - ipaq oops on connecting "Vodafone VPA-II" ? Tilman Schmidt
2009-09-20 15:05 ` Greg KH
2009-09-20 16:28   ` Tilman Schmidt
2009-09-20 16:37     ` Arjan van de Ven
2009-09-20 16:51       ` Tilman Schmidt
2009-09-20 17:32         ` Arjan van de Ven
2009-09-20 17:01   ` Tilman Schmidt
2009-09-20 21:13     ` Marcin Slusarz
2009-09-20 17:12   ` Alan Stern
2009-09-20 18:11     ` Greg KH
2009-09-21  1:59       ` Alan Stern
2009-09-21 23:03         ` Tilman Schmidt [this message]
2009-09-28 17:42         ` Status of Bug 8094 - ipaq oops on connecting "Vodafone VPA-II"? Matthias Geissert

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=4AB80646.6020008@imap.cc \
    --to=tilman@imap.cc \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=matthias.geissert@web.de \
    --cc=stern@rowland.harvard.edu \
    /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.