mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: ACPI mailing list <acpi-devel@lists.sourceforge.net>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [ACPI] Metolious hardware-sensors-using-ACPI specs
Date: Mon, 16 Dec 2002 23:40:57 +0100	[thread overview]
Message-ID: <20021216224057.GE20773@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <EDC461A30AC4D511ADE10002A5072CAD04C7A5A4@orsmsx119.jf.intel.com>

Hi!

> > Is it goign to be implemented in linux-acpi?
> > 
> > I took a look at specs at intel, and it has rather funny legaleese:
> 
> Wow, is that still on a website somewhere?

Yep, as someone already pointed out.

> So as you may know from looking at the spec, Metolious was a spec that
> defined a way for platforms to enumerate various motherboard sensors to the
> OS, for manageability purposes.
> 
> It never took off, except for a couple companies that used the Windows
> driver for other things because they didn't want to write a driver that
> received ACPI device Notify()s.

> The licensing may be weird, but given that there really is no point in
> implementing it on Linux, does that really matter?

Ouch, I started implementing that hour ago... [Never mind, very little
damage done so far].

But... Metolious sounds *needed*; how do you access voltage sensors
without metolious, in a way that can coexist with ACPI thermal
support?

								Pavel
-- 
Casualities in World Trade Center: ~3k dead inside the building,
cryptography in U.S.A. and free speech in Czech Republic.

  parent reply	other threads:[~2002-12-16 22:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-16 18:21 Grover, Andrew
2002-12-16 18:33 ` PSI-Systems
2002-12-16 22:40 ` Pavel Machek [this message]
2002-12-16 23:02 Grover, Andrew
2002-12-16 23:15 ` Pavel Machek

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=20021216224057.GE20773@atrey.karlin.mff.cuni.cz \
    --to=pavel@suse.cz \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=andrew.grover@intel.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®