BRN:Software:Build and Distribution: Difference between revisions
Jump to navigation
Jump to search
Line 17: | Line 17: | ||
#<div style='margin-bottom:2em;'> The most of BRN's functionality is implemented with the help of the '''[[BRN:Software:Build and Distribution:click|click modular router framework]]'''. Read how to build the click software for userspace and/or as linuxmodule. /////// brn-patches???</div> |
#<div style='margin-bottom:2em;'> The most of BRN's functionality is implemented with the help of the '''[[BRN:Software:Build and Distribution:click|click modular router framework]]'''. Read how to build the click software for userspace and/or as linuxmodule. /////// brn-patches???</div> |
||
#<div style='margin-bottom:2em;'> '''[[BRN:Software:Build and Distribution:Madwifi|Madwifi]]''' is the project name for the Atheros open source network device driver. The build depends on the linux kernel source tree.</div> |
#<div style='margin-bottom:2em;'> '''[[BRN:Software:Build and Distribution:Madwifi|Madwifi]]''' is the project name for the Atheros open source network device driver. The build depends on the linux kernel source tree.</div> |
||
#<div style='margin-bottom:2em;'> SDP</div> |
#<div style='margin-bottom:2em;'> For updates via mesh network you will need '''[[BRN:Software:Build and Distribution:BRN-SDP|BRN-SDP]]'''.</div> |
||
#<div style='margin-bottom:2em;'> OpenWGT-scripts</div> |
#<div style='margin-bottom:2em;'> Like every UNIX system the BRN meshnodes need some '''[[BRN:Software:Build and Distribution:OpenWGT-scripts|initscripts]]''' at boot time.</div> |
||
#<div style='margin-bottom:2em;'> Build an image</div> |
#<div style='margin-bottom:2em;'> Every target platfrom uses it's own way to install/update the base image. '''[[BRN:Software:Build and Distribution:Build and install an image|Build and install an image]]''' could be interesting for deployment of BRN images.</div> |
||
#<div style='margin-bottom:2em;'> Installing/Flashing image</div> |
Revision as of 12:22, 1 September 2006
Requirements
For desired new platforms the following critical items are required:
- GCC (cross) compiler to create binary code for the target platform
- Linux kernel (version 2.6) with support for target platform
- click (modular router) patch (hopefully working on target platform? x86 and mips tested)
- Wireless network device supporting to send raw frames (e.g. Atheros cards)
Build software
The build process to get a ready-to-run BRN software package is described in general and examples are made for the Netgear's WGT634U mips platform.
- The basic software you will need is a Compiler for the new target platform. If you do not have a running UNIX system on the target platform you will need a cross-compiler, which runs on your development machine (e.g. a x86 Linux system) and creates binary code for the target platform. Read the linked page to get details for the WGT634U.
- (optional) Build a Standarized Development Environment.
- The Linux operating system controls the execution of all BRN software and provides different device drivers for the hardware components of the target platform. You will need a (cross) compiler to build a Linux kernel. Notice: For some platform you will need extra kernel-patches to get full target platform support!
- The most of BRN's functionality is implemented with the help of the click modular router framework. Read how to build the click software for userspace and/or as linuxmodule. /////// brn-patches???
- Madwifi is the project name for the Atheros open source network device driver. The build depends on the linux kernel source tree.
- For updates via mesh network you will need BRN-SDP.
- Like every UNIX system the BRN meshnodes need some initscripts at boot time.
- Every target platfrom uses it's own way to install/update the base image. Build and install an image could be interesting for deployment of BRN images.