public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-ia64@vger.kernel.org, linux-acpi@vger.kernel.org, "Luck,
	Tony" <tony.luck@intel.com>
Subject: Re: [patch 2/2] ia64: add driver for ACPI methods to call native firmware
Date: Wed, 12 Sep 2007 16:50:27 +0000	[thread overview]
Message-ID: <200709121050.27668.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20070912085650.GA3015@srcf.ucam.org>

On Wednesday 12 September 2007 02:56:51 am Matthew Garrett wrote:
> On Tue, Sep 11, 2007 at 05:16:46PM -0600, Bjorn Helgaas wrote:
> > +config IA64_HP_AML_NFW
> > +	tristate "Support ACPI AML calls to native firmware"
> 
> The description seems a bit generic for something that's HP specific?

Thanks, I'll wordsmith the description a bit.  There's actually nothing
in the implementation that prevents this from working on non-HP firmware.  

I really want feedback on the best approach of:

  1.  Always build the driver static, accept the additional 4600 bytes
      in everybody's image, not export anything.

  2.  Allow building driver as a module, export sal_lock.  This would
      also enable building arch/ia64/kernel/esi.c as a module.

  3.  Allow building driver as a module, restructure SAL_CALL so we
      don't have to export sal_lock, but we do export fw_call_lock()
      (as done in these patches).  This isn't quite sufficient to
      enable building esi.c as a module.

#1 would be easiest, of course, but I'm not happy about adding stuff
that is only used on HP hardware.  #2 would be simple, but exporting
sal_lock has been resisted in the past.

Bjorn

  parent reply	other threads:[~2007-09-12 16:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11 23:14 [RFC] module to support ACPI AML calls to native firmware Bjorn Helgaas
2007-09-11 23:15 ` [patch 1/2] ia64: change SAL wrappers from macros to functions and export them Bjorn Helgaas
2007-09-11 23:16 ` [patch 2/2] ia64: add driver for ACPI methods to call native firmware Bjorn Helgaas
2007-09-12  8:56   ` Matthew Garrett
2007-09-12  9:48     ` Kyle McMartin
2007-09-12 16:50     ` Bjorn Helgaas [this message]
2007-09-13 23:11 ` [RFC] module to support ACPI AML calls to " Bjorn Helgaas
2007-09-18 23:53   ` Luck, Tony
2007-09-19 15:49     ` Bjorn Helgaas
  -- strict thread matches above, loose matches on Subject: below --
2007-09-20 20:20 driver " Bjorn Helgaas
2007-09-20 20:22 ` [patch 2/2] ia64: add driver for ACPI methods to call " Bjorn Helgaas
2007-09-21  1:03   ` Len Brown

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=200709121050.27668.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=tony.luck@intel.com \
    /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