On Tue, Feb 05, 2013 at 09:13:01PM +0100, Mark Kettenis wrote: > > Date: Mon, 4 Feb 2013 08:17:26 +1000 > > From: Peter Hutterer <[email protected]> > > > > On Fri, Feb 01, 2013 at 11:09:41AM +0100, Mark Kettenis wrote: > > > > Date: Fri, 1 Feb 2013 09:20:38 +1000 > > > > From: Peter Hutterer <[email protected]> > > > > > > > > If both are missing, input device hotplugging will not work out of the > > > > box. > > > > While we still have a DBus-API or the user may want to set AAD off all > > > > the > > > > time, the most likely source of this is misconfiguration (i.e. lack of > > > > the > > > > udev/hal devel packages). > > > > > > > > Message printed last to make it more obvious to the user. > > > > > > But the check is pretty much Linux-specific. On OpenBSD you'll get > > > (basic) input device hotplug capability through wscons (which is > > > always available). > > > > is this actual X hotplugging support or just the kernel multiplexing, > > similar to /dev/input/mice? > > Probably more like the latter. Still printng such a warning on > OpenBSD (or anything else hat isn't Linux?) seems inappropriate and is > likely to confuse people.
yes, but that's a general drawback of the term being overloaded. We've had the same basic input hotplugging in the Linux kernel well before X hotplugging. X-based hotplugging has only been around since server 1.4. And wscons is _not_ hotplugging. The server only sees one set of devices, with (presumably) no device-specific data. This is not hotplugging, it's the same behaviour that you get when you explicitly turn hotplugging off in the server, or when udev/hal isn't found on Linux. Cheers, Peter _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
