mirror of
git://projects.qi-hardware.com/openwrt-xburst.git
synced 2024-11-24 06:38:27 +02:00
OpenWrt XBurst, development environment for Qi Hardware device.
http://projects.qi-hardware.com/index.php/p/openwrt-xburst/
128434cb23
This is the bcm57xx package. I have tested default vlan functions, but I dont have the equipment to test more advanced setups. The default vlan setup seems to be working fine. I also added the activate_gpio parameter which will make the driver activate the switch via gpio before probing for it. I'm not sure which method is best for autoload. For the wrt350n, I need the activate_gpio parameter. But its probably not a good idea to add that to the autoload file. On a system without a bcm57xx switch, isn't it a bad idea to mess with the gpios looking for the switch? Ideally, wouldn't it be best to load the bcm57xx module from broadcom-diag, after it has determined which router its on? I tried using 'request_module' from there, but had no success. For now, I am relying on preinit to load the bcm57xx module with activate_gpio param, after it has failed to load switch_robo and switch_adm. Signed-off-by: Ben Pfountz <netprince (at) vt (dot) edu> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@11471 3c298f89-4303-0410-b956-a3cf2f4a3e73 |
||
---|---|---|
docs | ||
include | ||
package | ||
scripts | ||
target | ||
toolchain | ||
tools | ||
.gitignore | ||
BSDmakefile | ||
Config.in | ||
feeds.conf | ||
LICENSE | ||
Makefile | ||
README | ||
rules.mk |
This is the buildsystem for the OpenWrt Linux distribution Please use "make menuconfig" to configure your appreciated configuration for the toolchain and firmware. You need to have installed gcc, binutils, patch, bzip2, flex, bison, make, gettext, pkg-config, unzip, libz-dev and libc headers. Simply running 'make' will build your firmware. It will download all sources, build the cross-compile toolchain, the kernel and all choosen applications. You can use scripts/flash.sh for remotely updating your embedded system via tftp. The OpenWrt system is documented in docs/. You will need a LaTeX distribution and the tex4ht package to build the documentation. Type make -C docs/ to build it. Building your own firmware you need to have access to a Linux, BSD or MacOSX system. Cygwin will not be supported because of the lack of case sensitiveness. Sunshine! Your OpenWrt Project http://openwrt.org