mirror of
https://github.com/coolsnowwolf/lede.git
synced 2025-04-18 17:33:31 +00:00
51ec2f45a6
* build: fix incomplete initramfs compression options
Requires: tools/lz4, tools/lzop
complete the wiring so that these options work:
* `CONFIG_KERNEL_INITRAMFS_COMPRESSION_LZO`
* `CONFIG_KERNEL_INITRAMFS_COMPRESSION_LZ4`
Signed-off-by: Tony Butler <spudz76@gmail.com>
[remove blocking dependencies for separate ramdisk, fix lzop options]
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* include: sync with upstream
* toolchain/binutils: add support for version 2.40
Release notes:
https://sourceware.org/pipermail/binutils/2023-January/125671.html
Signed-off-by: Linhui Liu <liulinhui36@gmail.com>
* toolchain/gcc: switch to version 12 by default
Also fix build error with gcc 12.
* toolchain/nasm: update to 2.16.01
ChangeLog:
Version 2.16.01
_This is a documentation update release only._
(*) Fix the creation of the table of contents in the HTML version of
the documentation.
Version 2.16
(*) Support for the `rdf' format has been discontinued and all the
RDOFF utilities has been removed.
(*) The `--reproducible' option now leaves the filename field in the
COFF object format blank. This was always rather useless since
it is only 18 characters long; as such debug formats have to
carry their own filename information anyway.
(*) Fix handling of MASM-syntax reserved memory (e.g. `dw ?') when
used in structure definitions.
(*) The preprocessor now supports functions, which can be less
verbose and more convenient than the equivalent code implemented
using directives. See section 4.4.
(*) Fix the handling of `%00' in the preprocessor.
(*) Fix incorrect handling of path names affecting error messages,
dependency generation, and debug format output.
(*) Support for the RDOFF output format and the RDOFF tools have
been removed. The RDOFF tools had already been broken since at
least NASM 2.14. For flat code the ELF output format
recommended; for segmented code the `obj' (OMF) output format.
(*) New facility: preprocessor functions. Preprocessor functions,
which are expanded similarly to single-line macros, can greatly
simplify code that in the past would have required a lengthy
list of directives and intermediate macros. See section 4.4.
(*) Single-line macros can now declare parameters (using a `&&'
prefix) that creates a quoted string, but does _not_ requote an
already quoted string. See section 4.2.1.
(*) Instruction table updated per public information available as of
November 2022.
(*) All warnings in the preprocessor have now been assigned warning
classes. See appendix A.
(*) Fix the invalid use of `RELA'-type relocations instead of `REL'-
type relocations when generating DWARF debug information for the
`elf32' output format.
(*) Fix the handling `at' in `istruc' when the structure contains
local labels. See section 5.9.2.
(*) When assembling with `--reproducible', don't encode the filename
in the COFF header for the `coff', `win32' or `win64' output
formats. The COFF header only has space for an 18-character
filename, which makes this field rather useless in the first
place. Debug output data, if enabled, is not affected.
(*) Fix incorrect size calculation when using MASM syntax for non-
byte reservations (e.g. `dw ?'.)
(*) Allow forcing an instruction in 64-bit mode to have a (possibly
redundant) REX prefix, using the syntax `{rex}' as a prefix.
(*) Add a `{vex}' prefix to enforce VEX (AVX) encoding of an
instruction, either using the 2- or 3-byte VEX prefixes.
(*) The `CPU' directive has been augmented to allow control of
generation of VEX (AVX) versus EVEX (AVX-512) instruction
formats, see section 7.11.
(*) Some recent instructions that previously have been only
available using EVEX encodings are now also encodable using VEX
(AVX) encodings. For backwards compatibility these encodings are
not enabled by default, but can be generated either via an
explicit `{vex}' prefix or by specifying either `CPU LATEVEX' or
`CPU NOEVEX'; see section 7.11.
(*) Document the already existing `%unimacro' directive. See section
4.5.12.
(*) Fix a code range generation bug in the DWARF debug format
(incorrect information in the `DW_AT_high_pc' field) for the ELF
output formats. This bug happened to cancel out with a bug in
older versions of the GNU binutils linker, but breaks with other
linkers and updated or other linkers that expect the spec to be
followed.
(*) Fix segment symbols with addends, e.g. `jmp _TEXT+10h:0' in
output formats that support segment relocations, e.g. the `obj'
format.
(*) Fix various crashes and hangs on invalid input.
Signed-off-by: Linhui Liu <liulinhui36@gmail.com>
* toolchain: musl: Fix symbol loading in gdb
Fix DT_DEBUG handling on MIPS in musl libc.
With this change gdb will load the symbol files for shared libraries on MIPS too.
This patch was taken from this thread: https://www.openwall.com/lists/musl/2022/01/09/4
Signed-off-by: Hauke Mehrtens <hmehrtens@maxlinear.com>
* tools: sync with upstream
* build: fix issues with targets installed via feeds
- fix including modules.mk when a target is being replaced
- fix calling make targets from target/linux
Signed-off-by: Felix Fietkau <nbd@nbd.name>
* package: sync with upstream
Signed-off-by: Tony Butler <spudz76@gmail.com>
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Signed-off-by: Linhui Liu <liulinhui36@gmail.com>
Signed-off-by: Hauke Mehrtens <hmehrtens@maxlinear.com>
Signed-off-by: Felix Fietkau <nbd@nbd.name>
Co-authored-by: Tony Butler <spudz76@gmail.com>
Co-authored-by: Hauke Mehrtens <hmehrtens@maxlinear.com>
Co-authored-by: Felix Fietkau <nbd@nbd.name>
217 lines
7.9 KiB
Plaintext
217 lines
7.9 KiB
Plaintext
# DO NOT EDIT. This file is generated from Config.src
|
|
#
|
|
# For a description of the syntax of this configuration file,
|
|
# see docs/Kconfig-language.txt.
|
|
#
|
|
|
|
config BUSYBOX_CONFIG_UDHCPD
|
|
bool "udhcpd (21 kb)"
|
|
default BUSYBOX_DEFAULT_UDHCPD
|
|
help
|
|
udhcpd is a DHCP server geared primarily toward embedded systems,
|
|
while striving to be fully functional and RFC compliant.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_UDHCPD_BASE_IP_ON_MAC
|
|
bool "Select IP address based on client MAC"
|
|
default BUSYBOX_DEFAULT_FEATURE_UDHCPD_BASE_IP_ON_MAC
|
|
depends on BUSYBOX_CONFIG_UDHCPD
|
|
help
|
|
If selected, udhcpd will base its selection of IP address to offer
|
|
on the client's hardware address. Otherwise udhcpd uses the next
|
|
consecutive free address.
|
|
|
|
This reduces the frequency of IP address changes for clients
|
|
which let their lease expire, and makes consecutive DHCPOFFERS
|
|
for the same client to (almost always) contain the same
|
|
IP address.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_UDHCPD_WRITE_LEASES_EARLY
|
|
bool "Rewrite lease file at every new acknowledge"
|
|
default BUSYBOX_DEFAULT_FEATURE_UDHCPD_WRITE_LEASES_EARLY
|
|
depends on BUSYBOX_CONFIG_UDHCPD
|
|
help
|
|
If selected, udhcpd will write a new file with leases every
|
|
time a new lease has been accepted, thus eliminating the need
|
|
to send SIGUSR1 for the initial writing or updating. Any timed
|
|
rewriting remains undisturbed.
|
|
|
|
config BUSYBOX_CONFIG_DHCPD_LEASES_FILE
|
|
string "Absolute path to lease file"
|
|
default BUSYBOX_DEFAULT_DHCPD_LEASES_FILE
|
|
depends on BUSYBOX_CONFIG_UDHCPD
|
|
help
|
|
udhcpd stores addresses in a lease file. This is the absolute path
|
|
of the file. Normally it is safe to leave it untouched.
|
|
|
|
config BUSYBOX_CONFIG_DUMPLEASES
|
|
bool "dumpleases (5.1 kb)"
|
|
default BUSYBOX_DEFAULT_DUMPLEASES
|
|
help
|
|
dumpleases displays the leases written out by the udhcpd.
|
|
Lease times are stored in the file by time remaining in lease, or
|
|
by the absolute time that it expires in seconds from epoch.
|
|
|
|
config BUSYBOX_CONFIG_DHCPRELAY
|
|
bool "dhcprelay (5.2 kb)"
|
|
default BUSYBOX_DEFAULT_DHCPRELAY
|
|
help
|
|
dhcprelay listens for DHCP requests on one or more interfaces
|
|
and forwards these requests to a different interface or DHCP
|
|
server.
|
|
|
|
config BUSYBOX_CONFIG_UDHCPC
|
|
bool "udhcpc (24 kb)"
|
|
default BUSYBOX_DEFAULT_UDHCPC
|
|
help
|
|
udhcpc is a DHCP client geared primarily toward embedded systems,
|
|
while striving to be fully functional and RFC compliant.
|
|
|
|
The udhcp client negotiates a lease with the DHCP server and
|
|
runs a script when a lease is obtained or lost.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_UDHCPC_ARPING
|
|
bool "Verify that the offered address is free, using ARP ping"
|
|
default BUSYBOX_DEFAULT_FEATURE_UDHCPC_ARPING
|
|
depends on BUSYBOX_CONFIG_UDHCPC
|
|
help
|
|
If selected, udhcpc will send ARP probes and make sure
|
|
the offered address is really not in use by anyone. The client
|
|
will DHCPDECLINE the offer if the address is in use,
|
|
and restart the discover process.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_UDHCPC_SANITIZEOPT
|
|
bool "Do not pass malformed host and domain names"
|
|
default BUSYBOX_DEFAULT_FEATURE_UDHCPC_SANITIZEOPT
|
|
depends on BUSYBOX_CONFIG_UDHCPC
|
|
help
|
|
If selected, udhcpc will check some options (such as option 12 -
|
|
hostname) and if they don't look like valid hostnames
|
|
(for example, if they start with dash or contain spaces),
|
|
they will be replaced with string "bad" when exporting
|
|
to the environment.
|
|
|
|
config BUSYBOX_CONFIG_UDHCPC_DEFAULT_SCRIPT
|
|
string "Absolute path to config script"
|
|
default BUSYBOX_DEFAULT_UDHCPC_DEFAULT_SCRIPT
|
|
depends on BUSYBOX_CONFIG_UDHCPC
|
|
help
|
|
This script is called after udhcpc receives an answer. See
|
|
examples/udhcp for a working example. Normally it is safe
|
|
to leave this untouched.
|
|
|
|
config BUSYBOX_CONFIG_UDHCPC6_DEFAULT_SCRIPT
|
|
string "Absolute path to config script for IPv6"
|
|
default BUSYBOX_DEFAULT_UDHCPC6_DEFAULT_SCRIPT
|
|
depends on BUSYBOX_CONFIG_UDHCPC6
|
|
|
|
# udhcpc6 config is inserted here:
|
|
config BUSYBOX_CONFIG_UDHCPC6
|
|
bool "udhcpc6 (21 kb)"
|
|
default BUSYBOX_DEFAULT_UDHCPC6
|
|
depends on BUSYBOX_CONFIG_FEATURE_IPV6
|
|
help
|
|
udhcpc6 is a DHCPv6 client
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_UDHCPC6_RFC3646
|
|
bool "Support RFC 3646 (DNS server and search list)"
|
|
default BUSYBOX_DEFAULT_FEATURE_UDHCPC6_RFC3646
|
|
depends on BUSYBOX_CONFIG_UDHCPC6
|
|
help
|
|
List of DNS servers and domain search list can be requested with
|
|
"-O dns" and "-O search". If server gives these values,
|
|
they will be set in environment variables "dns" and "search".
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_UDHCPC6_RFC4704
|
|
bool "Support RFC 4704 (Client FQDN)"
|
|
default BUSYBOX_DEFAULT_FEATURE_UDHCPC6_RFC4704
|
|
depends on BUSYBOX_CONFIG_UDHCPC6
|
|
help
|
|
You can request FQDN to be given by server using "-O fqdn".
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_UDHCPC6_RFC4833
|
|
bool "Support RFC 4833 (Timezones)"
|
|
default BUSYBOX_DEFAULT_FEATURE_UDHCPC6_RFC4833
|
|
depends on BUSYBOX_CONFIG_UDHCPC6
|
|
help
|
|
You can request POSIX timezone with "-O tz" and timezone name
|
|
with "-O timezone".
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_UDHCPC6_RFC5970
|
|
bool "Support RFC 5970 (Network Boot)"
|
|
default BUSYBOX_DEFAULT_FEATURE_UDHCPC6_RFC5970
|
|
depends on BUSYBOX_CONFIG_UDHCPC6
|
|
help
|
|
You can request bootfile-url with "-O bootfile_url" and
|
|
bootfile-params with "-O bootfile_params".
|
|
|
|
comment "Common options for DHCP applets"
|
|
depends on BUSYBOX_CONFIG_UDHCPD || BUSYBOX_CONFIG_UDHCPC || BUSYBOX_CONFIG_UDHCPC6 || BUSYBOX_CONFIG_DHCPRELAY
|
|
|
|
config BUSYBOX_CONFIG_UDHCPC_DEFAULT_INTERFACE
|
|
string "Default interface name"
|
|
default BUSYBOX_DEFAULT_UDHCPC_DEFAULT_INTERFACE
|
|
depends on BUSYBOX_CONFIG_UDHCPC || BUSYBOX_CONFIG_UDHCPC6
|
|
help
|
|
The interface that will be used if no other interface is
|
|
specified on the commandline.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_UDHCP_PORT
|
|
bool "Enable '-P port' option for udhcpd and udhcpc"
|
|
default BUSYBOX_DEFAULT_FEATURE_UDHCP_PORT
|
|
depends on BUSYBOX_CONFIG_UDHCPD || BUSYBOX_CONFIG_UDHCPC || BUSYBOX_CONFIG_UDHCPC6
|
|
help
|
|
At the cost of ~300 bytes, enables -P port option.
|
|
This feature is typically not needed.
|
|
|
|
config BUSYBOX_CONFIG_UDHCP_DEBUG
|
|
int "Maximum verbosity level (0..9)"
|
|
default BUSYBOX_DEFAULT_UDHCP_DEBUG
|
|
range 0 9
|
|
depends on BUSYBOX_CONFIG_UDHCPD || BUSYBOX_CONFIG_UDHCPC || BUSYBOX_CONFIG_UDHCPC6 || BUSYBOX_CONFIG_DHCPRELAY
|
|
help
|
|
Verbosity can be increased with multiple -v options.
|
|
This option controls how high it can be cranked up.
|
|
|
|
Bigger values result in bigger code. Levels above 1
|
|
are very verbose and useful for debugging only.
|
|
|
|
config BUSYBOX_CONFIG_UDHCPC_SLACK_FOR_BUGGY_SERVERS
|
|
int "DHCP options slack buffer size"
|
|
default BUSYBOX_DEFAULT_UDHCPC_SLACK_FOR_BUGGY_SERVERS
|
|
range 0 924
|
|
depends on BUSYBOX_CONFIG_UDHCPD || BUSYBOX_CONFIG_UDHCPC
|
|
help
|
|
Some buggy DHCP servers send DHCP offer packets with option
|
|
field larger than we expect (which might also be considered a
|
|
buffer overflow attempt). These packets are normally discarded.
|
|
If circumstances beyond your control force you to support such
|
|
servers, this may help. The upper limit (924) makes udhcpc accept
|
|
even 1500 byte packets (maximum-sized ethernet packets).
|
|
|
|
This option does not make udhcp[cd] emit non-standard
|
|
sized packets.
|
|
|
|
Known buggy DHCP servers:
|
|
3Com OfficeConnect Remote 812 ADSL Router:
|
|
seems to confuse maximum allowed UDP packet size with
|
|
maximum size of entire IP packet, and sends packets
|
|
which are 28 bytes too large.
|
|
Seednet (ISP) VDSL: sends packets 2 bytes too large.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_UDHCP_RFC3397
|
|
bool "Support RFC 3397 domain search options"
|
|
default BUSYBOX_DEFAULT_FEATURE_UDHCP_RFC3397
|
|
depends on BUSYBOX_CONFIG_UDHCPD || BUSYBOX_CONFIG_UDHCPC
|
|
help
|
|
If selected, both client and server will support passing of domain
|
|
search lists via option 119, specified in RFC 3397,
|
|
and SIP servers option 120, specified in RFC 3361.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_UDHCP_8021Q
|
|
bool "Support 802.1Q VLAN parameters options"
|
|
default BUSYBOX_DEFAULT_FEATURE_UDHCP_8021Q
|
|
depends on BUSYBOX_CONFIG_UDHCPD || BUSYBOX_CONFIG_UDHCPC
|
|
help
|
|
If selected, both client and server will support passing of VLAN
|
|
ID and priority via options 132 and 133 as per 802.1Q.
|