lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 7 Jul 2008 20:16:02 +0200
From:	Matthias Geissert <matthias.geissert@....de>
To:	Oliver Neukum <oliver@...kum.org>
Cc:	Adrian Bunk <bunk@...nel.org>,
	Adam Williamson <awilliamson@...driva.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Arjan van de Ven <arjan@...radead.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Alan Cox <alan@...hat.com>, bugme-daemon@...zilla.kernel.org,
	Greg KH <greg@...ah.com>, linux-usb@...r.kernel.org
Subject: Re: [Bug 10868] Oops on loading ipaq module since 2.6.26, prevents use of device

Am Donnerstag, 3. Juli 2008 16:08:44 schrieb Oliver Neukum:


> >  	.num_interrupt_in =	NUM_DONT_CARE,
> > -	.num_bulk_in =		1,
> > -	.num_bulk_out =		1,
> > -	.num_ports =		1,
> > +	.num_bulk_in =		NUM_DONT_CARE,
> > +	.num_bulk_out =		NUM_DONT_CARE,
>
> This is good.
>
> > +	.num_ports =		2,
>
> This is fatal.

I checked what you said with kernel 2.6.26 rc9.  I set num_ports to 5. It 
worked quite well until I tried to connect to a non-existing endpoint. 

However, the problem is that the Yakumo Delta needs to connect to the 2nd 
endpoint. You can connect to the first one but you don't get any data. 

Is there any good way to tell the ipaq driver to use the 2nd endpoint? Maybe 
one could provide a different struct usb_serial_driver ipaq_device depending 
on the usb id or an option which tells the driver to use 2 endpoints.

Regards,
matthias  
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