Starting the phosphor-hwmon service from udev rules
Andrew Jeffery
andrew at aj.id.au
Wed Nov 30 12:14:16 AEDT 2016
On Tue, 2016-11-29 at 10:30 -0600, Matt Spinler wrote:
> Another issue I have is if the MRW should have the knowledge of if a
> device has a hwmon driver or not? While it would make things a lot
> more simple if it did, I'm not sure if it's in its domain. If it
> doesn't, then it would either still generate rules and unit files for
> every I2C device and some just wouldn't get used
This seems reasonable to me. That way as hwmon drivers are added to the
kernel we have no extra work to do to enable the devices, and we don't
have work to do to keep a list of disabled devices.
The "extra" cruft is a problem if we're running out of space, but I
doubt udev rules and systemd unit files are going to be our first
concern there.
Andrew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20161130/bfc1ce72/attachment-0001.sig>
More information about the openbmc
mailing list