Hi all, > As far as Chassis Intrusion (CI) goes, I've coerced an unused IN > limit for time being as all I need is a write-only trigger event. This is no good. We made the interface such that user-space can guess what any chip does and how to access it without any chip-specific knowledge. If you implement chassis intrusion, please make it a separate file with a dedicated, explicit name. Thanks, -- Jean Delvare
