| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
config append optional (leave enabled on x86)
SVN-Revision: 12657
|
|
|
|
| |
SVN-Revision: 12499
|
|
|
|
| |
SVN-Revision: 12276
|
|
|
|
|
|
| |
#2788)
SVN-Revision: 11935
|
|
|
|
| |
SVN-Revision: 11909
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
against 2.4.35 and repaired for obvious breakage (didn't use its device table, etc.).
Changes from Linksys tree:
- Remove 'vendor' and 'product' parameters; these aren't used in the
mainstream driver and seem to only have served to break it.
- Remove bogus 'sierra_device_ids' table, used with above.
- Changed references to 'sierra_device_ids' back to id_table
- Changed non-standard CONFIG_USB_SERIAL_SIERRA_3G (line 886) to
current module standard CONFIG_USB_SERIAL_SIERRAWIRELESS
- Added #include to enable pl2303 hack to remain until I can figure
out if it's still necessary.
Signed-off-by: RB <aoz.syn@gmail.com>
SVN-Revision: 11899
|
|
|
|
|
|
| |
supported platforms (WRT54G3G) by adding direct support for the Sierra Wireless 3G modems. Signed-off-by: RB <aoz.syn@gmail.com>
SVN-Revision: 11898
|
|
|
|
|
|
|
|
|
|
|
| |
I noticed my wrt350n would not reliably reboot after entering
the reboot command. I found this code in the source for the
wrt600n. It corrects the problem, and the wrt350n reboots
reliably now.
Signed-off-by: Ben Pfountz <netprince (at) vt (dot) edu>
SVN-Revision: 11470
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch allows the bcm57xx module to work correctly with failsafe mode.
insmod doesn't return an error when a module loads but doesn't detect a switch.
I added the check_module function to load the module, then make sure
it doesn't just exit immediately. This allows preinit to only attempt to
load the bcm57xx module when switch-robo and switch-adm dont detect a switch.
The activate_gpio parameter to bcm57xx simply instructs the module to attempt
to activate the switch via gpio before probing for the switch.
Tested on wrt350n.
Signed-off-by: Ben Pfountz <netprince (at) vt (dot) edu>
SVN-Revision: 11468
|
|
|
|
|
|
|
|
|
| |
Update the netconfig script to support boardtype 0x478. I've tested this
on the wrt350n, hopefully it will match the 600n as well.
Signed-off-by: Ben Pfountz <netprince (at) vt (dot) edu>
SVN-Revision: 11467
|
|
|
|
| |
SVN-Revision: 11340
|
|
|
|
| |
SVN-Revision: 11275
|
|
|
|
| |
SVN-Revision: 11214
|
|
|
|
|
|
| |
Pfountz <netprince@vt.edu>
SVN-Revision: 11070
|
|
|
|
| |
SVN-Revision: 10695
|
|
|
|
| |
SVN-Revision: 10694
|
|
|
|
| |
SVN-Revision: 10693
|
|
|
|
| |
SVN-Revision: 10205
|
|
|
|
| |
SVN-Revision: 10142
|
|
|
|
|
|
| |
broadcom-wl to a contributed version (v4.150.10.5) - no bcm57xx support yet, will follow shortly
SVN-Revision: 10137
|
|
|
|
| |
SVN-Revision: 10097
|
|
|
|
| |
SVN-Revision: 9684
|
|
|
|
|
|
| |
further
SVN-Revision: 9556
|
|
|
|
| |
SVN-Revision: 9533
|
|
|
|
| |
SVN-Revision: 9523
|
|
|
|
| |
SVN-Revision: 9494
|
|
|
|
| |
SVN-Revision: 9069
|
|
|
|
| |
SVN-Revision: 9015
|
|
|
|
| |
SVN-Revision: 8949
|
|
|
|
| |
SVN-Revision: 8848
|
|
|
|
| |
SVN-Revision: 8718
|
|
|
|
| |
SVN-Revision: 8695
|
|
|
|
|
|
| |
override many target settings, including arch - merge adm5120, adm5120eb. target profiles still need to be adapted for subtargets
SVN-Revision: 8694
|
|
|
|
| |
SVN-Revision: 8690
|
|
|
|
| |
SVN-Revision: 8654
|
|
|
|
|
|
| |
(the -2.4 will be included in the board name here). CONFIG_LINUX_<ver>_<board> becomes CONFIG_TARGET_<board>, same for profiles.
SVN-Revision: 8653
|
|
|
|
| |
SVN-Revision: 8483
|
|
|
|
| |
SVN-Revision: 8482
|
|
|
|
| |
SVN-Revision: 8450
|
|
|
|
|
|
| |
http://lists.openwrt.org/pipermail/openwrt-devel/2007-August/001159.html
SVN-Revision: 8362
|
|
|
|
|
|
| |
the moment
SVN-Revision: 7870
|
|
|
|
|
|
| |
atheros as well as soon as i've added support for it
SVN-Revision: 7810
|
|
|
|
|
|
| |
related bugs (#1888)
SVN-Revision: 7731
|
|
|
|
| |
SVN-Revision: 7722
|
|
|
|
| |
SVN-Revision: 7623
|
|
|
|
| |
SVN-Revision: 7622
|
|
|
|
| |
SVN-Revision: 7486
|
|
|
|
| |
SVN-Revision: 7275
|
|
|
|
|
|
|
|
|
|
| |
We switched over to appending the jffs2 eof mark to the squashfs images,
but since the squashfs is not always aligned to eraseblocksize, the eof
mark landed in the wrong place. This commit adds an extra flag to the
trx utility that can append extra data to a partition with alignment.
This is used to place the jffs2 eof mark at the right offset.
SVN-Revision: 7253
|
|
|
|
| |
SVN-Revision: 7176
|