⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 net.cdl

📁 Using eCos on LPC2
💻 CDL
📖 第 1 页 / 共 3 页
字号:
            flavor  data            default_value CYGPKG_NET_THREAD_PRIORITY + 1            active_if CYGOPT_NET_DHCP_DHCP_THREAD            description "            This option sets the thread priority level used by the DHCP            management thread.  It should be high enough that it can run            when necessary, but it does not need to be as high as the            network thread itself."        }        cdl_option CYGOPT_NET_DHCP_PARM_REQ_LIST_REPLACE {            display "Replace DHCP request options"            flavor  booldata            default_value 0            active_if CYGOPT_NET_DHCP_DHCP_THREAD            description "                This option replaces the default list of requested                options in the DHCP/BOOTP request list.  These are a                comma separated list of TAG_xxx values."        }        cdl_option CYGOPT_NET_DHCP_PARM_REQ_LIST_ADDITIONAL {            display "Additional DHCP request options"            flavor  booldata            default_value 0            active_if CYGOPT_NET_DHCP_DHCP_THREAD            description "                 This option adds additional options to the list of                requested options in the DHCP/BOOTP request list.                These are a comma separated list of TAG_xxx values."        }        cdl_component CYGOPT_NET_DHCP_OPTION_HOST_NAME {            display "DHCP host name option"            flavor  bool            default_value 0            active_if CYGOPT_NET_DHCP_DHCP_THREAD            description "                This option adds the TAG_HOST_NAME option to the DHCP/BOOTP                requests.  The host name is defined by calling the function                dhcp_set_hostname(), prior to calling init_all_network_interfaces()."            cdl_option CYGNUM_NET_DHCP_OPTION_HOST_NAME_LEN {                display "DHCP host name maximum length"                flavor  data                default_value 60                legal_values 0 to 255                active_if CYGOPT_NET_DHCP_OPTION_HOST_NAME                description "                    This option defines the maximum length allowed for the                     host name set by dhcp_set_hostname()."            }        }        cdl_option CYGOPT_NET_DHCP_OPTION_DHCP_CLIENTID_MAC {            display "DHCP client ID option"            flavor  bool            default_value 0            active_if CYGOPT_NET_DHCP_DHCP_THREAD            description "                This option adds the TAG_DHCP_CLIENTID option to the DHCP/BOOTP                requests.  It uses the interface MAC address for the identifier."        }        cdl_option CYGNUM_NET_DHCP_MIN_RETRY_TIME {            display "DHCP minimum retry time"            flavor        data            legal_values  0 to 100            default_value 100            description "               This option allows the application to specify the               minimum number of seconds for DHCP discovery. If DHCP               discovery fails, the action to be taken is application               specific. Multiple discovery attempts are made during               the time specified with each subsequent attempt having               a longer timeout. Attempts begin at approximately 1, 5,               15, 35, and 65 seconds with the last attempt timing out               after the total of 125 seconds. A new attempt will not               begin if the minimum time has been reached. Although,               an attempt in progress will run past the minimum time               specified. For example: Specifying 30 seconds would               timeout at 35 seconds. Specifying 70 seconds has the               same effect as specifying 100 seconds where it would               run for the total of 125 seconds."          }     }    cdl_component CYGPKG_NET_IPV6_ROUTING {        display       "Options controlling IPv6 routing"        active_if     CYGPKG_NET_INET6        flavor        bool        default_value 1        description "            Various options which control how routing is done for the            IPv6 enabled interfaces."        cdl_component CYGOPT_NET_IPV6_ROUTING_THREAD {            display       "Thread for IPv6 routing"            requires      CYGPKG_POSIX            flavor        bool            default_value 1            description "                Provide a separate thread to send router solicitation                messages."            compile ipv6_routing_thread.c            cdl_option CYGINT_NET_IPV6_ROUTING_THREAD_PRIORITY {                display       "IPv6 routing thread priority"                flavor        data                default_value CYGPKG_NET_THREAD_PRIORITY + 1                description "                    This option sets the thread priority level used by the IPv6                    routing thread.  It should be high enough that it can run                    when necessary, but it does not need to be as high as the                    network thread itself."            }            cdl_option CYGINT_NET_IPV6_ROUTING_THREAD_PERIOD {                display       "IPv6 routing thread rate"                flavor        data                default_value 5*60                description "                    This option sets the rate at which router solicitations will                    be sent out by the routing thread (in seconds)."            }        }    }    cdl_component CYGPKG_NET_DEBUG {        display       "Debug output"        default_value 0         description   "                This component controls whether there is diagnostic output                for stack operations. Options within this component allow                even more verbose output for certain areas."        cdl_option CYGDBG_NET_DHCP_CHATTER {                display       "Extra debug output for DHCP"                default_value 0        }    }    cdl_option CYGDBG_NET_TIMING_STATS {        display       "Network timing statistics"        default_value 0        description   "                This component controls whether there is diagnostic                 information about how long memcpy, malloc, mbuf_alloc                etc take to perform."    }    cdl_option CYGDBG_NET_SHOW_MBUFS {        display       "Network MBUF diagnostics"        default_value 0        description   "                This option controls whether diagnostic                 information about the state of all mbufs is collected.                This information will be displayed whenever the network                stack runs out of mbufs."    }    cdl_component CYGPKG_NET_OPTIONS {        display "Networking support build options"        flavor  none        no_define        cdl_option CYGPKG_NET_CFLAGS_ADD {            display "Additional compiler flags"            flavor  data            no_define            default_value { "-D_KERNEL -D__ECOS -D__INSIDE_NET" }            description   "                This option modifies the set of compiler flags for                building the networking package.                These flags are used in addition                to the set of global flags."        }        cdl_option CYGPKG_NET_CFLAGS_REMOVE {            display "Suppressed compiler flags"            flavor  data            no_define            default_value { "" }            description   "                This option modifies the set of compiler flags for                building the networking package. These flags are removed from                the set of global flags if present."        }    }    cdl_component CYGPKG_NET_BUILD_TESTS {        display "Testing options"        flavor  none        no_define        description "                This component contains options related to testing the network                stack."        cdl_option CYGPKG_NET_BUILD_HW_TESTS {            display "Build hardware networking tests (demo programs)"            flavor  bool            no_define            requires { CYGHWR_NET_DRIVER_ETH0_SETUP || CYGHWR_NET_DRIVER_ETH1_SETUP }            default_value 0            description   "             This option enables the building of additional network tests             that use real ethernet devices. At this time these are just             demos. With this option disabled, only loopback             interface tests will be built."        }        cdl_option CYGPKG_NET_TESTS {            display "Networking tests"            flavor  data            no_define            calculated { CYGPKG_NET_BUILD_HW_TESTS ? \                    "tests/mbuf_test \                    tests/socket_test \                    tests/ftp_test \                    tests/server_test \                    tests/nc_test_slave \                    tests/tftp_client_test \                    tests/tftp_server_test \                    tests/tcp_echo \                    tests/set_mac_address \                    tests/bridge \                    tests/flood \                    tests/ping_test \                    tests/dhcp_test \                    tests/dhcp_test2 \                    tests/ping_lo_test \                    tests/tcp_lo_test \                    tests/udp_lo_test \                    tests/multi_lo_select \                    tests/tcp_lo_select \                    tests/addr_test.c "             :                    "tests/ping_lo_test \                    tests/tcp_lo_test \                    tests/udp_lo_test \                    tests/multi_lo_select \                    tests/tcp_lo_select"            }            description   "             This option specifies the set of tests             for the networking package."        }                cdl_option CYGPKG_NET_TESTS_USE_RT_TEST_HARNESS {            display "Use real-time response test harness (if available)"            default_value 0            description "                    Platform and/or ethernet device driver packages may                    provide a test harness to verify that interrupts are                    not disabled or flooded for too long during a test.  If                    such is provided, CYGTST_DEVS_ETH_TEST_NET_REALTIME is                    defined and can be #include'd to acquire the support.                    Some tests in the TCP/IP stack can use this harness;                    this option controls whether they do.  The StrongARM                    EBSA285 Ethernet device driver is one package that                    provides such a harness.  See the file                    tests/test_net_realtime.h in there for details."

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -