From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug-- who notifies whom of what?
Date: Tue, 17 Feb 2004 17:28:56 +0000 [thread overview]
Message-ID: <20040217172855.GC13363@kroah.com> (raw)
In-Reply-To: <40316638.9060501@earthlink.net>
On Tue, Feb 17, 2004 at 09:34:30AM -0600, Bryan W. Headley wrote:
> Greg KH wrote:
> >On Mon, Feb 16, 2004 at 06:54:16PM -0600, Bryan W. Headley wrote:
> >
> >>Greg,
> >>
> >>Regards to Aiptek USB tablets...
> >>
> >>I'm trying to figure out a strategy for hotplugging.
> >>
> >>1) The tablet is mapped to the input device system.
> >> a) Because the order in which drivers complete loading/registering
> >> is not deterministic (e.g., mouse driver spawns thread), I do not
> >> know with certainty that the tablet will always be mapped to
> >> /dev/input/event27. So, configuration files of certain (XFree)
> >> applications that require that the path be known and static enough
> >> to put in a text file.
> >
> >
> >Use udev to always create your "/dev/input/tablet_mine_all_mine" node so
> >that XFree does not have to be reconfigured all the time.
>
> What do I do in 2.4-land? The silliness with hotplug scripts, .rc
> scripts, etc.?
I don't really know, sorry. Luckily I'm not running 2.4 on any of my
machines :)
Anyone else have an idea?
thanks,
greg k-h
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
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
prev parent reply other threads:[~2004-02-17 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 0:54 Hotplug-- who notifies whom of what? Bryan W. Headley
2004-02-17 1:39 ` Greg KH
2004-02-17 17:28 ` Greg KH [this message]
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=20040217172855.GC13363@kroah.com \
--to=greg@kroah.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 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).