From: Duncan Sands <duncan.sands@math.u-psud.fr>
To: mikie <mikie.pl@gmail.com>
Cc: "Indan Zupancic" <indan@nul.nu>,
"Kay Sievers" <kay.sievers@vrfy.org>,
linux-kernel@vger.kernel.org
Subject: Re: understanding firmware loader for speedtouch (kernel 2.6.21.5)
Date: Wed, 11 Jul 2007 14:33:32 +0200 [thread overview]
Message-ID: <200707111433.33156.duncan.sands@math.u-psud.fr> (raw)
In-Reply-To: <ca35ce500707110422j73c5c256i384327c652b7ccba@mail.gmail.com>
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.
next prev parent reply other threads:[~2007-07-11 12:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 12:54 mikie
2007-07-06 14:20 ` Duncan Sands
2007-07-06 19:16 ` Indan Zupancic
2007-07-09 8:49 ` mikie
2007-07-09 10:42 ` Indan Zupancic
2007-07-09 11:08 ` mikie
2007-07-09 13:59 ` Kay Sievers
2007-07-09 14:40 ` mikie
2007-07-09 15:03 ` Indan Zupancic
2007-07-09 17:00 ` mikie
[not found] ` <200707091923.38577.duncan.sands@math.u-psud.fr>
2007-07-09 17:41 ` mikie
2007-07-09 17:51 ` Duncan Sands
2007-07-10 7:54 ` mikie
2007-07-10 8:57 ` Duncan Sands
2007-07-10 9:13 ` mikie
2007-07-10 9:32 ` Duncan Sands
2007-07-10 10:32 ` mikie
2007-07-11 11:22 ` mikie
2007-07-11 12:33 ` Duncan Sands [this message]
2007-07-11 12:47 ` mikie
2007-07-11 13:07 ` Duncan Sands
2007-07-11 16:55 ` mikie
2007-07-19 10:24 ` mikie
2007-07-24 23:03 ` Duncan Sands
2008-11-19 12:25 ` mikie
2008-11-19 12:49 ` Duncan Sands
2007-07-09 15:08 ` Kay Sievers
2007-07-09 10:50 ` Duncan Sands
2007-07-09 11:06 ` mikie
[not found] ` <ca35ce500707061006k74754bd6m8a9d2f1cb2910823@mail.gmail.com>
[not found] ` <200707061924.57099.duncan.sands@math.u-psud.fr>
2007-07-06 19:30 ` mikie
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=200707111433.33156.duncan.sands@math.u-psud.fr \
--to=duncan.sands@math.u-psud.fr \
--cc=indan@nul.nu \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikie.pl@gmail.com \
/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®