On 07/26/2016 05:26 AM, Sathya Perla wrote:
-Original Message-
From: Guilherme G. Piccoli [mailto:gpicc...@linux.vnet.ibm.com]
On 07/25/2016 07:48 AM, Sathya Perla wrote:
-Original Message-
From: Guilherme G. Piccoli [mailto:gpicc...@linux.vnet.ibm.com]
Temperature values on be
> -Original Message-
> From: Guilherme G. Piccoli [mailto:gpicc...@linux.vnet.ibm.com]
>
> On 07/25/2016 07:48 AM, Sathya Perla wrote:
> >> -Original Message-
> >> From: Guilherme G. Piccoli [mailto:gpicc...@linux.vnet.ibm.com]
> >>
> >> Temperature values on be2net driver are made
On 07/25/2016 07:48 AM, Sathya Perla wrote:
-Original Message-
From: Guilherme G. Piccoli [mailto:gpicc...@linux.vnet.ibm.com]
Temperature values on be2net driver are made available to userspace via
hwmon abstraction, so tools like lm-
sensors can present them to the user.
The driver p
> -Original Message-
> From: Guilherme G. Piccoli [mailto:gpicc...@linux.vnet.ibm.com]
>
> Temperature values on be2net driver are made available to userspace via
hwmon abstraction, so tools like lm-
> sensors can present them to the user.
> The driver provides hwmon structures for each ada
Temperature values on be2net driver are made available to userspace via
hwmon abstraction, so tools like lm-sensors can present them to the user.
The driver provides hwmon structures for each adapter's function.
Nevertheless, the temperature information come from fw queries performed by
be_worker()