On Tue, Sep 27, 2016 at 02:42:22PM -0400, David Kershner wrote: > From: Tim Sell <timothy.s...@unisys.com> > > Previously, the lines describing devices controlled by the visorinput, > visornic, and visorhba drivers (keyboard, mouse, ultravnic, sparvhba) would > be missing from the vbus channel header. This is important info that is > collected as part of s-Par livedumps, and can be examined via > /sys/bus/visorbus/devices/visorbus<n>/client_bus_info, e.g.: > > $ pwd > /sys/bus/visorbus/devices > $ cat visorbus1/client_bus_info > Client device / client driver info for s-Par Console eartition > (vbus #4294967295): > chipset visorchipset kernel ver. 4.8.0-rc6-ARCH+ > clientbus visorbus kernel ver. 4.8.0-rc6-ARCH+ > -> [2]keyboard visorinput kernel ver. 4.8.0-rc6-ARCH+ > -> [3]mouse visorinput kernel ver. 4.8.0-rc6-ARCH+ > > $ cat visorbus2/client_bus_info > Client device / client driver info for s-Par IOVM eartition > (vbus #4294967295): > chipset visorchipset kernel ver. 4.8.0-rc6-ARCH+ > clientbus visorbus kernel ver. 4.8.0-rc6-ARCH+ > -> [0]ultravnic visornic kernel ver. 4.8.0-rc6-ARCH+ > -> [1]ultravnic visornic kernel ver. 4.8.0-rc6-ARCH+ > -> [2]sparvhba visorhba kernel ver. 4.8.0-rc6-ARCH+
You do realize that sysfs files are supposed to only be "one value per file", right? This is going to have to change soon, if you want this code out of staging. I'll take these patches now, but please work on a sane API (this really looks like something for debugfs as no userspace tools should be relying on it...) thanks, greg k-h _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
