On 19/12/16 10:29 AM, Keith Busch wrote: > Since the in-kernel driver binds to the device, won't this driver > conflict with the initialization the in-kernel one already does? Bus > master, MSI setup, etc? No. The management interface is on a completely separate PCI endpoint. So from the kernels perspective, the management interface is just another PCI device. It has the same vendor and device ID as the switch but uses separate class codes so it can be bound by an independent driver. > Could you also provide the reasoning against making the functionality > this driver provides in user space? I'm not sure how you mean. I suppose we could write a UIO driver but that seemed like an ugly solution to me and doesn't seem like an approach the community prefers. We do have to make use of interrupts so simply using /sys/bus/pci/.../resourceN wouldn't work either. Logan -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
