From: Bruce@Ivn.cl (Ivan Barrera A.)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] LM Sensors Autoconfig Tool
Date: Tue, 06 Jun 2006 19:16:28 +0000 [thread overview]
Message-ID: <4485D48C.7010507@Ivn.cl> (raw)
Hi !
I recently subscribed to the list, as i'll be the one developing an
Autoconfig Tool for Lm Sensors.
I've been taking a look with Hans de Goede in which way is the best to
identify a motheboard, and each sensor. (as well, as how to write a user
tool which will look into the database and write the configuration).
The project consist en 2 main parts :
1 - A web application which will mantain a database with the info about
motheboard - sensors and configurations. (as well as some "use notes").
2 - User tools which will be able to query the database and get the
correct configuration for the motheboard/sensors detected.
For this month's end i pretend to have a basic working website, as well
as a basic user-tool.
The next month, i'll want to work on the details (some gui, more
advanced website, etc)
Now, i'm working on how to detect correctly different motheboards and
sensors, to build the database. I own lots of motheboards, however most
of them are too different (i want to see, how similar are the reports of
dmidecode on "similar" motheboards (i.e. different revisions)).
I've been reading the earlier posts about his, to see more ideas on how
to detect this configurations. So, if any has ideas on this, let me know.
I don't want to be a pain to the list, so, i'll keep informed on
relevant issues working on the project. (as well, as some personal
questions about some drivers :) )
Well, this is just an introduction post. I'll write more as soon as i
have more news.
Ivan Barrera A. [Bruce]
PS: Excuse my english. It's a little rusty , as i haven't practiced in
some time.
next reply other threads:[~2006-06-06 19:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 19:16 Ivan Barrera A. [this message]
2006-06-06 20:55 ` [lm-sensors] LM Sensors Autoconfig Tool Roger Lucas
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=4485D48C.7010507@Ivn.cl \
--to=bruce@ivn.cl \
--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.