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] [PATCH 0/2] hwmon: (abituguru3) Partial DMI
Date: Thu, 15 Jan 2009 18:03:18 +0000	[thread overview]
Message-ID: <20090115190318.45ba2ab7@hyperion.delvare> (raw)
In-Reply-To: <1231865798-12187-1-git-send-email-alistair@devzero.co.uk>

On Thu, 15 Jan 2009 16:48:57 +0000, Alistair John Strachan wrote:
> On Thursday 15 January 2009 15:22:45 Jean Delvare wrote:
> > > (One remaining question would be whether patch 1 should be CCed to
> > > -stable, since there has been a regression introduced into 2.6.27 and
> > > present in 2.6.28 for some BIOS revisions of the IP35 Pro.)
> >
> > Is there really a regression? If the DMI matching doesn't work, we fall
> > back to the old detection method, so I can't see how there would be a
> > regression. Care to explain?
> 
> Having looked at this properly I agree. It's clear that in this bug report 
> what actually happened was the DMI match failed, AND the probe routine failed.
> 
> This definitely puts the final nail in the coffin of manual probing, 
> especially on the IP35 Pro (which was where all these changes originated 
> from).
> 
> Sorry for the confusion, you are correct, and there is no way this could be 
> considered a regression. I had just extrapolated that from the original 
> poster, but it must be the case that it has never worked, or worked 
> unreliably.

Or the regression was cause by a BUIS update. In which case we are not
responsible for it.

> > Speaking of DMI matching... If DMI is disabled, we do:
> >
> > static inline int abituguru3_dmi_detect(void)
> > {
> > 	return -ENODEV;
> > }
> >
> > And this error value causes abituguru3_init() to bail out. Unless I'm
> > missing something, the abituguru3 driver is simply useless without DMI
> > support at the moment. We should either make that official and make the
> > driver depend on DMI at Kconfig level, or change
> > abituguru3_dmi_detect() to return 1, so that we fallback to the old
> > detection method. Opinions?
> 
> It should return 1. This is simply a blunder. Fortunately CONFIG_DMI is quite 
> difficult to turn off, and no distribution would. I'll follow up to this email 
> with a proper patch.

Great, thanks.

> Apologies for the mistakes..

Heh, no problem.

-- 
Jean Delvare

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

      parent reply	other threads:[~2009-01-15 18:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 16:56 [lm-sensors] [PATCH 0/2] hwmon: (abituguru3) Partial DMI matching, Alistair John Strachan
2009-01-15 15:22 ` [lm-sensors] [PATCH 0/2] hwmon: (abituguru3) Partial DMI Jean Delvare
2009-01-15 16:48 ` Alistair John Strachan
2009-01-15 18:03 ` 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=20090115190318.45ba2ab7@hyperion.delvare \
    --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.