public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Corey Minyard <minyard@acm.org>
Cc: openipmi-developer@lists.sourceforge.net, bjorn.helgaas@hp.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] ipmi: Only register one si per bmc
Date: Wed, 21 Apr 2010 19:21:54 +0100	[thread overview]
Message-ID: <20100421182154.GA16436@srcf.ucam.org> (raw)
In-Reply-To: <4BCF3F69.3050003@acm.org>

On Wed, Apr 21, 2010 at 01:09:45PM -0500, Corey Minyard wrote:

> If I understand this correctly, this would really be "Only register one  
> si per system".  Unfortunately, there are systems that have more than  
> one BMC each with their own interface.

The spec explicitly says that while a system may have multiple BMCs, 
only one BMC may respond to GetDeviceID (6.11 of the 2.0 spec). Is the 
real world irritatingly incompatible with this?

> Also, I believe the driver would not function between the previous 
> patch and this patch, which isn't the best.

That's true. I can fix that up fairly easily.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2010-04-21 18:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20 18:40 [PATCH 1/3] ipmi: Split device discovery and registration Matthew Garrett
2010-04-20 18:40 ` [PATCH 2/3] ipmi: Only register one si per bmc Matthew Garrett
2010-04-20 18:40   ` [PATCH 3/3] ipmi: Change device discovery order Matthew Garrett
2010-04-21 18:09   ` [PATCH 2/3] ipmi: Only register one si per bmc Corey Minyard
2010-04-21 18:21     ` Matthew Garrett [this message]
2010-04-21 20:03       ` Corey Minyard
2010-04-21 20:10         ` Matthew Garrett

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=20100421182154.GA16436@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minyard@acm.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