[OpenWrt-Devel] adding tp-link wr740n v5.0 support
Hello, so i just got the v5.0 version of tp-link wr740n and it seems its not a 2 mb flash and 16 mb ram chinese version like stated in the wiki. Took a look at the download page for the firmware at www.tp-link.ro and the firmware looks like a 4 mb flash variant. Here is binwalk of it: [dani@x220 Downloads]$ binwalk wr740nv5_wr741ndv5_en_3_16_9_up_boot\(150312\).bin DECIMAL HEXADECIMAL DESCRIPTION 4 0x4 TP-Link firmware header, firmware version: 3.16.9, image version: "ver. 1.0", product ID: 0x745, product version: 1, kernel load address: 0x80002000, kernel entry point: 0x801D74B0, kernel offset: 512, kernel length: 895122, rootfs offset: 1048576, rootfs length: 2883584, bootloader offset: 0, bootloader length: 48518 14224 0x3790 U-Boot version string, "U-Boot 1.1.4 (Mar 12 2015 - 16:40:24)" 15568 0x3CD0 uImage header, header size: 64 bytes, header CRC: 0xA334F831, created: Thu Mar 12 10:40:25 2015, image size: 33398 bytes, Data Address: 0x8001, Entry Point: 0x8001, data CRC: 0xC9CFC8E6, OS: Linux, CPU: MIPS, image type: Firmware Image, compression type: lzma, image name: "u-boot image" 15632 0x3D10 LZMA compressed data, properties: 0x5D, dictionary size: 33554432 bytes, uncompressed size: 95708 bytes 1315880x20204 TP-Link firmware header, firmware version: 3.16.9, image version: "ver. 1.0", product ID: 0x745, product version: 1, kernel load address: 0x80002000, kernel entry point: 0x801D74B0, kernel offset: 512, kernel length: 895122, rootfs offset: 1048576, rootfs length: 2883584, bootloader offset: 0, bootloader length: 0 1320960x20400 LZMA compressed data, properties: 0x5D, dictionary size: 33554432 bytes, uncompressed size: 2589532 bytes 1180160 0x120200Squashfs filesystem, little endian, version 4.0, compression:lzma, size: 2344073 bytes, 566 inodes, blocksize: 131072 bytes, created: Thu Mar 12 10:48:34 2015 uncompressing the root shows the following 2.6.31 specific atheros kernel modules: ag7240_mod.ko, ath_rate_atheros.ko My question to the list is: would i manage to produce a valid firmware if i just replicate the patches from https://dev.openwrt.org/attachment/ticket/10492/tl-wr740n-v4.support.final.patch but with v5 related details added? Thanks! ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] libubox: cmake: Add BUILD_EXAMPLES option
Add ability to skip building the examples. The default value is ON to follow the original cmake behavior. Signed-off-by: Nikolay Dimitrov --- CMakeLists.txt |1 + examples/CMakeLists.txt | 28 +++- 2 files changed, 16 insertions(+), 13 deletions(-) diff --git a/CMakeLists.txt b/CMakeLists.txt index 38709ec..ecca3e9 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -6,6 +6,7 @@ PROJECT(ubox C) ADD_DEFINITIONS(-Os -Wall -Werror --std=gnu99 -g3 -Wmissing-declarations) OPTION(BUILD_LUA "build Lua plugin" ON) +OPTION(BUILD_EXAMPLES "build examples" ON) INCLUDE(FindPkgConfig) PKG_SEARCH_MODULE(JSONC json-c) diff --git a/examples/CMakeLists.txt b/examples/CMakeLists.txt index 6399c7a..a635535 100644 --- a/examples/CMakeLists.txt +++ b/examples/CMakeLists.txt @@ -1,21 +1,23 @@ cmake_minimum_required(VERSION 2.6) -PROJECT(ubox-examples C) -ADD_DEFINITIONS(-O1 -Wall -Werror --std=gnu99 -g3) +IF (BUILD_EXAMPLES) +PROJECT(ubox-examples C) +ADD_DEFINITIONS(-O1 -Wall -Werror --std=gnu99 -g3) -INCLUDE_DIRECTORIES(${CMAKE_CURRENT_SOURCE_DIR}/..) -LINK_DIRECTORIES(${CMAKE_CURRENT_SOURCE_DIR}/..) +INCLUDE_DIRECTORIES(${CMAKE_CURRENT_SOURCE_DIR}/..) +LINK_DIRECTORIES(${CMAKE_CURRENT_SOURCE_DIR}/..) -FIND_LIBRARY(json NAMES json-c json) +FIND_LIBRARY(json NAMES json-c json) -ADD_EXECUTABLE(blobmsg-example blobmsg-example.c) -TARGET_LINK_LIBRARIES(blobmsg-example ubox blobmsg_json ${json}) +ADD_EXECUTABLE(blobmsg-example blobmsg-example.c) +TARGET_LINK_LIBRARIES(blobmsg-example ubox blobmsg_json ${json}) -ADD_EXECUTABLE(ustream-example ustream-example.c) -TARGET_LINK_LIBRARIES(ustream-example ubox) +ADD_EXECUTABLE(ustream-example ustream-example.c) +TARGET_LINK_LIBRARIES(ustream-example ubox) -ADD_EXECUTABLE(runqueue-example runqueue-example.c) -TARGET_LINK_LIBRARIES(runqueue-example ubox) +ADD_EXECUTABLE(runqueue-example runqueue-example.c) +TARGET_LINK_LIBRARIES(runqueue-example ubox) -ADD_EXECUTABLE(json_script-example json_script-example.c) -TARGET_LINK_LIBRARIES(json_script-example ubox blobmsg_json json_script ${json}) +ADD_EXECUTABLE(json_script-example json_script-example.c) +TARGET_LINK_LIBRARIES(json_script-example ubox blobmsg_json json_script ${json}) +ENDIF() -- 1.7.10.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Linux 4.x
On 6 June 2015 at 09:21, Dirk Neukirchen wrote: > On 05.06.2015 16:00, Baptiste Clenet wrote: >> Hi OpenWRT developers, >> >> Is there any plan to port OPENWRT on Linux 4.x? (Or is it already done?) >> >> > > > - ar71xx: ar8216/ar8316/ar8xxx driver is broken > on 8337N and some unknown router (reported yesterday on IRC) > look at [3] if anybody is interested That was me, probably. I'm trying 4.0.4 on several ar71xx routers/APs, mostly Ubiquiti. All have the same problem: http://p.tet.rtu.lv/pbzn5sspm/wvtsep/raw I think the problem is inside ag71xx (ethernet driver) and related to timers and/or interrupts but not sure. Regards, Roman ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH RFC] Add support for Ubiquiti Unifi Outdoor Plus
Hi, please review my patch to add support for the Ubiquiti Unifi Outdoor Plus access point based on the work of Kirill Berezin and me. The access point has a configurable RF filter in the receive path that must be tuned according to the selected Wifi channel. A patch to compat_wireless adds support to register a callback to the ath9k driver that is called whenever the channel changes. It also adds hsr.c, the channel change helper that tunes the filter connected to the AR9287 GPIO pins. I'm running this part successfully on top of the Chaos Calmer RC1 image. A new configuration option to create the kmod-ath-hsr. It contains the driver .ko and must be installed on the access point. This is compile tested on trunk. I also tried to change target/linux/ar71xx/generic/profiles/ubnt.mk and target/linux/ar71xx/image/Makefile to include this module into the UBNTUNIFIOUTDOORPLUS image, but this fails. Any idea why? Comments? Stefan Index: package/kernel/mac80211/Makefile === --- package/kernel/mac80211/Makefile(Revision 45907) +++ package/kernel/mac80211/Makefile(Arbeitskopie) @@ -27,7 +27,7 @@ rt2x00-lib rt2x00-pci rt2x00-usb rt2800-lib rt2400-pci rt2500-pci \ rt2500-usb rt61-pci rt73-usb rt2800-mmio rt2800-pci rt2800-usb rt2800-soc \ rtl8180 rtl8187 zd1211rw mac80211-hwsim carl9170 b43 b43legacy \ - ath9k-common ath9k ath9k-htc ath10k ath net-libipw net-ipw2100 net-ipw2200 \ + ath9k-common ath9k ath9k-htc ath9k-hsr ath10k ath net-libipw net-ipw2100 net-ipw2200 \ mwl8k mwifiex-pcie net-hermes net-hermes-pci net-hermes-plx net-hermes-pcmcia \ iwl-legacy iwl3945 iwl4965 iwlagn wlcore wl12xx wl18xx lib80211 \ rtlwifi rtlwifi-pci rtlwifi-usb rtl8192c-common rtl8192ce rtl8192se \ @@ -589,6 +589,22 @@ endef +define KernelPackage/ath9k-hsr + $(call KernelPackage/mac80211/Default) + TITLE:=Driver for the Ubiquiti UniFi Outdoor Plus HSR filter + URL:=http://wiki.openwrt.org/toh/ubiquiti/unifi_outdoorplus + DEPENDS+= @PCI_SUPPORT||TARGET_ar71xx +kmod-ath9k + FILES:= \ + $(PKG_BUILD_DIR)/drivers/net/wireless/ath/ath9k/ath9k_hsr.ko + AUTOLOAD:=$(call AutoProbe,ath9k_hsr) +endef + +define KernelPackage/ath9k-hsr/description +This modules adds support for the 'High-Selectivity Receiver' +RF filter in the receive path of the access point. It is +required for this and only for this access point. +endef + define KernelPackage/ath9k-htc $(call KernelPackage/mac80211/Default) TITLE:=Atheros 802.11n USB device support @@ -1559,6 +1575,8 @@ config-$(CONFIG_ATH_USER_REGD) += ATH_USER_REGD config-$(CONFIG_ATH9K_SUPPORT_PCOEM) += ATH9K_PCOEM +config-$(call config_package,ath9k-hsr) += ATH9K_HSR + config-$(call config_package,ath9k-htc) += ATH9K_HTC config-$(call config_package,ath10k) += ATH10K ATH10K_PCI @@ -2055,6 +2073,7 @@ $(eval $(call KernelPackage,mac80211-hwsim)) $(eval $(call KernelPackage,ath9k-common)) $(eval $(call KernelPackage,ath9k)) +$(eval $(call KernelPackage,ath9k-hsr)) $(eval $(call KernelPackage,ath9k-htc)) $(eval $(call KernelPackage,ath10k)) $(eval $(call KernelPackage,ath)) Index: package/kernel/mac80211/patches/930-ubnt-uap-plus-hsr.patch === --- package/kernel/mac80211/patches/930-ubnt-uap-plus-hsr.patch (Revision 0) +++ package/kernel/mac80211/patches/930-ubnt-uap-plus-hsr.patch (Arbeitskopie) @@ -0,0 +1,346 @@ +diff -X diffign -Npur kernel/drivers/net/wireless/ath/ath9k.orig/ath9k.h kernel/drivers/net/wireless/ath/ath9k/ath9k.h +--- kernel/drivers/net/wireless/ath/ath9k.orig/ath9k.h 2015-06-04 21:19:11.0 +0200 kernel/drivers/net/wireless/ath/ath9k/ath9k.h 2015-06-06 10:23:05.0 +0200 +@@ -1110,4 +1110,10 @@ static inline int ath_ahb_init(void) { r + static inline void ath_ahb_exit(void) {}; + #endif + ++/* ++ * OpenWrt UBNT HSR filter support ++ */ ++typedef void (set_channel_helper_fn)(struct ath_hw* ah, int bw, int fq); ++void ath9k_register_set_channel_helper(set_channel_helper_fn *); ++ + #endif /* ATH9K_H */ +diff -X diffign -Npur kernel/drivers/net/wireless/ath/ath9k.orig/channel.c kernel/drivers/net/wireless/ath/ath9k/channel.c +--- kernel/drivers/net/wireless/ath/ath9k.orig/channel.c 2015-03-10 04:37:15.0 +0100 kernel/drivers/net/wireless/ath/ath9k/channel.c2015-06-06 10:23:05.0 +0200 +@@ -16,6 +16,18 @@ + + #include "ath9k.h" + ++/* ++ * OpenWrt UBNT HSR filter support ++ */ ++static set_channel_helper_fn *ath9k_set_channel_helper; ++ ++void ath9k_register_set_channel_helper(set_channel_helper_fn *chanfn) ++{ ++ ath9k_set_channel_helper = chanfn; ++} ++EXPORT_SYMBOL(ath9k_register_set_channel_helper); ++ ++ + /* Set/change channels. If the channel is really being changed, it's done + * by reseting the chip. To accomplish this we must first cleanup any pending + * DMA, then restart
Re: [OpenWrt-Devel] lantiq DSL drivers / firmware info
W dniu 2015-06-06 o 14:18, Aleksander Wałęski pisze: Interesting. Have you made a note of which parameter made such a difference? I guess disabling ReTx could potentially cause lower sync speeds because DSLAM needs to compensate for lack of retransmissions. It may be enabled/disabled in autoboot script as it is in latest TP-LINK firmware. Vectroring needs firmware to have it enabled, but its VDSL2-only feature anyway so it shouldn't cause issues for you. Bonding does not seem to be supported by the driver (yet). Router's performance change with time worries me a bit. Are you sure it is DSL part that is slowing it down? I have 9 days uptime at this point and have not noticed any slowdowns yet. As for speed, yes only DSL is affected. LAN -> WLAN and overall (USB/3G) performance is same, bit higher CPU usage but cannot trace it by top, ram a bit but that because driver is bit bigger. ReTx on ADSL isn't used so I don't know if driver tries to do something that it can't do. What intriges me is that only two options (except low-level init) are different VDSL / ADSL related in init scripts delivered with original driver package: if [ "$wanphy_phymode" = "0" -o "$wanphy_phymode" = "3" ]; then # If BitSwap is disabled, or Retransmission is enabled # then set the DSL Parameters accordingly if [ "$BS_ENA" != "1" ]; then dir="0 1" for j in $dir ; do LFCG_VALS=`${BIN_DIR}/dsl_cpe_pipe.sh lfcg $j` if [ "$?" = "0" ]; then for i in $LFCG_VALS; do eval $i 2>/dev/null; done ${BIN_DIR}/dsl_cpe_pipe.sh lfcs $nDirection \ $bTrellisEnable $BS_ENA $RETX_ENA $bVirtualNoiseSupport \ $b20BitSupport >/dev/null else if [ "$j" = "0" ]; then ${BIN_DIR}/dsl_cpe_pipe.sh lfcs $j 1 $BS_ENA $RETX_ENA \ 0 -1 >/dev/null else ${BIN_DIR}/dsl_cpe_pipe.sh lfcs $j 1 $BS_ENA $RETX_ENA \ 0 0 >/dev/null fi fi done After 9 days and bit of performance drop I reverted back to stripped out init script and also lowered debug level to default so I can track what is causing these issues. On Fri, Jun 5, 2015 at 9:27 AM, Sylwester Petela wrote: W dniu 2015-06-05 o 04:56, Aleksander Wałęski pisze: Try playing with /etc/init.d/dsl_control when you'll have a moment to spare to see if all parameters it passes to control application are necessary. Selecting between ADSL and VDSL may be necessary but firmware for ADSL seems to be annex-specific and I think that each step we can make towards simplifying configuration will be welcomed. There are more parameters required then only dsl_control passes, low_level config, ReTx, Bonding, Vectoring. Getting rid of these gave me two things: 1. slower 1 synch (full_init -> exception -> full_init) 2. after couple of days (8d 0h 9m 30s) router is less responsive then at the beginning, d/u speed is also affected. Tested on Annex A line ATM, compared to normal dsl_control with only higher debug level (it consumes bit more RAM then lower debug level). Conclusion: maybe on VDSL line these values have margin usage but ReTx or Vectoring on Annex A ADSL line is bit to much to driver. On Thu, Jun 4, 2015 at 10:30 PM, Martin Blumenstingl wrote: On Tue, Jun 2, 2015 at 1:54 AM, Aleksander Wałęski wrote: Extraction procedure is exactly the same as for regular TD-W9980. Thanks, I have it that this afternoon. I was expecting only Annex difference, but this firmware may be specifically tweaked for Germany ("# for DT/Germany market" in vdsl.scr). I guess ADSL over ISDN is not very popular elsewhere. Yes, Germany is a bit special regarding this... On Mon, Jun 1, 2015 at 11:32 PM, Martin Blumenstingl wrote: I can test it this weekend on an Annex B ADSL connection. So I will test with firmware 1e472dad0eda88281af7c00cd3f49fcc29d4fa83 or 186b5406e6511c97d997b48f5e0ec5ad3f62600d (see [1]). I was able to test those two today: both are working fine on my ADSL2+ Annex B connection - I did not notice any difference between them. I have also updated my patch once again: [0]. It does not spam my dmesg, device is still responsive. However, I cannot say anything regarding stability yet. Let's wait a few days... Regards, Martin [0] https://gist.github.com/xdarklight/2986587133d97892a4b3 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Rate limiting features of the ag71xx hardware
On Friday, June 05, 2015 02:18:22 PM Dave Taht wrote: > TX delay setting? What else can it do? Can't tell. Atheros' ethernet driver source is available in the GPL source for this device (but I guess this is nothing special. Version is: s17_ssdk_v1.0.4p1). > My dream has been to find a way to set the tx completion interrupt > to only return with a soft set rate. So if I had a gigE connection > but my uplink was only 10Mbits, it would return the interrupt > after 1.3ms had expired. > > this would let me get away entirely from using software rate limiting > with htb, just program a register once with the uplink rate, and > let bql and fq_codel handle the rest. I don't know if the rate limiting implementation you describe would be possible to implement or not. But, the vendor driver has some code to setup some hardware rate limiting in "athrs_qos.c". Regards, Christian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Visita a Abrint
** Flavio Leonel ** Consultoria em Telecom (redes sem fio para provedores - redes cabeadas - FTTH - Servidores Linux - Servidores Windows) Desde 2009 trabalho com consultoria que se estende até hoje com fortes parceiros e consolidando o mercado a cada dia, com seriedade e habilidade para levar a solução perfeita ao seu negocio e manter uma solida parceria Sempre busco levar ao meus clientes a mais inovadora e solida tecnologia para que possa leva-la aos seus clientes. Obrigado aos parceiros que pude visitar e revê-los na 7º Abrint. Att: Flavio R. Leonel This email was sent to openwrt-devel@lists.openwrt.org (mailto:openwrt-devel@lists.openwrt.org) why did I get this? (http://br0solutions.us10.list-manage.com/about?u=2b49b556fbfe72c68ef83b907&id=bdf9a07d31&e=acebd36abb&c=c161a6f023) unsubscribe from this list (http://br0solutions.us10.list-manage1.com/unsubscribe?u=2b49b556fbfe72c68ef83b907&id=bdf9a07d31&e=acebd36abb&c=c161a6f023) update subscription preferences (http://br0solutions.us10.list-manage.com/profile?u=2b49b556fbfe72c68ef83b907&id=bdf9a07d31&e=acebd36abb) br0solutions . estra agua branca . Rio De Janeiro, MD 21720-161 . Brazil Email Marketing Powered by MailChimp http://www.mailchimp.com/monkey-rewards/?utm_source=freemium_newsletter&utm_medium=email&utm_campaign=monkey_rewards&aid=2b49b556fbfe72c68ef83b907&afl=1___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq DSL drivers / firmware info
As I mentioned earlier I am already running with very minimal configuration. My control process parameters list looks like this: /sbin/vdsl_cpe_control -i -n /sbin/dsl_notify.sh -f /lib/firmware/vdsl.bin -A /lib/firmware/vdsl.scr -i is required, but actual initialization bits are not (in my case). As far as I know this selects operation mode of the firmware (VDSL/ADSL). Not sure if firmware can autodetect this, or if it just defaults to VDSL. I am passing -A vdsl autoboot script just for peace of mind (it was included with firmware). My connection seems to work exactly the same without it. We indeed could use some more testing. Preferably not only on different annexes but different ISPs as well. On Sat, Jun 6, 2015 at 1:49 PM, Martin Blumenstingl wrote: > On Fri, Jun 5, 2015 at 4:56 AM, Aleksander Wałęski wrote: >> Try playing with /etc/init.d/dsl_control when you'll have a moment to >> spare to see if all parameters it passes to control application are >> necessary. > It seems that the lowlevel configuration is indeed not required > anymore. > Removing the "autoboot" configurations also did not make any > difference. > DSL is still coming up fine, and still syncing at the same speed. > > I have updated my patch yet again: [0] > > Maybe you can give it a go again with your VDSL connection? > Someone testing with ADSL and Annex A would be good as > well. > > > [0] https://gist.github.com/xdarklight/2986587133d97892a4b3 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq DSL drivers / firmware info
On Fri, Jun 5, 2015 at 4:56 AM, Aleksander Wałęski wrote: > Try playing with /etc/init.d/dsl_control when you'll have a moment to > spare to see if all parameters it passes to control application are > necessary. It seems that the lowlevel configuration is indeed not required anymore. Removing the "autoboot" configurations also did not make any difference. DSL is still coming up fine, and still syncing at the same speed. I have updated my patch yet again: [0] Maybe you can give it a go again with your VDSL connection? Someone testing with ADSL and Annex A would be good as well. [0] https://gist.github.com/xdarklight/2986587133d97892a4b3 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Linux 4.x
On 06/06/2015 08:21 AM, Dirk Neukirchen wrote: > On 05.06.2015 16:00, Baptiste Clenet wrote: >> Hi OpenWRT developers, >> >> Is there any plan to port OPENWRT on Linux 4.x? (Or is it already done?) >> >> > > There is a patch available for Kernel 4.1-rc1 [1] > it does not apply cleanly anymore, have a look at my refreshed version [2] > There might be some compile issues depending your target, see the other > folders at [2] > > 4.x commits are a little bit on hold since CC which has 3.18 > is not branched yet and probably needs some more testing > > Some testing results for 4.0/4.1: > - afaik omap was running but produces an oops in bootup > (afair Arch Linux produced an oops too during bootup) > > - ar71xx: ar8216/ar8316/ar8xxx driver is broken > on 8337N and some unknown router (reported yesterday on IRC) > look at [3] if anybody is interested > > > References: > [1]: http://patchwork.ozlabs.org/patch/465774/ > [2]: https://github.com/plntyk/openwrt-patches/tree/master/kernel_4_1 > [3]: ar71xx with 4.1-rc1 switch driver error: paste.debian.net/205511 > Because of the CC release kernel updates are on hold, we want to get the existing stuff stable first. If your are interested here are some patches to make kernel 4.1 work, they are based on the patches Dirk referenced: https://github.com/hauke/openwrt/tree/bcm53xx-4.1 Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] grub: add download mirrors
grub: add download mirrors Add three download mirrors for 'grub', as the Makefile currently defines only one download location. @GNU can not be used, as the most recent version of 'grub' is not available at the general GNU mirrors, and can only be found at the "gnu-alpha" mirrors. Signed-off-by: Hannu Nyman --- A forum discussion brought 'bc' download problems into my attention: https://forum.openwrt.org/viewtopic.php?id=57803 I sent a patch about bc and then searched Openwrt sources for other similar packages. In the core packages only grub has the same alpha.gnu.org download location definition. The most recent version of grub is also not available at the Openwrt download mirrors. So I submit also a patch regarding grub. Index: package/boot/grub2/Makefile === --- package/boot/grub2/Makefile (revision 45907) +++ package/boot/grub2/Makefile (working copy) @@ -1,5 +1,5 @@ # -# Copyright (C) 2006-2010 OpenWrt.org +# Copyright (C) 2006-2015 OpenWrt.org # # This is free software, licensed under the GNU General Public License v2. # See /LICENSE for more information. @@ -13,7 +13,10 @@ PKG_RELEASE:=1 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.xz -PKG_SOURCE_URL:=http://alpha.gnu.org/gnu/grub +PKG_SOURCE_URL:=http://alpha.gnu.org/gnu/grub \ + http://gnualpha.uib.no/grub/ \ + http://mirrors.fe.up.pt/pub/gnu-alpha/grub/ \ + http://www.nic.funet.fi/pub/gnu/alpha/gnu/grub/ PKG_MD5SUM:=be62932eade308a364ea4bbc91295930 HOST_BUILD_PARALLEL:=1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2] bc: add download mirrors
bc: add download mirrors Add three download mirrors for 'bc', as the Makefile currently defines only one download location. @GNU can not be used, as the most recent version of 'bc' is not available at the general GNU mirrors, and can only be found at the "gnu-alpha" mirrors. Signed-off-by: Hannu Nyman --- Patch v2 corrects whitespace in the Makefile. A forum discussion brought 'bc' download problems into my attention: https://forum.openwrt.org/viewtopic.php?id=57803 The package Makefile defines only a single download server and the file is not available at the Openwrt mirrors. The most recent 'bc' is not available in most of the GNU mirrors, so @GNU is unusable. I searched a bit and found three mirrors of "GNU alpha", which I added to the Makefile. Index: tools/bc/Makefile === --- tools/bc/Makefile (revision 45907) +++ tools/bc/Makefile (working copy) @@ -10,7 +10,10 @@ PKG_VERSION:=1.06.95 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2 -PKG_SOURCE_URL:=http://alpha.gnu.org/gnu/bc +PKG_SOURCE_URL:=http://alpha.gnu.org/gnu/bc \ + http://gnualpha.uib.no/bc/ \ + http://mirrors.fe.up.pt/pub/gnu-alpha/bc/ \ + http://www.nic.funet.fi/pub/gnu/alpha/gnu/bc/ PKG_MD5SUM:=5126a721b73f97d715bb72c13c889035 include $(INCLUDE_DIR)/host-build.mk ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] bc: add download mirrors
bc: add download mirrors Add three download mirrors for 'bc', as the Makefile currently defines only one download location. @GNU can not be used, as the most recent version of 'bc' is not available at the general GNU mirrors, and can only be found at the "gnu-alpha" mirrors. Signed-off-by: Hannu Nyman --- A forum discussion brought 'bc' download problems into my attention: https://forum.openwrt.org/viewtopic.php?id=57803 The package Makefile defines only a single download server that was down, and the file is not available at the Openwrt mirrors. The most recent 'bc' is not available in most of the GNU mirrors, so I searched a bit and found three mirrors of "GNU alpha", which I added to the Makefile. Index: tools/bc/Makefile === --- tools/bc/Makefile (revision 45907) +++ tools/bc/Makefile (working copy) @@ -10,7 +10,11 @@ PKG_VERSION:=1.06.95 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2 -PKG_SOURCE_URL:=http://alpha.gnu.org/gnu/bc +PKG_SOURCE_URL:=http://alpha.gnu.org/gnu/bc \ + http://gnualpha.uib.no/bc/ \ + http://mirrors.fe.up.pt/pub/gnu-alpha/bc/ \ + http://www.nic.funet.fi/pub/gnu/alpha/gnu/bc/ + PKG_MD5SUM:=5126a721b73f97d715bb72c13c889035 include $(INCLUDE_DIR)/host-build.mk ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel