From: Stefan Schweizer <sschweizer@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Run hotplug scripts after device node is created?
Date: Mon, 22 Aug 2005 21:23:44 +0000 [thread overview]
Message-ID: <e796392205082214236030a3ae@mail.gmail.com> (raw)
In-Reply-To: <e796392205082213456c05e1b@mail.gmail.com>
On 8/22/05, Kay Sievers <kay.sievers@vrfy.org> wrote:
> On Mon, Aug 22, 2005 at 10:45:49PM +0200, Stefan Schweizer wrote:
> > I use a hotplug script to download the firmware to my hp printer. This
> > is needed for HP Laserjet 1000,1005 and 1020. The procedure is just
> > cat firmware > /dev/usb/lp*
> >
> > The problem is that /dev/usb/lp* has to exist for the script to work.
> > In earlier udev versions I just added "sleep 20" to the script to be
> > sure that the device node exists. With the last version of udev this
> > seems to be no longer possiblee because udev waits for the hotplug
> > script to exit before creating the device node :(
>
> No, only PROGRAM and IMPORT runs before the node is created.
>
> > How can I make sure that the hotplug script is run after usblp is
> > loaded and after the device is created?
>
> RUN runs definitely after the node handling is finished.
>
I don't use either of those ..
this is just a plain old hotplug script with
/etc/hotplug/usb/hplj.usermap:
hplj1005 0x0003 0x03f0 0x1317 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000
/etc/hotplug/usb/hplj1005
waiting and catting the firmware into the device node.
> > Is there some hotplug-way to find out which device-node I am supposed
> > to load the firmware into?
>
> Don't understand the question.
currently the script is scanning all devices for a supported one .. is
there some variable in a hotplug script to read out the device node?
> And what udev version is it?
udev-068
> What does:
> cat /proc/sys/kernel/hotplug
> print?
/sbin/udevsend
thanks,
Stefan
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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:[~2005-08-22 21:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 20:45 Run hotplug scripts after device node is created? Stefan Schweizer
2005-08-22 21:15 ` Kay Sievers
2005-08-22 21:23 ` Stefan Schweizer [this message]
2005-08-22 21:46 ` Marco d'Itri
2005-08-22 21:48 ` Kay Sievers
2005-08-23 5:26 ` Stefan Schweizer
2005-08-23 5:29 ` Stefan Schweizer
2005-08-23 7:54 ` Marco d'Itri
2005-08-23 11:32 ` Olivier Blin
2005-08-23 12:27 ` Marco d'Itri
2005-08-23 13:39 ` Sergey Vlasov
2005-08-23 14:10 ` Olivier Blin
2005-08-23 18:25 ` Stefan Schweizer
2005-08-23 19:25 ` Kay Sievers
2005-08-23 21:34 ` Stefan Schweizer
2005-08-23 21:52 ` Marco d'Itri
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=e796392205082214236030a3ae@mail.gmail.com \
--to=sschweizer@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.