openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Venture <venture@google.com>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: Andrew Jeffery <andrew@aj.id.au>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	John Wang <wangzhiqiang.bj@bytedance.com>
Subject: Re: qemu for bmc
Date: Thu, 19 Nov 2020 08:56:51 -0800	[thread overview]
Message-ID: <CAO=noty4NEETUhb2jXhODV9THigegMdpKcteofBdygzLD0PZdw@mail.gmail.com> (raw)
In-Reply-To: <e605bae4-b17a-b383-62a9-7594b57f7245@kaod.org>

On Wed, Nov 18, 2020 at 11:41 PM Cédric Le Goater <clg@kaod.org> wrote:
>
> Hello,
>
> On 11/18/20 10:11 PM, Patrick Venture wrote:
> > 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?
>
> I haven't seen any patches for this device on the QEMU mailing
> list.
>
> John Wang from Bytedance has started developing some new I2C
> device models for their G220A board. We hope to get that merged
> in 6.0.
>
> If you are interested, we maintain a brief TODO list here
>
>   https://github.com/openbmc/qemu/wiki

Thanks, I'll take a look.

>
> Feel free to update.
>
>
> In terms of priority, I think that the support to boot from eMMC
> on the AST2600 is an important one. Reviewing the FSI patches
> also but that's an IBM thing, so it might not interest the
> community that much.
>
> There are quite a few I2C models missing.

Yes.

>
> All Aspeed models could be more precise.
>
>
> Google and Nuvoton have merged their models for the npcm750-evb
> and quanta-gsj boards. It would be good to have some interaction
> with them, on bus/device modeling but also on full system emulation.

Yeah, I believe you've seen my team's patches adding nuvoton support
to Qemu.  It's a WIP, but we're making a lot of headway and hope to
have more Nuvoton 730/750 qemu devices sent to qemu over the coming
days, weeks, etc.

One of the big gaps that I'm seeing is that we weren't yet looking at
the rest of the board as closely, to see what other devices are
missing, such as the i2c-muxes, etc.  This will be a really good
community convergence point as there are only so many i2c-muxes,
voltage regulators, temperature sensors, that are in common use.

I'll go through some of our plans as stated and add them to the todo
list.  My team currently isn't focused on aspeed support at present,
but we're keeping an eye on it and are definitely excited to see
others contributing in that space!

>
> Cheers,
>
> C.

- Patrick

  reply	other threads:[~2020-11-19 16:59 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
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 [this message]
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='CAO=noty4NEETUhb2jXhODV9THigegMdpKcteofBdygzLD0PZdw@mail.gmail.com' \
    --to=venture@google.com \
    --cc=andrew@aj.id.au \
    --cc=clg@kaod.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=wangzhiqiang.bj@bytedance.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).