| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
SVN-Revision: 23930
|
|
|
|
| |
SVN-Revision: 23929
|
|
|
|
| |
SVN-Revision: 23928
|
|
|
|
| |
SVN-Revision: 23927
|
|
|
|
| |
SVN-Revision: 23926
|
|
|
|
| |
SVN-Revision: 23925
|
|
|
|
| |
SVN-Revision: 23924
|
|
|
|
| |
SVN-Revision: 23923
|
|
|
|
|
|
|
|
| |
Fixes dependencies, and properly labels the module as GPL (thanks, Felix!).
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 23922
|
|
|
|
| |
SVN-Revision: 23921
|
|
|
|
| |
SVN-Revision: 23920
|
|
|
|
| |
SVN-Revision: 23919
|
|
|
|
| |
SVN-Revision: 23918
|
|
|
|
| |
SVN-Revision: 23917
|
|
|
|
|
|
|
|
|
|
|
| |
Since the net5501 doesn't have a VGA port, it doesn't need HID support either --
all console access will be over a serial port.
Also add FEATURES to it as well.
Signed-of-by: Philip Prindeville <philip@redfish-solutions.com>
SVN-Revision: 23916
|
|
|
|
| |
SVN-Revision: 23914
|
|
|
|
| |
SVN-Revision: 23912
|
|
|
|
|
|
|
|
|
|
| |
Readd the workarround from the old version again which was removed in r22296 and refresh the patches.
This should close #7874
Thank you Russell Senior for testing.
SVN-Revision: 23911
|
|
|
|
| |
SVN-Revision: 23908
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
During the first OpenWrt boot after a clean flash (when the jffs2
partition is not yet initialized) tmpfs is used instead of the usual
jffs2 overlay filesystem. If this tmpfs is mounted with default
options, all directories created there (/etc, /etc/config, other
subdirectories in /etc) get permissions 1777 by default, and these
permissions then persist in the created jffs2 at least until
subsequent sysupgrade. Mounting tmpfs with mode=0755 fixes the
permission problem.
Signed-off-by: Sergey Vlasov <vsu@altlinux.ru>
SVN-Revision: 23906
|
|
|
|
|
|
| |
pthreads always resulted in 0 breaking various programs like transmission and collectd. This patch is not 100% thread safe but it brings back threading into a usable state for now.
SVN-Revision: 23905
|
|
|
|
| |
SVN-Revision: 23904
|
|
|
|
| |
SVN-Revision: 23903
|
|
|
|
| |
SVN-Revision: 23902
|
|
|
|
| |
SVN-Revision: 23901
|
|
|
|
| |
SVN-Revision: 23900
|
|
|
|
|
|
|
| |
For kernel 2.6.36 some additional pcmcia backpots would be needed, but
this should not depend on pcmcia.
SVN-Revision: 23899
|
|
|
|
| |
SVN-Revision: 23898
|
|
|
|
| |
SVN-Revision: 23897
|
|
|
|
| |
SVN-Revision: 23895
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
b65c7b2c79debcb9017e31913e01eeaa280106fb, the implicit search path can be disabled by not #defining __LDSO_SEARCH_INTERP_PATH__. This causes _dl_ldsopath to never be set, so it remains NULL. _dl_ldsopath is still used when __LDSO_LDD_SUPPORT__ is #defined, to strip the path off of the beginning of the absolute path to the ld.so interpreter in use for printing. The _dl_strlen will crash with a NULL argument.
Rather than relying on _dl_ldsopath, this change causes ldd to compute
the interpreter's basename directly.
glibc ld.so seems to print the full path to the interpreter without
any computed basename or =>. I personally prefer glibc's behavior, but
to preserve backwards compatibility with uClibc ld.so, the existing
format with the computed basename, =>, and full path is used here. This
enables simpler (and unchanged) text processing in a pipeline.
Signed-off-by: Mark Mentovai <mark at moxienet.com>
SVN-Revision: 23892
|
|
|
|
| |
SVN-Revision: 23891
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I discovered another bug in the ath9k WNDR3700 quirk fix from r23822.
ath9k_hw_apply_gpio_override was testing the original value of gpio_mask
to determine which bits were appropriate, instead of testing the shifted
value. Because bit 0 is always clear in the original value, this
resulted in no calls to set the GPIOs, an improperly-configured radio,
and reduced RSSI on other systems listening to the radio.
Signed-off-by: Mark Mentovai <mark@moxienet.com>
SVN-Revision: 23890
|
|
|
|
| |
SVN-Revision: 23889
|
|
|
|
| |
SVN-Revision: 23888
|
|
|
|
| |
SVN-Revision: 23887
|
|
|
|
| |
SVN-Revision: 23886
|
|
|
|
| |
SVN-Revision: 23885
|
|
|
|
| |
SVN-Revision: 23884
|
|
|
|
| |
SVN-Revision: 23883
|
|
|
|
| |
SVN-Revision: 23882
|
|
|
|
| |
SVN-Revision: 23881
|
|
|
|
|
|
|
|
|
|
|
| |
For WNDR3700, use green for 1Gb/s and amber for 100Mb/s and 10Mb/s on
the four LAN port switch LEDs. The LEDs will be lit to indicate a link
and will blink to indicate activity. This matches the stock firmware
and the description printed on the label on the unit's underside.
Signed-off-by: Mark Mentovai <mark@moxienet.com>
SVN-Revision: 23879
|
|
|
|
|
|
| |
submitter's request
SVN-Revision: 23878
|
|
|
|
|
|
|
|
|
|
|
| |
Make the WiFi LEDs blink for activity on the WNDR3700, matching the
stock firmware and user expectations. The green 2.4GHz and blue 5GHz
LEDs will illuminate with the radio on, and will blink to indicate
transmission and reception.
Signed-off-by: Mark Mentovai <mark@moxienet.com>
SVN-Revision: 23877
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The WNDR3700's art/caldata partition contains three MAC addresses at
offsets 0, 6, and 12, used for eth0/wlan0 (shared), eth1, and wlan1,
respectively. The existing code configures eth1's MAC address by adding
1 to eth0's instead of using the value stored in the EEPROM. This patch
causes the stored value to be used directly. (On my WNDR3700s, the three
stored addresses are all sequential anyway.)
Signed-off-by: Mark Mentovai <mark@moxienet.com>
SVN-Revision: 23876
|
|
|
|
|
|
| |
(thx, Mark Mentovai)
SVN-Revision: 23875
|
|
|
|
| |
SVN-Revision: 23870
|
|
|
|
| |
SVN-Revision: 23867
|
|
|
|
| |
SVN-Revision: 23866
|