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

10 lines
754 B
Makefile
Raw Normal View History

[202012] BRCM SAI 4.3.5.1 Fix for TH3 FDB Flush Timeout (#8342) This is to pick up BRCM SAI 4.3.5.1 which contains the following fix: CS00012201406: [4.3.3.9] SAI_STATUS_FAILURE on FDB flush after all ports flapped Preliminary tests looks fine. BGP neighbors were all up with proper routes programmed interfaces are all up Manually ran the following test cases on z9332f (TH3) T0 DUT and all passed: ``` ipfwd/test_dir_bcast.py fib/test_fib.py ``` Manually ran the following test cases on S6100 (TH) and all passed: ``` ipfwd/test_dir_bcast.py fdb/test_fdb.py ```
2021-08-05 21:03:06 -05:00
BRCM_SAI = libsaibcm_4.3.5.1_amd64.deb
$(BRCM_SAI)_URL = "https://sonicstorage.blob.core.windows.net/packages/bcmsai/4.3/202012/libsaibcm_4.3.5.1_amd64.deb?sv=2015-04-05&sr=b&sig=c%2BgR2UeeyjEyo%2BBwCFtcTOxOQbX38EeIiwqdfQSh76o%3D&se=2035-04-13T19%3A30%3A14Z&sp=r"
BRCM_SAI_DEV = libsaibcm-dev_4.3.5.1_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)))
[202012] BRCM SAI 4.3.5.1 Fix for TH3 FDB Flush Timeout (#8342) This is to pick up BRCM SAI 4.3.5.1 which contains the following fix: CS00012201406: [4.3.3.9] SAI_STATUS_FAILURE on FDB flush after all ports flapped Preliminary tests looks fine. BGP neighbors were all up with proper routes programmed interfaces are all up Manually ran the following test cases on z9332f (TH3) T0 DUT and all passed: ``` ipfwd/test_dir_bcast.py fib/test_fib.py ``` Manually ran the following test cases on S6100 (TH) and all passed: ``` ipfwd/test_dir_bcast.py fdb/test_fdb.py ```
2021-08-05 21:03:06 -05:00
$(BRCM_SAI_DEV)_URL = "https://sonicstorage.blob.core.windows.net/packages/bcmsai/4.3/202012/libsaibcm-dev_4.3.5.1_amd64.deb?sv=2015-04-05&sr=b&sig=qxAl66xr1T%2B0ibG%2BSSc4xM3nfVpE5w%2Bk1z8jI%2Fihu6c%3D&se=2035-04-13T19%3A33%3A19Z&sp=r"
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