All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: "Andrew Jeffery" <andrew@aj.id.au>
Cc: "Sharad Khetan" <sharad.khetan@intel.com>,
	"Vijay Khemka" <vijaykhemka@fb.com>, rgrs <rgrs@protonmail.com>,
	"openbmc\@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: MCTP over PCI on AST2500
Date: Thu, 09 Jan 2020 22:40:06 -0500	[thread overview]
Message-ID: <29717.1578627606@localhost> (raw)
In-Reply-To: <8a1fc80f-9d25-4c38-bdcd-df05c4194fe7@www.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]


Andrew Jeffery <andrew@aj.id.au> wrote:
    > On Sat, 21 Dec 2019, at 10:45, Khetan, Sharad wrote:
    >> Hi Andrew,
    >> Sorry for late response.
    >> The plan is to have MCTP in user space.
    >>

    > How are you handling this then? mmap()'ing the BAR from sysfs?

    > I plan to get back to implementing in-kernel socket-based MCTP shortly.
    > Unfortunately it slipped back a little in my priority list late last year. I'd be
    > interested in your feedback on the proposal when I get something written
    > down.

I have read through a few MCTP documents on dtmf.org, but they either dealt
with too highlevel (SMBIOS tables), or too low-level (MCTP over UART).

Is there something that I can read that explains the underlying PCI
relationships between the BMC and the host CPU's PCI/bridges?
Maybe I just need to read the AST2500 datasheet?

(I was at one point quite knowledgeable about PCI, having designed adapter
cards with multiple targets and dealt with swizzling, and BARs, etc.)

What I heard is that for typical AST2500 based BMCs, the host CPU can map the
entire address space of the AST2500, and this rather concerns me.
I had rather expected some kind of mailbox system in a specialized ram that
both systems could use to exchange data.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2020-01-10  3:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20  5:26 MCTP over PCI on AST2500 rgrs
2019-11-20  6:54 ` Vijay Khemka
2019-11-20  6:59   ` Khetan, Sharad
2019-11-22  0:38     ` Andrew Jeffery
2019-12-21  0:15       ` Khetan, Sharad
2020-01-09  1:57         ` Andrew Jeffery
2020-01-09 18:17           ` Vijay Khemka
2020-01-09 20:45             ` Richard Hanley
2020-01-10  1:29               ` Andrew Jeffery
2020-01-10  0:30           ` Andrew Jeffery
2020-01-13 16:53             ` Khetan, Sharad
2020-01-13 18:54               ` Deepak Kodihalli
2020-01-14  5:54                 ` Khetan, Sharad
2020-01-14  6:20                   ` Jeremy Kerr
2020-01-14  6:39                     ` Khetan, Sharad
2020-01-14  8:10                       ` Deepak Kodihalli
2020-01-14 15:54                       ` Thomaiyar, Richard Marian
2020-01-14 17:45                     ` Patrick Williams
2020-01-15 13:51                       ` Jeremy Kerr
2020-01-15 14:16                         ` Patrick Williams
2020-01-14  8:54                   ` rgrs
2020-01-13 23:22               ` Andrew Jeffery
2020-01-10  3:40           ` Michael Richardson [this message]
2020-01-10  5:05             ` Andrew Jeffery
2020-01-10 15:38               ` Michael Richardson
2020-01-12 23:38                 ` Andrew Jeffery
2020-01-13 17:09                   ` Michael Richardson

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=29717.1578627606@localhost \
    --to=mcr@sandelman.ca \
    --cc=andrew@aj.id.au \
    --cc=openbmc@lists.ozlabs.org \
    --cc=rgrs@protonmail.com \
    --cc=sharad.khetan@intel.com \
    --cc=vijaykhemka@fb.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.