All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Lucas <ejl@eberian.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Motherboard-specific configurations (sensors4mobo)
Date: Thu, 29 Mar 2007 14:18:57 +0000	[thread overview]
Message-ID: <460BCAD1.1070700@eberian.com> (raw)
In-Reply-To: <46084A44.4070101@eberian.com>

Hi Folks,

Ivo Manca wrote:
...
> One thing I noticed, looking through your code, was the fact that your 
> script is capable of finding multipe matches. I wonder whether or not 
> this is something we want to have there?
> Giving a random, unique DMI string, there should only be one possible 
> configuration, unless the dmistrings are bogus.
>
> It is possible that users want to improve the config, but then he or 
> she should just modify the existing and upload it, isn't it?
> So I don't really see a point of supporting more matches. Maybe I'm 
> overlooking something.
Erm, that was speculative - The fear was that a BIOS update might change 
the dmidecode info. In that case, it would be cleanest to allow multiple 
matches in the one file instead of forcing users to create duplicate 
sensors.conf files for each BIOS.

I don't know if this is actually a real risk or not. Has anyone found 
BIOS updates changing the six key parameters?


>> I have also added a "tags" field in which you can add a fixed set of 
>> tags to describe the file: so far I have thought of "broken", 
>> "experimental" and "beta". Perhaps this goes some way 
>> towardsemulating your "unsure" database flag, Ivo? I went for the 
>> name "tags" rather than "status" so that other info could be added 
>> with minimal api changes. This is more for my sensors overlay work, 
>> so feel free to disregard it if it doesn't fit your goals.
>
> Sounds good. Maybe add a final as well?
I was thinking it would be easier to make that implicit? i.e. only add a 
tag in the special cases. It might well be worth putting in though, as a 
seal of approval.


>> Can anyone point me towards a description of the "dynamic chips 
>> support" for libsensors that Jean mentioned. (Sorry, my googling 
>> failed on this).
>>
>> For motherboard specific sensors.conf files, would it make sense to 
>> use the same fan labels that are used in the manual and on the 
>> motherboard itself? (What is the offical naming policy? - grepping  
>> sensors.conf shows a range of names)
>
> I've seen it being mentioned various times, but I don't think I can 
> help you out with it.
I will keep looking.

Gook luck,
    Ed


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2007-03-29 14:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26 22:33 [lm-sensors] Motherboard-specific configurations (sensors4mobo) Ed Lucas
2007-03-27 15:39 ` Jean Delvare
2007-03-27 16:07 ` Ivo Manca
2007-03-28  9:30 ` Ed Lucas
2007-03-28 10:56 ` Ivo Manca
2007-03-28 11:20 ` Hans de Goede
2007-03-28 11:49 ` Ed Lucas
2007-03-28 12:07 ` Ivo Manca
2007-03-28 17:09 ` David Hubbard
2007-03-29  8:03 ` Pinkel
2007-03-29 10:00 ` Ed Lucas
2007-03-29 13:20 ` Ivo Manca
2007-03-29 14:18 ` Ed Lucas [this message]
2007-03-29 14:56 ` Hans de Goede
2007-03-31 12:22 ` Jean Delvare
2007-03-31 12:36 ` Jean Delvare
2007-03-31 12:42 ` Jean Delvare
2007-03-31 12:45 ` Jean Delvare
2007-03-31 12:50 ` Jean Delvare
2007-04-04  9:34 ` Ivo Manca
2007-04-08 11:13 ` Jean Delvare

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=460BCAD1.1070700@eberian.com \
    --to=ejl@eberian.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.