linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <ca35ce500707060554v71ebdca3k8ef18e4c0a44c9cb@mail.gmail.com>
Date:	Fri, 6 Jul 2007 14:54:18 +0200
From:	mikie <mikie.pl@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: understanding firmware loader for speedtouch (kernel 2.6.21.5)

Hi,

I experience some problems with the speedtch.c module, especially in
regards to its firmware loader.
I am not quite sure if this module is going to load the firmware
itself or does it use some external software to do that ?

All I get is :

Jul  6 13:41:37 srv kernel: speedtch 1-2:1.0: speedtch_find_firmware:
looking for speedtch-1.bin.2.00
[...]
Jul  6 13:42:19 srv kernel: speedtch 1-2:1.0: speedtch_find_firmware:
looking for speedtch-1.bin.2
[...]
Jul  6 13:43:19 srv kernel: speedtch 1-2:1.0: speedtch_find_firmware:
looking for speedtch-1.bin

And nothing more happens. The firmware does not get loaded to the
modem. There is also no information in the logs that the firmware
loading failed...

It is worth noting that I use slackware distro, that was installed
long time ago with 8.1 (or 9.0) CD version, and I only make package
upgrades. I used to work with kernel 2.4.33.3 (I compile the kernel
myself), but now decided I switch to the new 2.6 series. The old
distro means that I do not use hotplug nor udevd in my system (and
would like to stick with that scenario, if possible).

I have read and checked the firmware.agent script from some hotplug
package, and noticed that it makes something like simple file copy of
the firmware to the "data" and echoing 1 or 0 to the "loading" file.
But what is the location of these data/loading ? Also the firmware is
split into 2 parts -- should I upload them one after another? Is that
all that should be done to get the firmware loaded?

Regards,
MK
-
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/