From: Hans de Goede <hdegoede@redhat.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Another possible hwmon project
Date: Wed, 24 Jun 2009 08:24:03 +0000 [thread overview]
Message-ID: <4A41E2A3.9020808@redhat.com> (raw)
In-Reply-To: <20090624081700.GB4949@ubuntu>
Hi all,
On 06/24/2009 10:17 AM, Andre Prendel wrote:
> On Mon, Jun 22, 2009 at 12:03:13AM +0200, Hans de Goede wrote:
>>
>> On 06/21/2009 10:35 AM, Andre Prendel wrote:
>>> On Fri, Jun 19, 2009 at 09:15:39AM +0200, Hans de Goede wrote:
>>>> Hi,
>>> Hi Hans,
>>>
>>> First, sorry for bad response times. I'm very busy with private stuff
>>> at the moment. I'll change the company I'm working for. This is
>>> related with moving back to my hometown (Dresden).
>>>
>> Ok, np.
>>
>>>> <snip>
>>>>
>>>>> Thanks for all the material. I read some stuff about DMI and SMBIOS
>>>>> yesterday. Further I checked out the dmidecode source code. I will
>>>>> go on with investigation by reading the mailing list discussions etc.
>>>>>
>>>> I don't think you need to dig that deep wrt DMI,
>>> I want to know how things work at low level. This makes things easier
>>> to understand for me.
>>>
>>>> what we will most likely
>>>> and up doing is looking for the strings found inside
>>>> /sys/devices/virtual/dmi/id/board_name
>>>> /sys/devices/virtual/dmi/id/board_vendor
>>> I can't see these files in sysfs. What driver is responsible for creation?
>>>
>> Hmm, strange, I dunno on all my systems they just exists. Weird, maybe you
>> are running a somewhat old kernel ?
>
> Ok, I've found the files on my system under /sys/class/dmi/id/. Driver
> /drivers/firmware/dmi-id.c creates the files. The driver was
> introduced in 2007.
>
Hmm, ok, I have them there too (/sys/class/dmi/id is a symlink to
/sys/devices/virtual/dmi/id on my system), so if /sys/class/dmi/id
works on more systems / kernel configs lets use that.
> Jean, could you bring some light into the darkness? I've seen you did
> some work on the DMI stuff.
>
> I'm using the most recent mainline kernel form git. Hans, what version
> do you use?
>
I'm using a stock Fedora 11 kernel, I think this might be related to
the various sysfs compatibility kernel configuration options.
> BTW, Jean. Hans asked me for working on the automatic configuration of
> sensors using DMI information.
>
Ack, its still something which I would like to see done, so I suggested the
idea to Andre.
Andre, as said before I think once you're done orienting yourself, the first
thing to do is write a proposal how this all will work and send it to the
list.
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-06-24 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 8:17 [lm-sensors] Another possible hwmon project Andre Prendel
2009-06-24 8:24 ` Hans de Goede [this message]
2009-06-24 9:26 ` Andre Prendel
2009-06-26 8:29 ` Andre Prendel
2009-07-21 14:20 ` Jean Delvare
2009-07-22 20:44 ` Andre Prendel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A41E2A3.9020808@redhat.com \
--to=hdegoede@redhat.com \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.