summaryrefslogtreecommitdiffstats
path: root/package/busybox/patches/243-udhcpc_changed_ifindex.patch
diff options
context:
space:
mode:
authorflorian <florian@3c298f89-4303-0410-b956-a3cf2f4a3e73>2009-05-25 13:13:10 +0000
committerflorian <florian@3c298f89-4303-0410-b956-a3cf2f4a3e73>2009-05-25 13:13:10 +0000
commit2ed8e5602fadd4d03e0ed0f3af3041d874b56e66 (patch)
tree26fa97e257f3168ed01e0484c676ea35a2e6af1c /package/busybox/patches/243-udhcpc_changed_ifindex.patch
parenta210854b74cfa94a76a8c967439d795052346d48 (diff)
I recently came across an ar7 device which has the vlynq hardwired
so that the clocks are always generated by the remote device instead of the local one. Upon initialization the current version of vlynq driver disables remote clock generation and causes the entire bus to hang on my device. This patch adds support for detecting which device (local or remote) is responsible of clock generation and implements clock initialization based on detection result. Signed-off-by: Antti Seppala <a.seppala at gmail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@16049 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'package/busybox/patches/243-udhcpc_changed_ifindex.patch')
0 files changed, 0 insertions, 0 deletions