OpenWRT - Revision history

Amallen at 20:06, 24 June 2008

2008-06-24T20:06:11Z

Michael: Reverted edits by 70.87.7.56 (Talk); changed back to last version by Michael

2007-10-10T22:30:25Z

Reverted edits by 70.87.7.56 (Talk); changed back to last version by Michael

70.87.7.56 at 21:49, 10 October 2007

2007-10-10T21:49:52Z

Michael at 23:17, 18 July 2007

2007-07-18T23:17:42Z

Phinze: tone it down a bit ;)

2007-06-20T19:24:53Z

tone it down a bit ;)

Phinze: added related links and edited

2007-06-20T17:01:05Z

added related links and edited

Phinze: Starting with some basics

2006-09-01T05:11:41Z

Starting with some basics

New page

OpenWRT is essentially a Linux distribution for embedded systems, specifically routers. It has an incredibly modular structure which allows it to build easily for dozens of different devices and makes package selection easy. It also makes browsing around its source relatively difficult. When you first download a copy of "White Russian", the stable branch of OpenWRT, you don't have a linux kernel, or even a toolchain, but you have its unique build system, which is everything you need to build a firmware image. As far as we can tell it:

* Downloads the correct toolchain
* Builds the toolchain
* Downloads a linux kernel
* Downloads your selected packages
* Uses the toolchain to build the kernel / packages
* Smushes everything together into several flavors of executable (depending on which file system you desire)
* Also creates versions with proper Linksys headers so that they can be uploaded though the web interface as "legit" firmware upgrades

So though the precious bounty is not in the original download, once you complete the build process, the build system leaves the linux source behind in the '''build_mipsel''' directory, and the toolchain is left waiting to be swiped as well.

@@ Line 9: / Line 9: @@
 * Also create versions with proper Linksys headers so that they can be uploaded though the web interface as "legit" firmware upgrades
