Generate image for the ALL0239-3G which can be flashed through the
chipset-vendor SDK based firmware's web-interface and bootloader.
The bootloader seems to ignore uImage checksum errors, but does complain about
them once the 0xDEADC0DE was replaced by an actual JFFS2 page.
I'm working on implementing fixtrx for uImage in the mtd package to solve this.
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 33206
rt2x00 still needs some patching as the radio doesn't come to life.
Installation via webflash.
[juhosg: fix whitespace issues, remove rt305x_register_usb
from machine setup because the board has no USB port]
Signed-off-by: Mikko Hissa <mikko.hissa@uta.fi>
SVN-Revision: 33205
This takes the device_id and subsystem_id from the EEPROM, I'll add
the info for other Rt3xxx chips in the next days.
[jow: minor whitespace changes]
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 33199
These are two Atheros modules we are using, just for the cosmetics to make them
show up with the proper names in LuCI.
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 33186
* Creation of uImage for WNR854T only done once (before 2x for jffs2 build and 1x for squashfs build)
* Got rid of unneccessary padding of rootfs partition
* ARM zImages always need a machine id, therefore do not copy generic (=no id) uImage to BIN_DIR, instead copy zImage
* Generalized functions for easier re-using and enhancing (e.g. D-Link DNS 323 implementation would be only a couple lines)
* Copy rootfs partitions to BIN_DIR, just like it is done for D-Link DNS 323
* Use variables to allows easily changing for custom builds, e.g. kernel mtd size for symbols
* Size check of kernel files to avoid builds that break devices
* Use for "-sysupgrade" and "-factory" in image names (like ar71xx, brcm63xx, etc.) to avoid questions about which image to use
Signed-off by: Matthias Buecher <mail@maddes.net>
SVN-Revision: 33174
rssileds is a small user-space process to control LEDs by polling the
signal quality reported by a WiFi interface. By using the iwinfo library,
rssileds is independent of the WiFi driver used.
It supports pwm controlled LEDs and may by used to nicely fade through
all colors in real-time of the rainbow while only wasting very little CPU
time and a small constant amount of system memory.
An example configuration for the ALL0258N will follow in the next patch.
This is a slightly improved version of rssileds, now quality values are
in percent and stuff is written to syslog.
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 33163
In order to get OHCI/EHCI working on the Rt3352, the platform device must be
named so rt3883-?hci will recognize it.
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 33145
As the userspace has no means to determine the maximum possible timeout, use
that as the default and let the userspace lower it when necessary.
As the result the usual OpenWrt install (with busybox's watchdog trying to set
the timeout to 60s on start) is using a 33s timeout on an RT3052 clocked at
384MHz instead of the current 20s default.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
SVN-Revision: 33144
D-Link's DIR-620 allows to flash a uImage directly from its web-interface but
for that the image name should be set to DIR_620.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
SVN-Revision: 33143
Full functionality runtime tested, installation via OEM web-interface requires
a follow-up patch.
Thanks go to Sergey Vasilyugin for his patch that pointed me at the missing
bits (including the antiparallel wps led).
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
SVN-Revision: 33142
I recently experienced this:
configure.ac:1101: the top level
interfaces/Prolog/Ciao/Makefile.am:168: `pkglibdir' is not a legitimate directory for `DATA'
interfaces/Prolog/GNU/Makefile.am:167: `pkglibdir' is not a legitimate directory for `DATA'
interfaces/Prolog/SICStus/Makefile.am:71: `pkglibdir' is not a legitimate directory for `DATA'
interfaces/Prolog/SWI/Makefile.am:187: `pkglibdir' is not a legitimate directory for `DATA'
interfaces/Prolog/XSB/Makefile.am:186: `pkglibdir' is not a legitimate directory for `DATA'
interfaces/Prolog/YAP/Makefile.am:176: `pkglibdir' is not a legitimate directory for `DATA'
make[4]: *** [Makefile.in] Error 1
Found this on google:
http://bugs.mysql.com/bug.php?id=63898
And used this to fix it:
fgrep -rlZ pkglib_DATA --include Makefile.am . | xargs -0 sed -i 's/pkglib_DATA/pkgdata_DATA/g'
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 33141
Fixes this section mismatch warning:
WARNING: vmlinux.o(.meminit.text+0xb14): Section mismatch in reference
from the function memblock_insert_region() to the function
.init.text:crashlog_init_memblock()
The function __meminit memblock_insert_region() references
a function __init crashlog_init_memblock().
If crashlog_init_memblock is only used by memblock_insert_region then
annotate crashlog_init_memblock with a matching annotation.
Also, remove the __init annotations from 'include/linux/crashlog.h'
SVN-Revision: 33137
Hauke Mehrtens
Gabor Juhos
Jo-Philipp Wich
Felix Fietkau
John Crispin
Florian Fainelli