matthew/sonic-buildimage
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
e88c7d11ca
sonic-buildimage/platform/broadcom/sai.mk

10 lines
826 B
Makefile
Raw Normal View History

Upgrade to SAI BCM 4.2.1.5-6 to pick up the fib hash patch (CS00011388674) and the fdb invalid port patch (CS00011298546) (#6165)
2020-12-09 15:53:27 -06:00
BRCM_SAI = libsaibcm_4.2.1.5-6_amd64.deb
Upgrade syncd to buster. (#6106) - Why I did it To upgrade brcm syncd to buster - How I did it Updated BCM SAI using kernel version 4.19.0-12 and debian 10 to support buster. Updated syncd docker from stretch to buster in sonic-buildimage - How to verify it Ensured docker is running synd buster. After upgrade, ensured all BGP peers and ip interfaces are up. Ping to BGP neighbors is working fine.
2020-12-17 14:46:45 -06:00
$(BRCM_SAI)_URL = "https://sonicstorage.blob.core.windows.net/packages/bcmsai/4.2/master/buster/libsaibcm_4.2.1.5-6_amd64.deb?sv=2019-12-12&st=2020-12-15T06%3A40%3A06Z&se=2035-12-16T06%3A40%3A00Z&sr=b&sp=r&sig=aux78f4Uhmh2AHJqZh1GMWPYdQDWI3fVLgLmFXrpbFQ%3D"
Upgrade to SAI BCM 4.2.1.5-6 to pick up the fib hash patch (CS00011388674) and the fdb invalid port patch (CS00011298546) (#6165)
2020-12-09 15:53:27 -06:00
BRCM_SAI_DEV = libsaibcm-dev_4.2.1.5-6_amd64.deb
build orchagent and syncd docker on broadcom platform (#118) * build orchagent and syncd docker on broadcom platform
2016-12-14 13:59:24 -06:00
$(eval $(call add_derived_package,$(BRCM_SAI),$(BRCM_SAI_DEV)))
Upgrade syncd to buster. (#6106) - Why I did it To upgrade brcm syncd to buster - How I did it Updated BCM SAI using kernel version 4.19.0-12 and debian 10 to support buster. Updated syncd docker from stretch to buster in sonic-buildimage - How to verify it Ensured docker is running synd buster. After upgrade, ensured all BGP peers and ip interfaces are up. Ping to BGP neighbors is working fine.
2020-12-17 14:46:45 -06:00
$(BRCM_SAI_DEV)_URL = "https://sonicstorage.blob.core.windows.net/packages/bcmsai/4.2/master/buster/libsaibcm-dev_4.2.1.5-6_amd64.deb?sv=2019-12-12&st=2020-12-15T06%3A40%3A46Z&se=2035-12-16T06%3A40%3A00Z&sr=b&sp=r&sig=%2BnflSlIa9cIMPr%2BDmZLYtO2rhXwdDwv7Z%2BqY5MUlIM0%3D"
build orchagent and syncd docker on broadcom platform (#118) * build orchagent and syncd docker on broadcom platform
2016-12-14 13:59:24 -06:00
[build]: Eliminate build warning messages (#2172)
2018-10-20 16:39:04 -05:00
SONIC_ONLINE_DEBS += $(BRCM_SAI)
[broadcom]: Updated BRCM SAI Debian package revision number to 3.7.3.3-2. (#4182) This has patch to fix enable/disable attribute for lag member. It's on top of vanilla 3.7.3.3
2020-02-25 11:14:23 -06:00
$(BRCM_SAI_DEV)_DEPENDS += $(BRCM_SAI)
[build]: wait for conflicts package to be uninstalled (#5039) when parallel build is enabled, both docker-fpm-frr and docker-syncd-brcm is built at the same time, docker-fpm-frr requires swss which requires to install libsaivs-dev. docker-syncd-brcm requires syncd package which requires to install libsaibcm-dev. since libsaivs-dev and libsaibcm-dev install the sai header in the same location, these two packages cannot be installed at the same time. Therefore, we need to serialize the build between these two packages. Simply uninstall the conflict package is not enough to solve this issue. The correct solution is to have one package wait for another package to be uninstalled. For example, if syncd is built first, then it will install libsaibcm-dev. Meanwhile, if the swss build job starts and tries to install libsaivs-dev, it will first try to query if libsaibcm-dev is installed or not. if it is installed, then it will wait until libsaibcm-dev is uninstalled. After syncd job is finished, it will uninstall libsaibcm-dev and swss build job will be unblocked. To solve this issue, _UNINSTALLS is introduced to uninstall a package that is no longer needed and to allow blocked job to continue. Signed-off-by: Guohan Lu <lguohan@gmail.com>
2020-07-27 12:46:20 -05:00
$(eval $(call add_conflict_package,$(BRCM_SAI_DEV),$(LIBSAIVS_DEV)))
Reference in New Issue Copy Permalink