On Tue, Aug 30, 2011 at 03:14:12AM -0400, Jean Delvare wrote: > On Mon, 29 Aug 2011 22:57:56 -0700, Guenter Roeck wrote: > > The chips supported by the max16065 driver should not be accessed using direct > > i2ctools commands. Add warning to driver documentation to alert users. > > > > Signed-off-by: Guenter Roeck <guenter.roeck@xxxxxxxxxxxx> > > --- > > RFC: Do we want this kind of warning in driver documentation ? > > Sure, this can't hurt. Maybe we could add a section in i2c-tools' > documentation as well, listing the dangerous chips, starting with this > one? i2cdetect already has a note about the AT24RF08 for historical > reasons, I wouldn't mind documenting the "dangerous" chips more > prominently. Hopefully the list will stay short. > Hopefully yes. Many of the PMBus chips are potentially affected, though. They typically have a means to protect settings from overwrite, but if that is not enabled, one can be in hot water. Worst I have seen so far was to execute i2cdump on an eval board and it lost its configuration :(. [ ... ] > > Acked-by: Jean Delvare <khali@xxxxxxxxxxxx> > Thanks for the review! Guenter _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
