What does this mean?
I wanted to have a configure option that allows you to point at:
/foo/fakesysfs/hwmon/hwmonx
instead of the real one.
Then we can actually run hwmon instances in qemu.
If this is for qemu, a better solution would be to add a device that has a hwmon driver to the model.
@legoater @amboar any suggestions?
For that to be "better" it would need to be the default qemu model that comes with Yocto, preferably both the arm and x86 models as I know those are two models most (userspace) devs run.
Or, if we can figure out how to change the default model to something more appropriate to our distro that would work too.
@bradbishop @kc8apf opened an issue recently about migrating our yocto setup to use the aspeed qemu models. Yocto have improved their handling of qemu, so it should be a matter of writing some configuration files.
Yeah. We should get them using the machine that we've spent the past year working on
And we can write more model for sensors. These are easy to write when the logic is just a question of getting and setting values from the QEMU monitor. see https://github.com/openbmc/qemu/commit/1fa5a71977c8806fa374600af27bee4f4b240bf6 for that.
This issue has been automatically marked as stale because no activity has occurred in the last 6 months. It will be closed if no activity occurs in the next 30 days. If this issue should not be closed please add a comment. Thank you for your understanding and contributions.
Closing this, as it's morphed into two separate problems: Implementing hwmon models and integrating our machines into yocto.
Most helpful comment
Yeah. We should get them using the machine that we've spent the past year working on