openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Patrick Venture <venture@google.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: qemu for bmc
Date: Wed, 18 Nov 2020 17:09:38 -0600	[thread overview]
Message-ID: <20201118230938.GA1261035@heinlein> (raw)
In-Reply-To: <CAO=noty_ADQwzPXx8AneRRcXNr9B15PBBByP6TNDeDCoy2ug6Q@mail.gmail.com>

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

On Wed, Nov 18, 2020 at 01:11:42PM -0800, Patrick Venture wrote:

Hi Patrick.

> Patrick;
> 
> I was looking at a patch series of yours that landed,
> https://github.com/qemu/qemu/blob/master/hw/arm/aspeed.c#L517 <-- in
> this line you're referencing a device that appears to be missing from
> qemu - namely, the pca i2c mux.
> 
> My question is to the community at large, and you also, is anyone
> currently implementing this i2c-mux or a similar one?

Timely question.

I don't know of any current work going on in that space.

Facebook has a hack-a-thon kind of event we are sponsoring at a local
university this weekend and that was one of the projects I gave as a
potential item.  So, maybe, if we're lucky, it'll be done by Monday.

I'll keep you posted.

-- 
Patrick Williams

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

  reply	other threads:[~2020-11-18 23:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 21:11 qemu for bmc Patrick Venture
2020-11-18 23:09 ` Patrick Williams [this message]
2020-11-19  0:29   ` Patrick Venture
2020-11-24 14:07     ` Patrick Williams
2020-11-24 15:56       ` Patrick Venture
2020-11-19  7:41 ` Cédric Le Goater
2020-11-19 16:56   ` Patrick Venture
2020-11-20 16:44     ` Patrick Venture
2020-11-23 10:58       ` Cédric Le Goater
2020-11-23 20:57         ` Patrick Venture

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=20201118230938.GA1261035@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=openbmc@lists.ozlabs.org \
    --cc=venture@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).