From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Tue, 01 Mar 2005 08:41:48 +0000 Subject: Re: event sequencing Message-Id: <20050301084148.GB4243@kroah.com> 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 Tue, Mar 01, 2005 at 03:30:37AM -0500, Jon Smirl wrote: > On Tue, 1 Mar 2005 00:01:43 -0800, Greg KH wrote: > > Anyway, let's do this properly, it's on the todo list, and will get done > > in a few weeks. > > I'll add notes in my fbdev patches that the class_device child code is > temporary and waiting on a real fix. That's fine with me. > I'm changing the driver design to assume that I can do this. This > eliminates the need for a MODE_CHANGE event type. It makes more sense > looking at the sysfs entries too. > > sys > class > graphics > fb0(mode_list, mode) > monitor(edid) > fb1(mode_list, mode) > monitor(edid) > > If you unplug the monitor the monitor directory disappears and the > mode_list goes empty. The framebuffer is still there. Plug is back in > and the monitor directory is created and we get the hotplug event. > Hotplug event rebuilds the valid mode_list. Oooh, that will be nice, I like it a lot. Ok, that gives me an extra incentive to get this stuff working, let's see if I can get some free time this week... thanks, greg k-h ------------------------------------------------------- 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