public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
Cc: linux-acpi@vger.kernel.org,
	openipmi <openipmi-developer@lists.sourceforge.net>,
	Len Brown <lenb@kernel.org>, Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: acpi_find_bmc() and acpi_get_table()
Date: Tue, 20 Feb 2007 07:55:36 -0600	[thread overview]
Message-ID: <45DAFDD8.909@acm.org> (raw)
In-Reply-To: <45DA9931.80605@linux.intel.com>

Alexey Starikovskiy wrote:
> Bjorn Helgaas wrote:
>> On Thursday 15 February 2007 22:15, Corey Minyard wrote:
>>  
>>> Bjorn Helgaas wrote:
>>>    
>>>> On Saturday 10 February 2007 21:27, Len Brown wrote:
>>>>        
>>>>> acpi_find_bmc() appears to be searching for multiple SPMI tables 
>>>>> in the RSDT and running
>>>>> try_init_acpi() on each of them
>>>>> until it doesn't find any more.
>>>>>             
>>>> I can't remember why we look at the SPMI table(s) rather than
>>>> registering a normal ACPI (or even PNP) driver.  Unless we
>>>> need to poke the BMC very early, wouldn't it be better to
>>>> rely on the device description in the namespace?
>>>>         
>>> For some strange reason the normal ACPI information does not
>>> have all the information needed by the driver.  It doesn't have
>>> register size or spacing information.
>>>     
>>
>> I guess that would be a defect in the way ACPI is being used,
>> wouldn't it?  A PNP ID should define the device programming
>> model, including things like register size and spacing.  It
>> sounds like somebody didn't define a new PNP ID when he should
>> have.  I wonder whether it's worth trying to fix this.
>>
>>   
> Yes, it is considered an ACPI fault. Could you please describe in 
> detail, which registers miss the information? And probably your 
> acpidump will help as well.
I don't have a machine with an ACPI description of the BMC.  I'll copy 
the mailing list to see if anyone has an ACPI-described BMC.

I don't know that much about ACPI, so maybe that information is 
described somehow in a way the IPMI spec doesn't talk about directly, 
like in the _CRS object.

-Corey

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2007-02-20 13:55 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 [this message]
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
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=45DAFDD8.909@acm.org \
    --to=minyard@acm.org \
    --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