Hello Bjorn, >> >> I think our handling of slot capabilities and control is a bit >> haphazard. It seems like we're mostly responding to things that >> break, and we don't really have a coherent explanation of how things >> *should* work in different configurations. I think it would be good >> if somebody wrote up something for Documentation/PCI, with references >> to the relevant specifications, that describes how we think things >> should work. > > Sure, I think I'll take a stab. > > Thanks, > > Rajat > >> For example, I think we have at least four models: >> >> 1) ExpressCard >> 2) Slots with attention button >> 3) Slots with no button where we expect a software UI, e.g., Taku's box >> 4) Devices with no actual slot, no button, etc., e.g., Rajat's system >> I'm trying to come up with a write up for this. And am trying to understand what differentiates (1) from others - from the view of use case model of course. I briefly looked at the ExpressCard specs at http://www.usb.org/developers/expresscard/EC_specifications/ExpressCard_2_0_FINAL.pdf I understand that ExpressCard shall be an actual slot and of course has a defined form factor etc, but, when I think of the _use case_ that the user is expected to follow, it shall be pretty much dependent on the HP elements. For e.g, if there is attention button, it would follow (2), but if link comes up automatically (no power controller etc), then it would follow (4) etc. Thus I think that the use cases (sequence to be followed for hotplug) shall be more appropriately categorized based on what hot-plug elements (button etc) are present in a system. Of course, we can give examples ("ExpressCards are one example in this category and is typically characterized by .. ") within those categories, while also making references to the appropriate standards. What do you think? Thanks, Rajat -- 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
