From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Kay Sievers" <kay.sievers@vrfy.org>
Date: Thu, 09 Oct 2008 09:43:31 +0000
Subject: Re: why kernel not call /sbin/hotplug ?
Message-Id: <ac3eb2510810090243v6ef8673ayb7b225d63f6ca36b@mail.gmail.com>
List-Id: <linux-hotplug.vger.kernel.org>
References: <d30f40a80810090225t4a0d7070y9271848324988837@mail.gmail.com>
In-Reply-To: <d30f40a80810090225t4a0d7070y9271848324988837@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
To: linux-hotplug@vger.kernel.org

On Thu, Oct 9, 2008 at 11:25 AM, Grzegorz Heldt
<grzegorz.heldt@gmail.com> wrote:

> I have embedded system based on sh4-cpu with kernel 2.6.17.14.  I have
> build latest rt73.ko module which is usb-wifi driver. This driver also
> need firmware to be loaded into device during initialization.
>
> Basing on information that I found, i put following script in /sbin/hotpl=
ug:
>
> #cat /sbin/hotplug
> #!/bin/sh
> echo hotplug script is runned !
>
> HOTPLUG_FW_DIR=3D/lib/firmware/
>
>                echo 1 > /sys/$DEVPATH/loading
>                cat $HOTPLUG_FW_DIR/$FIRMWARE > /sysfs/$DEVPATH/data

/sysfs/... ?

And do not use echo on stdout, kernel forked process don't have that,
and also check for $ACTION=ADd.

Kay