On Tue, Mar 24, 2009 at 06:40:56PM +0900, Taku Izumi wrote: > > > The reason I'm asking is because, if you're looking to get a > > uevent emitted when the attention button is pressed or the MRL is > > opened, well... why do you need it? The operator knows he pressed > > the button or opened the latch. > > > > So I'm confused as to why software would need to know about these > > physical events. > > > > I think the sysfs operation for hotplug is not very nice, so I want to make > the hotplug management utility. The utility that I have in mind has abilities > - to display slots' status (power, latch, ...) > - to show and record hotplug event log > - to perform hotplug operations > - to show hotplug procedure automatically when the attention button is pressed. > and so on. I think the event notification is variously useful... > Is it unnecessary? Possibly, yes. You can do all of the above without the uevents being sent from the kernel today, right? And, if the uevents are sent, udev will eat them up, how will your application get access to them? Have you created new udev rules and/or HAL code to emit those events to dbus properly? Don't just add events from the kernel unless you have some code that uses them :) thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
