linux-kernel - Re: understanding firmware loader for speedtouch (kernel 2.6.21.5)

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]

Message-Id: <200707111433.33156.duncan.sands@math.u-psud.fr>
Date:	Wed, 11 Jul 2007 14:33:32 +0200
From:	Duncan Sands <duncan.sands@...h.u-psud.fr>
To:	mikie <mikie.pl@...il.com>
Cc:	"Indan Zupancic" <indan@....nu>,
	"Kay Sievers" <kay.sievers@...y.org>, linux-kernel@...r.kernel.org
Subject: Re: understanding firmware loader for speedtouch (kernel 2.6.21.5)

Hi Mikie,

> I begin to think that the isochronous mode is not working. I tried the
> speedtch module with disabled and enabled isoc and there is no
> difference in transfer speeds at all.
> 
> All I checked was :
> root@srv:~# cat /sys/module/speedtch/parameters/enable_isoc
> Y
> 
> which as I now believe only means what options have been specified,
> but does not confirm the actual mode being in use.
> Especially that I do not see anything like "isoc support enabled" in
> any of the logs.
> 
> Are there any requirements for UHCI hardware to support isoc mode  ?
> Mine is:
> USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> Controller (rev 08) (prog-if 00 [UHCI])
> 
> Or maybe I am missing something else? I am sure the isoc mode is
> supported by my modem, now I only have doubts if my hardware on server
> box supports this ?

can you please send the part of /proc/bus/usb/devices concerning the
modem, while the modem is plugged in and (supposedly) using isoc mode.
If /proc/bus/usb isn't mounted, you can mount it like this IIRC:
	mount -t usbfs usbfs /proc/bus/usb/
Also, looking in the driver I see that if isoc mode is disabled you
should see one of the following messages:
	- setting interface to ?? failed (??)!
	- isochronous transfer not supported - using bulk
The first one may be a debug message, so you will not necessarily see
it depend on which level of kernel debug messages you have turned on.
(I have made some changes in my tree so that if you asked for isoc
transfer but get bulk then a message is printed).

Ciao,

Duncan.
-
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/