/openwrt/docs/ |
H A D | submitting-patches.tex | 1 \subsection{How to contribute} 2 OpenWrt is constantly being improved. We'd like as many people to contribute 3 to this as we can get. If you find a change useful, by all means try to get 7 This section tries to lay out a procedure to enable people to submit patches 10 It is important to do all these steps repeatedly: 13 \item \textit{listen} to what other people think. 20 \subsection{Where to liste [all...] |
H A D | working.tex | 1 The following section gives some tips and tricks on how to use efficiently 6 The buildroot allows you to recompile the full environment or only parts of it 9 For instance if you want to recompile the toolchain after you made any change to it 16 Which will clean, compile and install the toolchain. The command actually expands to the 27 Of course, you could only choose to recompile one or several of the toolchain components 36 will clean, compile and install busybox (if selected to be installed on the final rootfs). 38 Supposing that you made changes to the Linux kernel, but do not want to recompile everything, 53 OpenWrt integrates quilt in order to eas [all...] |
H A D | Makefile | 38 You need to install LaTeX to build the OpenWrt documentation \ 41 You need to install PDFLaTeX to build the OpenWrt documentation \ 44 You need to install tex4ht to build the OpenWrt documentation \
|
H A D | build.tex | 1 One of the biggest challenges to getting started with embedded devices is that you 2 cannot just install a copy of Linux and expect to be able to compile a firmware. 3 Even if you did remember to install a compiler and every development tool offered, 4 you still would not have the basic set of tools needed to produce a firmware image. 7 cross compiling you need to produce a new compiler capable of generating code for 8 your embedded platform, and then use it to compile a basic Linux distribution to 17 to be provided with a patched copy of the Linux kernel from the board or chip vendor, 18 but this is also dated and it can be difficult to spo [all...] |
H A D | adding.tex | 2 to its openess as well as the wide variety of platforms it can run on. Many 5 firmware is not really open to the consumer, even if it uses open source software. 10 open-source firmware is de-facto needed for such applications, since you want to 11 be free to use this or that version of a particular reason, be able to correct a 13 that would allow you to create your own and custom firmware and most of the time, 14 when they do, you will most likely not be able to complete the firmware creation process. 18 platforms, known to be running Linux originally. 22 There is a lot of methods to ensure your device is running Linux. Some of them do 23 need your router to b [all...] |
H A D | debugging.tex | 2 development. It might become handy for you to add serial console to your 3 device as well as using JTAG to debug your code. 8 and its pins are routed on the Printed Circuit Board to allow 13 least 4 signals (without modem signaling) to work : VCC, GND, TX and 14 RX. Since your router is very likely to have its I/O pins working at 16 to change the level from 3.3V to your computer level which is usually 22 the top or bottom layer of the PCB, and connected to the TX and RX. 24 Once found, you can easily check where is GND, which is connected to [all...] |
H A D | config.tex | 6 Every option has a name and a value and is assigned to the section 16 Every parameter needs to be a single string and is formatted exactly 22 To be able to load configuration files, you need to include the common 29 Then you can use \texttt{config\_load \textit{<name>}} to load config files. The function 30 first checks for \textit{<name>} as absolute filename and falls back to loading 33 If you want to use special callbacks for sections and/or options, you 34 need to define the following shell functions before running \texttt{config\_load} 41 # commands to be run for every section 45 # commands to b [all...] |
H A D | bugs.tex | 1 OpenWrt as an open source software opens its development to the community by 4 is used as an interface between developers, users and contributors in order to 10 \item developers, able to report, close and fix tickets 11 \item reporters, able to add a comment, patch, or request ticket status 16 A reporter might want to open a ticket for the following reasons: 19 \item a bug affects a specific hardware and/or software and needs to be fixed 27 \item new package to be included in OpenWrt 33 as "accepted" with the developer name. You can add comments at any time to the ticket, 44 \item the problem is very similar to something that has already been reported (duplicate) 48 At the same time, the reporter may want to ge [all...] |
H A D | network.tex | 3 Each interface configuration either refers directly to an ethernet/wifi 4 interface (\texttt{eth0}, \texttt{wl0}, ..) or to a bridge containing multiple interfaces. 18 If you want to use bridging on one or more interfaces, set \texttt{ifname} to a list 24 It is possible to use VLAN tagging on an interface simply by adding the VLAN IDs 25 to it, e.g. \texttt{eth0.15}. These can be nested as well. See the switch section for 51 DHCP currently only accepts \texttt{ipaddr} (IP address to request from the server) 71 The ping interval defaults to 5, but can be changed by appending 72 ",<interval>" to the keepalive value 121 On Broadcom hardware the section name needs to b [all...] |
/openwrt/package/utils/usbreset/ |
H A D | Makefile | 18 TITLE:=Utility to send a USB port reset to a USB device 24 can be used to send a USB port reset to a USB device - 25 useful for debugging or to force re-detection of particular
|
/openwrt/package/libs/libmnl/ |
H A D | Makefile | 36 libmnl is a minimalistic user-space library oriented to Netlink developers. 38 both the Netlink header and TLVs that are repetitive and easy to get wrong. 39 This library aims to provide simple helpers that allows you to re-use code 40 and to avoid re-inventing the wheel. The main features of this library are: 45 tend to hide Netlink details. 47 * Easy to use: the library simplifies the work for Netlink-wise developers. 48 It provides functions to make socket handling, message building, validating, 51 * Easy to re-use: you can use the library to buil [all...] |
/openwrt/package/network/utils/iproute2/files/ |
H A D | 15-teql | 14 logger Adding device $DEVICE to TEQL master $teql
|
/openwrt/package/network/utils/iwcap/ |
H A D | Makefile | 25 and outputs it to pcap format. It gathers recived packets in a fixed ring 26 buffer to dump them on demand which is useful for background monitoring. 27 Alternatively the utility can stream the data to stdout to act as remote
|
/openwrt/package/network/services/ipset-dns/ |
H A D | Makefile | 32 TITLE:=A lightweight DNS forwarder to populate ipsets 39 resolved IPs to a given netfilter ipset. It is designed to be used in
|
/openwrt/package/network/utils/owipcalc/ |
H A D | Makefile | 24 The owipcalc utility supports a number of calculations and tests to work 25 with ip-address ranges, this is useful for scripts that e.g. need to 26 partition ipv6-prefixes into small subnets or to calculate address ranges
|
/openwrt/package/network/services/samba36/ |
H A D | Makefile | 59 SMB protocol for UNIX systems, allowing you to serve files and printers to 61 to as the LanManager or Netbios protocol.
|
/openwrt/include/ |
H A D | depends.mk | 33 $(call debug_eval,$(SUBDIR),r,echo "No need to rebuild $(2)";) \ 37 $(call debug_eval,$(SUBDIR),r,echo "Need to rebuild $(2)";) \
|
/openwrt/package/kernel/trelay/ |
H A D | Makefile | 25 trelay relays ethernet packets between two devices (similar to a bridge), but 26 without any MAC address checks. This makes it possible to bridge client mode 27 or ad-hoc mode wifi devices to ethernet VLANs, assuming the remote end uses 28 the same source MAC address as the device that packets are supposed to exit
|
/openwrt/target/linux/realview/ |
H A D | Makefile | 24 Build images for ARM Ltd. Realview boards to be run with qemu
|
/openwrt/package/kernel/linux/modules/ |
H A D | leds.mk | 36 Kernel module that allows LEDs to blink like heart beat 51 Kernel module that allows LEDs to be controlled by gpio events 66 Kernel module to show morse coded messages on LEDs 81 Kernel module to drive LEDs based on network activity 97 Kernel module to flash LED when a particular packets passing through your machine. 99 For example to create an LED trigger for incoming SSH traffic: 101 Then attach the new trigger to an LED on your system: 118 Kernel module to drive LEDs based on USB device presence/activity 133 Kernel module that allows LEDs to be initialised in the ON state 148 Kernel module that allows LEDs to b [all...] |
/openwrt/package/boot/kobs-ng/ |
H A D | Makefile | 26 TITLE:=Application for writing bootstreams to NAND flash 31 The kobs-ng application writes a bootstream to NAND flash with the proper
|
/openwrt/package/network/ipv6/6to4/ |
H A D | Makefile | 21 TITLE:=IPv6-to-IPv4 configuration support 28 Refer to http://wiki.openwrt.org/doc/uci/network for
|
/openwrt/package/network/utils/resolveip/ |
H A D | Makefile | 25 can be used by scripts to turn host names into numeric 27 has a configurable timeout to guarantee a certain maximum
|
/openwrt/package/system/zram-swap/ |
H A D | Makefile | 27 A script to activate swaping on a compressed zram partition. This 28 could be used to increase the available memory, by using compressed
|
/openwrt/target/linux/adm5120/rb1xx/profiles/ |
H A D | RB1xx.mk | 14 Package set compatible with the RouterBoard RB1xx devices. Contains RouterOS to OpenWrt\\\
|