1*4882a593Smuzhiyunconfig BR2_PACKAGE_LIBTEAM 2*4882a593Smuzhiyun bool "libteam" 3*4882a593Smuzhiyun depends on BR2_USE_MMU # fork() 4*4882a593Smuzhiyun depends on !BR2_STATIC_LIBS # libnl-tools 5*4882a593Smuzhiyun depends on BR2_TOOLCHAIN_HAS_THREADS # libnl 6*4882a593Smuzhiyun select BR2_PACKAGE_JANSSON 7*4882a593Smuzhiyun select BR2_PACKAGE_LIBDAEMON 8*4882a593Smuzhiyun select BR2_PACKAGE_LIBNL 9*4882a593Smuzhiyun select BR2_PACKAGE_LIBNL_TOOLS 10*4882a593Smuzhiyun help 11*4882a593Smuzhiyun The purpose of the Team driver is to provide a mechanism to 12*4882a593Smuzhiyun team multiple NICs (ports) into one logical one (teamdev) at 13*4882a593Smuzhiyun L2 layer. The process is called "channel bonding", "Ethernet 14*4882a593Smuzhiyun bonding", "channel teaming", "link aggregation", etc. 15*4882a593Smuzhiyun 16*4882a593Smuzhiyun Team tries to provide similar functionality as the bonding 17*4882a593Smuzhiyun driver, however architecturally it is quite different. Team is 18*4882a593Smuzhiyun modular, userspace driven, very lean and efficient, and it 19*4882a593Smuzhiyun does have some distinct advantages over bonding. The way Team 20*4882a593Smuzhiyun is configured differs dramatically from the way bonding is. 21*4882a593Smuzhiyun 22*4882a593Smuzhiyun If building the kernel with Buildroot, basic team support is 23*4882a593Smuzhiyun automatically enabled, but you will still need to enable the 24*4882a593Smuzhiyun modes you need, e.g. activebackup or loadbalance (e.g. with a 25*4882a593Smuzhiyun config fragment or a custom config). 26*4882a593Smuzhiyun 27*4882a593Smuzhiyun https://github.com/jpirko/libteam 28*4882a593Smuzhiyun 29*4882a593Smuzhiyuncomment "libteam needs MMU and a toolchain w/ dynamic library and threads" 30*4882a593Smuzhiyun depends on BR2_USE_MMU 31*4882a593Smuzhiyun depends on BR2_STATIC_LIBS || !BR2_TOOLCHAIN_HAS_THREADS 32