From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755939AbXGIKmm (ORCPT ); Mon, 9 Jul 2007 06:42:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752063AbXGIKme (ORCPT ); Mon, 9 Jul 2007 06:42:34 -0400 Received: from neon.samage.net ([85.17.153.66]:47473 "EHLO neon.samage.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751315AbXGIKmd (ORCPT ); Mon, 9 Jul 2007 06:42:33 -0400 Message-ID: <59741.81.207.0.53.1183977750.squirrel@secure.samage.net> In-Reply-To: References: <200707061620.44348.duncan.sands@math.u-psud.fr> <58019.81.207.0.53.1183749400.squirrel@secure.samage.net> Date: Mon, 9 Jul 2007 12:42:30 +0200 (CEST) Subject: Re: understanding firmware loader for speedtouch (kernel 2.6.21.5) From: "Indan Zupancic" To: "mikie" Cc: "Duncan Sands" , linux-kernel@vger.kernel.org User-Agent: SquirrelMail/1.4.8 MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Spam-Score: -1.8 X-Scan-Signature: 8b3222cd26cce149ddb9ffa05c4da76e Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, July 9, 2007 10:49, mikie wrote: > 2007/7/6, Indan Zupancic : >> On Fri, July 6, 2007 16:20, Duncan Sands wrote: >> > On Friday 6 July 2007 14:54:18 mikie wrote: >> >> 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 ? >> > >> > It loads it itself, using some external software! >> >> For information, it generates a hotplug event and the kernel calls the >> program written at /proc/sys/kernel/hotplug with certain information. >> That used to be /sbin/hotplug, became later udev, but today in general >> udev reads the uevents generated by the kernel. > > On my system the /proc/sys/kernel/hotplug points to /sbin/hotplug. > I copied your script to /sbin/hotplug and also added simple logging, > so I can see whenever the script is being started. It turns out that > the script is not started at all by the kernel... > > I am afraid that the kernel generates uevents only, could this be true? Not really, it would break backward compatibility, and if it were true, they're remove the /proc/sys/kernel/hotplug setting too. As far as I know, if it's set, that program will be executed, and if zero is written to it, only uevents are generated. Make sure that the script is executable (chmod +x) and has "#!/bin/sh" at the top, or else it won't work. If that's already the case, I've no idea. Good luck, Indan