From: Corey Minyard <minyard@acm.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Jordan_Hargrave@dell.com, linux-acpi@vger.kernel.org,
Matt_Domsch@dell.com, alexey.y.starikovskiy@linux.intel.com,
openipmi-developer@lists.sourceforge.net, lenb@kernel.org
Subject: Re: [Openipmi-developer] acpi_find_bmc() and acpi_get_table()
Date: Wed, 28 Feb 2007 16:44:56 -0600 [thread overview]
Message-ID: <45E605E8.1010502@acm.org> (raw)
In-Reply-To: <200702281535.31329.bjorn.helgaas@hp.com>
Bjorn Helgaas wrote:
> On Wednesday 28 February 2007 15:05, Jordan_Hargrave@dell.com wrote:
>
>> The reason for the acpi_bus_register/unregister is to get the handle
>> of the IPMI ACPI object. There isn't a way to get the device handle
>> otherwise. Once it gets the handle it doesn't need the ACPI device
>> anymore.
>>
>
> Well, but in a world of truth and beauty, we should treat the
> interface as an ACPI device, and we really should only be using
> it after acpi_ipmi_add() and before acpi_ipmi_remove(). So that
> implies that we shouldn't call acpi_bus_unregister_driver() until
> we're ready to unload the driver.
>
yes, that sounds more reasonable to me.
> I have no idea how multiple IPMI devices should be handled. But
> some HP systems have several, and I think they can be hot-added
> and removed.
The current IPMI driver can actually do hot add and remove, so if the low-level ACPI code does the add/remove, it will automagically work. I'd like to know how well that worked :).
-Corey
next prev parent reply other threads:[~2007-02-28 22:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-11 4:27 acpi_find_bmc() and acpi_get_table() Len Brown
2007-02-11 4:53 ` Corey Minyard
2007-02-11 5:28 ` Len Brown
2007-02-16 4:03 ` Bjorn Helgaas
2007-02-16 5:15 ` Corey Minyard
2007-02-20 4:31 ` Bjorn Helgaas
2007-02-20 6:46 ` Alexey Starikovskiy
2007-02-20 13:55 ` Corey Minyard
2007-02-25 21:59 ` Matt Domsch
2007-02-26 18:30 ` Jordan_Hargrave
2007-02-26 19:32 ` [Openipmi-developer] " Bjorn Helgaas
2007-02-26 20:06 ` Jordan_Hargrave
2007-02-26 22:39 ` Bjorn Helgaas
2007-02-28 21:42 ` Corey Minyard
2007-02-28 22:05 ` Jordan_Hargrave
2007-02-28 22:35 ` Bjorn Helgaas
2007-02-28 22:44 ` Corey Minyard [this message]
2007-04-13 17:44 ` Bjorn Helgaas
2007-04-17 22:50 ` Corey Minyard
2007-04-18 15:32 ` [Openipmi-developer] " Bjorn Helgaas
2007-07-18 16:49 ` Jordan_Hargrave
2007-07-18 19:19 ` Bjorn Helgaas
2007-07-19 16:32 ` [Openipmi-developer] " Jordan_Hargrave
2007-07-19 18:50 ` Bjorn Helgaas
2008-07-17 18:32 ` [Openipmi-developer] " Bjorn Helgaas
2007-07-20 14:11 ` Corey Minyard
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=45E605E8.1010502@acm.org \
--to=minyard@acm.org \
--cc=Jordan_Hargrave@dell.com \
--cc=Matt_Domsch@dell.com \
--cc=alexey.y.starikovskiy@linux.intel.com \
--cc=bjorn.helgaas@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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