回复: About RGMII mode setting of MAC0

[zhouyuanqing8 at outlook.com]

Hi Andrew,

    Thank you very much for your guidance！

    I have modified the ${MACHINE}.conf file and recompiled u-boot,I will debug it on the board tomorrow.

    According to your guidance, I found the correspondence between the recipes specified in the ${MACHINE}.conf file and the pn-buildlist.

    In the compilation directory of obmc-op-control-power，as follows：

    [work/arm1176jzs-openbmc-linux-gnueabi/obmc-op-control-power/1.0+gitAUTOINC+1146f8c6e5-r1/image/usr/sbin]$ ls
    pgood_wait  power_control.exe

    The .exe file should be the executable file of windows, how can it appear in the linux system?

________________________________
发件人: Andrew Jeffery <andrew at aj.id.au>
发送时间: 2020年4月19日 12:30
收件人: zhouyuanqing8 at outlook.com <zhouyuanqing8 at outlook.com>; openbmc at lists.ozlabs.org <openbmc at lists.ozlabs.org>
抄送: uperic at 163.com <uperic at 163.com>; shinerocky at yahoo.com <shinerocky at yahoo.com>
主题: Re: About RGMII mode setting of MAC0

Hi Harley

On Sat, 18 Apr 2020, at 20:44, zhouyuanqing8 at outlook.com wrote:
>
>  Hi,
>
>  My name is Harley, I am currently developing an openbmc project based
> on the AST2500 chip. There are a few questions that need to be
> consulted. Please help me to answer them. Thank you very much!
>
>  1、About RGMII mode setting of MAC0
>  The current openbmc project and uboot code support 2 modes: MAC0 uses
> NCSI, MAC2 uses RGMII, but my board uses MAC0 RGMII. How can I simply
> configure this to complete this work, or do I have to modify
> aspeednic.c and add the new patch file under the directory
> meta-phosphor/aspeed-layer/recipes-bsp/u-boot/files ?

The way to select NCSI vs PHY is via the u-boot config files. Here are some
examples of different platforms selecting between different configs:

```
$ git grep 'UBOOT_MACHINE =' | head
meta-aspeed/conf/machine/evb-ast2500.conf:UBOOT_MACHINE = "ast_g5_phy_config"
meta-aspeed/conf/machine/evb-ast2600.conf:UBOOT_MACHINE = "ast2600_openbmc_defconfig"
meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf/machine/evb-ast2500.conf:UBOOT_MACHINE = "ast_g5_phy_config"
meta-evb/meta-evb-enclustra/meta-evb-zx3-pm3/conf/machine/evb-zx3-pm3.conf:UBOOT_MACHINE = "zynq_zc702_config"
meta-facebook/meta-tiogapass/conf/machine/tiogapass.conf:UBOOT_MACHINE = "ast_g5_ncsi_config"
meta-facebook/meta-yosemitev2/conf/machine/yosemitev2.conf:UBOOT_MACHINE = "ast_g5_ncsi_config"
```

Essentially, you want to configure your platform (i.e. in ${MACHINE}.conf) with:

```
UBOOT_MACHINE = "ast_g5_phy_config"
```

>
>  2、There are lot of recipes under  directory meta-phosphor, How does
> bitbake choose specific recipes? I read the manual of bitbake and the
> project of openbmc, and I didn't find a way to choose. openbmc has many
> recipes, we can't use them all。

This is handled by variously by packagegroups, DISTRO_FEATURES,
MACHINE_FEATURES and IMAGE_INSTALL. Additionally if we look at
e.g. meta-ibm/meta-witherspoon/conf/machine/witherspoon.conf, we find:

```
require conf/machine/include/ast2500.inc
require conf/machine/include/obmc-bsp-common.inc
require conf/machine/include/openpower.inc
require conf/machine/include/p9.inc
```

If we drill down through these files we find things like
meta-aspeed/conf/machine/include/aspeed.inc:

MACHINE_EXTRA_RRECOMMENDS += "udev-aspeed-vuart udev-aspeed-mtd-partitions"

So if recommended packages are to be installed, then these two packages
will be installed on ASPEED-based images.

The hierarchy of `require` directives helps build up the set of packages to be
installed in the image via at least the variables I mentioned above.

>
>  3、There are many common recipes under openbmc / meta-phosphor, is
> there any documentation about the architecture and detailed
> implementation principles of each recipe? For example, chassis power
> control.

Less so documentation of the recipes themselves, but you'll find design
discussions, cheatsheets and guides in the docs repository:

https://github.com/openbmc/docs/

Hope that helps.

Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200419/c6999d15/attachment-0001.htm>