public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Carlos Corbacho <carlos@strangeworlds.co.uk>
Cc: Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, Matthew Garrett <mjg59@srcf.ucam.org>,
	Alexey Starikovskiy <aystarik@gmail.com>,
	linux-ia64@vger.kernel.org
Subject: Re: [PATCH 0/5] WMI patches for acpi-test (v2)
Date: Wed, 06 Feb 2008 00:35:54 +0000	[thread overview]
Message-ID: <200802051735.55106.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <200802052118.02733.carlos@strangeworlds.co.uk>

On Tuesday 05 February 2008 02:18:01 pm Carlos Corbacho wrote:
> On Tuesday 05 February 2008 21:03:30 Len Brown wrote:
> > On Monday 04 February 2008 21:16, Carlos Corbacho wrote:
> > > 2) Do you know of any IA64 systems using ACPI-WMI? At the moment, WMI
> > > will work on x86 and hopefully IA64, but if it turns out that no vendor
> > > has or ever will implement ACPI-WMI on IA64, then we could safely drop it
> > > there.
> >
> > I recommend skipping WMI on IA64 unless/until a real need to support it
> > emerges. There are no WMI extensions on the Intel Tiger or Hitachi Fusion
> > IA64 boxes I have access to.
> 
> Ok. The only other vendors I really have in mind are HP and Fujitsu, since 
> both those vendors use WMI on their laptops, so they would be my most likely 
> candidates to have WMI on an IA64 box (if anyone actually does use WMI on 
> IA64).

How could I tell whether our HP systems use WMI?

Bjorn

  reply	other threads:[~2008-02-06  0:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080205021658.4422.83165.stgit@pacifica>
2008-02-05 21:03 ` [PATCH 0/5] WMI patches for acpi-test (v2) Len Brown
2008-02-05 21:18   ` Carlos Corbacho
2008-02-06  0:35     ` Bjorn Helgaas [this message]
2008-02-06  2:03       ` Carlos Corbacho
2008-02-06  6:30         ` Bjorn Helgaas

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=200802051735.55106.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=aystarik@gmail.com \
    --cc=carlos@strangeworlds.co.uk \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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