On Tue, Jul 22, 2014 at 09:56:32AM -0400, Benjamin Romer wrote: > This patch adds a documentation file for all of the interfaces that were moved > to sysfs by the other patches in this set. > > Signed-off-by: Benjamin Romer <benjamin.ro...@unisys.com> > --- > v2: whitespace errors were corrected. > > .../Documentation/ABI/sysfs-platform-visorchipset | 74 > ++++++++++++++++++++++ > 1 file changed, 74 insertions(+) > create mode 100644 > drivers/staging/unisys/Documentation/ABI/sysfs-platform-visorchipset > > diff --git > a/drivers/staging/unisys/Documentation/ABI/sysfs-platform-visorchipset > b/drivers/staging/unisys/Documentation/ABI/sysfs-platform-visorchipset > new file mode 100644 > index 0000000..b6cad24 > --- /dev/null > +++ b/drivers/staging/unisys/Documentation/ABI/sysfs-platform-visorchipset > @@ -0,0 +1,74 @@ > +What: install/error > +Date: 7/18/2014 > +KernelVersion: TBD > +Contact: sparmaintai...@unisys.com > +Description: used to send the ID of a string that should be displayed on > + s-Par's automatic installation progress screen when an error > + is encountered during installation. This field has no effect > + if not in installation mode. > +Users: sparmaintai...@unisys.com > + > +What: install/remainingsteps > +Date: 7/18/2014 > +KernelVersion: TBD > +Contact: sparmaintai...@unisys.com > +Description: used to set the value of the progress bar on the s-Par automatic > + installation progress screen. This field has no effect if not in > + installation mode. > +Users: sparmaintai...@unisys.com > + > +What: install/textid > +Date: 7/18/2014 > +KernelVersion: TBD > +Contact: sparmaintai...@unisys.com > +Description: used to send the ID of a string that should be displayed on > + s-Par's automatic installation progress screen. Setting this > + field when not in installation mode (boottotool was set on > + the previous guest boot) has no effect. > +Users: sparmaintai...@unisys.com > + > +What: install/boottotool > +Date: 7/18/2014 > +KernelVersion: TBD > +Contact: sparmaintai...@unisys.com > +Description: The boottotool flag controls s-Par behavior on the next boot of > + this guest. Setting the flag will cause the guest to boot from > + the utility and installation image, which will use the value in > + the toolaction field to determine what operation is being > + requested. > +Users: sparmaintai...@unisys.com > + > +What: install/toolaction > +Date: 7/18/2014 > +KernelVersion: TBD > +Contact: sparmaintai...@unisys.com > +Description: This field is used to tell s-Par which type of recovery tool > + action to perform on the next guest boot-up. The meaning of the > + value is dependent on the type of installation software used to > + commission the guest. > +Users: sparmaintai...@unisys.com > + > +What: guest/chipsetready > +Date: 7/18/2014 > +KernelVersion: TBD > +Contact: sparmaintai...@unisys.com > +Description: This entry is used by Unisys application software on the guest > + to acknowledge completion of specific events for integration > + purposes, but these acknowledgements are not required for the > + guest to operate correctly. > +Users: sparmaintai...@unisys.com
What is the format of the chipsetready file? It looks like you want to write 2 values to it? Please describe it better, for all of these. thanks, greg k-h _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
