All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] BIOS Corruption (was : new abituguru driver in mm
Date: Fri, 11 Aug 2006 09:05:57 +0000	[thread overview]
Message-ID: <20060811110557.0da9ee0c.khali@linux-fr.org> (raw)
In-Reply-To: <ce9ef0d90608052222j74e9f6fes40cbc5edf5678577@mail.gmail.com>

Hi Hans,

> Jean Delvare wrote:
> > 
> > (As a side note, our sensors-detect script still doesn't know about the
> > uGuru. Don't you want to add support for it? Or is it just too
> > dangerous because of the non-standard I/O addresses?)
> 
> I don't know what else could be behind those addresses, so thats not the 
> reason I haven't worked on adding it to the script yets. The real 
> problem is that the current detection code in the driver could very well 
> miss-detect. The only good way of doing detection would be todo a proof 
> read. A better idea would be to use dmidecode and sue the info from 
> there, atleast for Abit motherboards this info seems sane. I could do 
> that if you want me to (as time permits).

I don't really care myself, but that would probably bring you some more
testers. Indeed checking that the board is an Abit board would make
some sense. Not only in sensors-detect, but also in the driver itself.

-- 
Jean Delvare


      parent reply	other threads:[~2006-08-11  9:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-06  5:22 [lm-sensors] BIOS Corruption (was : new abituguru driver in mm Sunil Kumar
2006-08-07 10:19 ` Jean Delvare
2006-08-07 16:10 ` Sunil Kumar
2006-08-07 19:34 ` Sergey Vlasov
2006-08-07 20:53 ` Sunil Kumar
2006-08-08 15:25 ` Sergey Vlasov
2006-08-09 18:35 ` Hans de Goede
2006-08-09 20:48 ` Sunil Kumar
2006-08-10 11:57 ` Hans de Goede
2006-08-10 15:48 ` Sunil Kumar
2006-08-11  7:47 ` Jean Delvare
2006-08-11  7:50 ` Hans de Goede
2006-08-11  9:05 ` Jean Delvare [this message]

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=20060811110557.0da9ee0c.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.