From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kristian Hogsberg Date: Sun, 16 Sep 2001 21:32:08 +0000 Subject: Re: Hotplug scripts for ieee1394 Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org David Brownell writes: > Way cool! > > > I just added it to cvs, thanks a lot for doing this! > > You barely beat me to it ... :) > > I added a couple things to this. The LABEL variable wasn't set, which > meant that "no such driver" diagnostics wouldn't be helpful. I added > the ": case $expected $actual" statements to the match logic, so that > it's easier to use "sh -x" to debug things (as it is for the other agents). > And also tweaked the doc a little, so it's clear that 2.4.10 and the right > modutils are needed, and there's a HISTORY section. Nice, I knew I must have missed some details -- I'm not too familiar with those shell-script details... > Is there something that addresses the "cold-plugging" (boot time) init > of ieee1394/firewire/i-link/... devices, like the "usbmodules" command? > > * Scenario: firewire driver is statically linked, device is > connected at boot time, but hotplugging won't behave since > filesystems aren't ready yet. > * Solution: a /etc/hotplug/ieee1394.rc script that scans the bus and > issues fake hotplug events for those devices. > > There could be other solutions of course. Currently there is no such mechanism, the ieee1394 subsystem maintains no /proc entries at the moment. I'd like to add it eventually, but currently it can't be supported easily. Kristian _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel