All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Corey Minyard <minyard@acm.org>
Cc: Len Brown <lenb@kernel.org>,
	minyard@mvista.com, linux-acpi@vger.kernel.org
Subject: Re: acpi_find_bmc() and acpi_get_table()
Date: Mon, 19 Feb 2007 21:31:52 -0700	[thread overview]
Message-ID: <200702192131.52947.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <45D53DDE.5000300@acm.org>

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.

Bjorn

  reply	other threads:[~2007-02-20  4:31 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 [this message]
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
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=200702192131.52947.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=minyard@acm.org \
    --cc=minyard@mvista.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.