linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Benton <andy@benton987.fsnet.co.uk>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10 and speedtouch usb
Date: Mon, 27 Dec 2004 15:48:13 +0000	[thread overview]
Message-ID: <41D02EBD.80600@benton987.fsnet.co.uk> (raw)
In-Reply-To: <200412271433.28454.zztchesmeli@echo.fr>

Serge Tchesmeli wrote:
> Le Lundi 27 Décembre 2004 14:25, Andrew Benton a écrit :
> 
>>Serge Tchesmeli wrote:
>>
>>>Hi,
>>>
>>>i have try the new kernel 2.6.10, compil with exactly the same option
>>>from my 2.6.9 (i have copied the .config) but i notice a high load on my
>>>machine, and i see that was syslogd.
>>>So, i look at my log and see:
>>>
>>>Dec 26 19:40:44 gateway last message repeated 137 times
>>>Dec 26 19:40:46 gateway kernel: usb 2-1: events/0 timed out on ep0in
>>>Dec 26 19:40:46 gateway kernel: SpeedTouch: Error -110 fetching device
>>>status Dec 26 19:40:46 gateway kernel: usb 2-1: modem_run timed out on
>>>ep0in Dec 26 19:40:46 gateway kernel: usb 2-1: usbfs: USBDEVFS_CONTROL
>>>failed cmd modem_run rqt 192 rq 18 len 8 ret -110
>>
>>Are you using the kernel or userspace driver?
> 
> 
> I'm using the kernel speedtouch driver.
> 
Well it looks like modem_run is giving you problems. If you want you could do 
without it and  let the kernel load the firmware itself. To try this you will 
need to  prepare the firmware by splitting it into two parts To do that you'll 
need a copy of the speedtouch-1.3.1 driver
http://prdownloads.sourceforge.net/speedtouch/speedtouch-1.3.1.tar.gz?download
untar it and cd into the speedtouch-1.3.1/src folder and then enter

gcc -o firmware firmware.c -DSTANDALONE_EXTRACTER

That will compile a binary called firmware. You can use that to split  the 
modems firmware into two parts. If (for example) the firmware is  called mgmt.o, 
copy it into the speedtouch-1.3.1/src folder and then enter

./firmware mgmt.o
mv boot.bin speedtch-1
mv firmware.bin speedtch-2

That will create two files, boot.bin and firmware.bin. Rename boot.bin  -> 
speedtch-1 and firmware.bin -> speedtch-2. Then you need to copy  these two 
speedtch files into hotplugs firmware folder. You can find  this by reading 
/etc/hotplug/firmware.agent

cat /etc/hotplug/firmware.agent | grep FIRMWARE_DIR=

Make sure you enabled hotplug firmware loading in your kernel config
CONFIG_FW_LOADER=y
and check that hotplug has this line in /etc/hotplug/usb.usermap

speedtouch 0x0003 0x06b9 0x4061 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00  0x00 
0x00000000

  reply	other threads:[~2004-12-27 15:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-27 10:08 2.6.10 and speedtouch usb Serge Tchesmeli
2004-12-27 13:25 ` Andrew Benton
2004-12-27 13:33   ` Serge Tchesmeli
2004-12-27 15:48     ` Andrew Benton [this message]
2004-12-27 16:03       ` Serge Tchesmeli
2004-12-29  9:11 ` Duncan Sands
2004-12-29 16:18 ` Roman Kagan
2004-12-30 12:00   ` Duncan Sands
2004-12-30 16:48     ` Serge Tchesmeli
2005-01-03 11:17     ` Serge Tchesmeli

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=41D02EBD.80600@benton987.fsnet.co.uk \
    --to=andy@benton987.fsnet.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).