-So though the precious bounty is not in the original download, once you complete the build process, the build system leaves the linux source behind in the '''build_mipsel''' directory, and the toolchain is left waiting to be swiped as well.  Although we recommend building your own [[HOWTO:Build and Deploy XINU#Cross-Compiler|cross compiler]] which can be more finely tuned.
+So though the precious bounty is not in the original download, once you complete the build process, the build system leaves the linux source behind in the '''build_mipsel''' directory, and the toolchain is left waiting to be swiped as well.  Although we recommend building your own [[HOWTO:Build XINU|cross compiler]] which can be more finely tuned.
 The [[Main Page|Embedded XINU]] project has used OpenWRT's linux source as a reference in our work on implementing XINU for MIPS.

← Older revision		Revision as of 22:30, 10 October 2007
Line 1:		Line 1:
−	~~talidrone~~
	OpenWRT is essentially a Linux distribution for embedded systems, specifically routers. It has an incredibly modular structure which allows it to build easily for dozens of different devices and makes package selection easy. It also makes browsing around its source relatively difficult. When you first download a copy of "White Russian", the stable branch of OpenWRT, you don't have a linux kernel, or even a toolchain, but you have its unique build system, which is everything you need to build a firmware image. As far as we can tell the build process follows these steps:		OpenWRT is essentially a Linux distribution for embedded systems, specifically routers. It has an incredibly modular structure which allows it to build easily for dozens of different devices and makes package selection easy. It also makes browsing around its source relatively difficult. When you first download a copy of "White Russian", the stable branch of OpenWRT, you don't have a linux kernel, or even a toolchain, but you have its unique build system, which is everything you need to build a firmware image. As far as we can tell the build process follows these steps:

← Older revision		Revision as of 21:49, 10 October 2007
Line 1:		Line 1:
		+	talidrone
	OpenWRT is essentially a Linux distribution for embedded systems, specifically routers. It has an incredibly modular structure which allows it to build easily for dozens of different devices and makes package selection easy. It also makes browsing around its source relatively difficult. When you first download a copy of "White Russian", the stable branch of OpenWRT, you don't have a linux kernel, or even a toolchain, but you have its unique build system, which is everything you need to build a firmware image. As far as we can tell the build process follows these steps:		OpenWRT is essentially a Linux distribution for embedded systems, specifically routers. It has an incredibly modular structure which allows it to build easily for dozens of different devices and makes package selection easy. It also makes browsing around its source relatively difficult. When you first download a copy of "White Russian", the stable branch of OpenWRT, you don't have a linux kernel, or even a toolchain, but you have its unique build system, which is everything you need to build a firmware image. As far as we can tell the build process follows these steps:

@@ Line 9: / Line 9: @@
 * Also create versions with proper Linksys headers so that they can be uploaded though the web interface as "legit" firmware upgrades
-So though the precious bounty is not in the original download, once you complete the build process, the build system leaves the linux source behind in the '''build_mipsel''' directory, and the toolchain is left waiting to be swiped as well.
+So though the precious bounty is not in the original download, once you complete the build process, the build system leaves the linux source behind in the '''build_mipsel''' directory, and the toolchain is left waiting to be swiped as well.  Although we recommend building your own [[HOWTO:Build and Deploy XINU#Cross-Compiler|cross compiler]] which can be more finely tuned.
-The Embedded XINU project has used OpenWRT's linux source as a reference in our work on implementing XINU for MIPS.
+The [[Main Page|Embedded XINU]] project has used OpenWRT's linux source as a reference in our work on implementing XINU for MIPS.
 == Related Links ==
 * http://www.openwrt.org - OpenWRT home page
 * http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/WRT54GL - information on our primary router

@@ Line 11: / Line 11: @@
 So though the precious bounty is not in the original download, once you complete the build process, the build system leaves the linux source behind in the '''build_mipsel''' directory, and the toolchain is left waiting to be swiped as well.
-The Embedded XINU project has used OpenWRT's linux source extensively as a reference in our work on implementing XINU for MIPS.
+The Embedded XINU project has used OpenWRT's linux source as a reference in our work on implementing XINU for MIPS.
 == Related Links ==
 * http://www.openwrt.org - OpenWRT home page
 * http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/WRT54GL - information on our primary router

@@ Line 1: / Line 1: @@
-OpenWRT is essentially a Linux distribution for embedded systems, specifically routers.  It has an incredibly modular structure which allows it to build easily for dozens of different devices and makes package selection easy.  It also makes browsing around its source relatively difficult.  When you first download a copy of "White Russian", the stable branch of OpenWRT, you don't have a linux kernel, or even a toolchain, but you have its unique build system, which is everything you need to build a firmware image.  As far as we can tell it:
+OpenWRT is essentially a Linux distribution for embedded systems, specifically routers.  It has an incredibly modular structure which allows it to build easily for dozens of different devices and makes package selection easy.  It also makes browsing around its source relatively difficult.  When you first download a copy of "White Russian", the stable branch of OpenWRT, you don't have a linux kernel, or even a toolchain, but you have its unique build system, which is everything you need to build a firmware image.  As far as we can tell the build process follows these steps:
-* Downloads the correct toolchain
+* Download the correct toolchain
-* Builds the toolchain
+* Build the toolchain
-* Downloads a linux kernel
+* Download a linux kernel
-* Downloads your selected packages
+* Download selected packages
-* Uses the toolchain to build the kernel / packages
+* Use the toolchain to build the kernel / packages
-* Smushes everything together into several flavors of executable (depending on which file system you desire)
+* Smush everything together into several flavors of executable (depending on file system)
-* Also creates versions with proper Linksys headers so that they can be uploaded though the web interface as "legit" firmware upgrades
+* Also create versions with proper Linksys headers so that they can be uploaded though the web interface as "legit" firmware upgrades
 So though the precious bounty is not in the original download, once you complete the build process, the build system leaves the linux source behind in the '''build_mipsel''' directory, and the toolchain is left waiting to be swiped as well.