All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Motherboard-specific configurations (sensors4mobo)
Date: Sat, 31 Mar 2007 12:42:09 +0000	[thread overview]
Message-ID: <20070331144209.cd36dcab.khali@linux-fr.org> (raw)
In-Reply-To: <46084A44.4070101@eberian.com>

Hi Ivo,

On Wed, 28 Mar 2007 14:07:18 +0200, Ivo Manca wrote:
> >> We were thinking about using the following:
> >> system-manufacturer
> >> system-product-name
> >> system-version
> >> system-serial-number
> >> baseboard-manufacturer
> >> baseboard-product-name
> >> baseboard-version
> >>
> >> It seems like these 6 fields covers all motherboards. Sending/storing the 
> >> serial number might also be a privacy issue.
> 
> > Good point.
> >
> > Do you require an exact match on all 7 parameters or do you cherry-pick 
> > the minimum that identify a motherboard?
> 
> Oops, system-serial-number didn't need to be in that list, making it 6 
> fields instead of 7. I was just copy/pasting ;)
> Anyway, we do need all the 6 to match. It might be true that some fields 

I believe that non-matching version numbers should not be fatal. It
sometimes happen that different versions of a board need different
configuration files, true, but it's rather rare, so we don't want to
store one configuration file per version in general, that would be
overkill; we'll only do so when really needed.

So I think we should try to match all 6 fields first, if it fails, try
without the versions (so only 4 fields), and only if that fails too,
declare that no matching configuration file was found.

-- 
Jean Delvare

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

  parent reply	other threads:[~2007-03-31 12:42 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
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 [this message]
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=20070331144209.cd36dcab.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --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.