From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug scripts for ieee1394
Date: Sun, 16 Sep 2001 20:10:33 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100067297431024@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100066152014337@msgid-missing>
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.
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.
> It's looking like it's time for another linux-hotplug release, does
> anyone have any outstanding issues that need to be addressed before I
> make another release?
I finally got around to integrating a bunch of the fixes from SuSE,
though not all of them. It would be good to have the scripts sense
whether they're running on a RedHat-ish system or SuSE one, and
use the appropriate style admin scripts for (a) hotplug options, and
(b) network administration. (Best to have distros agree more on
such stuff, but that's a bit out of scope for me ... :)
Unless someone else wants to volunteer to address those issues
in the near future, I think it's a fine time to release. This one will
have the "fxload" utility (hotplugging can load EZ-USB FX/FX2
firmware), some of the SuSE support, bugfixes, IEEE1394, and
stuff I've forgotten ... should be interesting! :)
- Dave
_______________________________________________
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
next prev parent reply other threads:[~2001-09-16 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-16 17:29 Hotplug scripts for ieee1394 Kristian Hogsberg
2001-09-16 18:33 ` Greg KH
2001-09-16 20:10 ` David Brownell [this message]
2001-09-16 21:32 ` Kristian Hogsberg
2001-09-16 21:39 ` David Brownell
2001-09-16 21:47 ` David Brownell
2001-09-16 22:33 ` Ben Collins
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=marc-linux-hotplug-100067297431024@msgid-missing \
--to=david-b@pacbell.net \
--cc=linux-hotplug@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).