From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sat, 26 Feb 2005 13:11:08 +0000 Subject: Re: event sequencing Message-Id: <1109423468.7400.39.camel@localhost.localdomain> List-Id: References: <9e473391050225081838f673c7@mail.gmail.com> In-Reply-To: <9e473391050225081838f673c7@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Sat, 2005-02-26 at 01:25 -0500, Jon Smirl wrote: >On Fri, 25 Feb 2005 21:35:37 -0800, Greg KH wrote: >> Hm, I don't think the kernel knows about a "monitor", just a fb device. >> Right Jon? > >Correct. > >Current changes are under way to make one fb device per head. I could >make a sysfs monitor entry but you would not want a class_device since >there is no major and /dev device for monitors. The reason I'm asking is that it's always nice if userspace can read the current device state from sysfs at any time and not only at event time. Stuff like HAL heavily depends on that as it needs to get the initial state of all devices at startup to present this to applications. But if there is any other way to get that without sysfs, it would work too, sure. Thanks, Kay ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&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