| /OK3568_Linux_fs/yocto/poky/meta/recipes-support/boost/boost/ |
| H A D | 0001-futex-fix-build-on-32-bit-architectures-using-64-bit.patch | 8 | ./boost/fiber/detail/futex.hpp:31:23: error: use of undeclared identifier 'SYS_futex' 13 Upstream-Status: Submitted [https://github.com/boostorg/fiber/pull/292] 16 boost/fiber/detail/futex.hpp | 4 ++++ 19 diff --git a/boost/fiber/detail/futex.hpp b/boost/fiber/detail/futex.hpp 21 --- a/boost/fiber/detail/futex.hpp 22 +++ b/boost/fiber/detail/futex.hpp 25 #include <boost/fiber/detail/config.hpp>
|
| H A D | 0001-Don-t-skip-install-targets-if-there-s-build-no-in-ur.patch | 14 Fixes install of boost fiber shared libraries which are missing in 1.78.0
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/net/ |
| H A D | micrel.txt | 39 - micrel,fiber-mode: If present the PHY is configured to operate in fiber mode 41 Some PHYs, such as the KSZ8041FTL variant, support fiber mode, enabled 43 registers whether the PHY is in fiber mode, so this boolean device tree 46 In fiber mode, auto-negotiation is disabled and the PHY can only work in
|
| H A D | keystone-netcp.txt | 101 - mac<->fiber mode: 3
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/lib/gcc/arm-none-linux-gnueabihf/10.3.1/include/sanitizer/ |
| H A D | tsan_interface.h | 149 void __tsan_destroy_fiber(void *fiber); 150 void __tsan_switch_to_fiber(void *fiber, unsigned flags); 151 void __tsan_set_fiber_name(void *fiber, const char *name);
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/lib/gcc/aarch64-none-linux-gnu/10.3.1/include/sanitizer/ |
| H A D | tsan_interface.h | 149 void __tsan_destroy_fiber(void *fiber); 150 void __tsan_switch_to_fiber(void *fiber, unsigned flags); 151 void __tsan_set_fiber_name(void *fiber, const char *name);
|
| /OK3568_Linux_fs/u-boot/board/freescale/t4qds/ |
| H A D | README | 84 four Lanes A/B/C/D to a SFP+ cages, which to house fiber cable or 87 So, for XFI usage, there are two scenarios, one will use fiber cable, 94 "fsl_10gkr_copper", it will use copper cable, otherwise, fiber cable 99 XFI ports will use copper cable, the other two XFI ports will use fiber
|
| /OK3568_Linux_fs/kernel/drivers/net/fddi/ |
| H A D | Kconfig | 12 run over copper or fiber. If you are connected to such a network and 23 This is support for the DEC FDDIcontroller 700 (DEFZA-AA, fiber)
|
| /OK3568_Linux_fs/u-boot/board/freescale/t208xqds/ |
| H A D | README | 90 a on-board SFP+ cages, which to house optical module (fiber cable) or 93 So, for XFI usage, there are two scenarios, one will use fiber cable, 100 "fsl_10gkr_copper", it will use copper cable, otherwise, fiber cable 105 XFI ports will use copper cable, the other two XFI ports will use fiber
|
| /OK3568_Linux_fs/buildroot/package/boost/ |
| H A D | boost.mk | 18 contract container coroutine date_time exception fiber filesystem graph \ 31 BOOST_WITHOUT_FLAGS += $(if $(BR2_PACKAGE_BOOST_FIBER),,fiber)
|
| H A D | Config.in | 137 bool "boost-fiber" 151 comment "boost-fiber needs a toolchain w/ NPTL" 156 comment "boost-fiber needs a toolchain not affected by GCC bug 64735"
|
| /OK3568_Linux_fs/kernel/drivers/net/ethernet/alacritech/ |
| H A D | Kconfig | 24 both copper and fiber.
|
| /OK3568_Linux_fs/kernel/drivers/net/hippi/ |
| H A D | Kconfig | 12 can run over copper (25m) or fiber (300m on multi-mode or 10km on
|
| /OK3568_Linux_fs/kernel/drivers/net/phy/ |
| H A D | marvell.c | 1372 int fiber, int status) in marvell_read_status_page_an() argument 1401 if (!fiber) { in marvell_read_status_page_an() 1443 int fiber; in marvell_read_status_page() local 1462 fiber = 1; in marvell_read_status_page() 1464 fiber = 0; in marvell_read_status_page() 1471 phydev->port = fiber ? PORT_FIBRE : PORT_TP; in marvell_read_status_page() 1474 err = marvell_read_status_page_an(phydev, fiber, status); in marvell_read_status_page()
|
| H A D | Kconfig | 314 fiber connections.
|
| /OK3568_Linux_fs/u-boot/board/freescale/t208xrdb/ |
| H A D | README | 52 - SerDes-1 Lane A-B: to two 10G XFI fiber (MAC9 & MAC10) 60 - Two on-board 10Gbps XFI fiber ports
|
| /OK3568_Linux_fs/kernel/arch/arm64/boot/dts/hisilicon/ |
| H A D | hip06.dtsi | 536 media-type = "fiber"; 544 media-type = "fiber";
|
| /OK3568_Linux_fs/kernel/drivers/net/dsa/microchip/ |
| H A D | ksz8795.c | 576 if (dev->ports[p].fiber) in ksz8795_w_phy() 1089 p->fiber = 1; in ksz8795_config_cpu_port() 1090 if (p->fiber) in ksz8795_config_cpu_port()
|
| H A D | ksz_common.h | 36 u32 fiber:1; /* port is fiber */ member
|
| /OK3568_Linux_fs/kernel/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | e1000e.rst | 327 between copper-based adapters and fiber-based adapters. 349 An Intel(R) Ethernet Network Adapter using fiber-based connections, however,
|
| H A D | e1000.rst | 341 If the board uses a fiber interface, these keywords are ignored, and the 342 fiber interface board only links at 1000 Mbps full-duplex.
|
| H A D | ixgb.rst | 59 | 82597EX | Intel(R) PRO/10GbE LR/SR/CX4 | - 10G Base-LR (fiber) | 60 | | Server Adapters | - 10G Base-SR (fiber) |
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-support/boost/ |
| H A D | boost.inc | 26 fiber \
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-devtools/php/ |
| H A D | php_8.1.16.bb | 79 EXTRA_OECONF:append:riscv32:libc-musl = " --disable-fiber-asm"
|
| /OK3568_Linux_fs/kernel/Documentation/networking/device_drivers/ethernet/dlink/ |
| H A D | dl2k.rst | 232 available for fiber adapter.
|