Re: [OpenWrt-Devel] i get no image for TL-WA7510
W dniu 12.08.2015 o 21:29, smile...@gmail.com pisze: I miss not only the TL-WA7510 image. I missing also several images for other 4MB Flash-Router. Is there a Funktion in Openwrt which build images only if the image-size not excite the flash-size? I found there is. I was also wonder for half day why image for my board was not created. I think there should be at least a warning and option to bypass this check it would be helpful to estimate how many bytes we need to reclaim to fit. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Fwd: 3-address Wi-Fi bridging (was: Multiple Wi-Fi client/AP interfaces on one radio)
Hi, i will check whether this is driver issue or Luci, I have to add disable WPS if this feature is enabled for the WiFi module this in wireless. How i can handle this. Thanks, On Thu, Aug 13, 2015 at 2:18 PM, David Lang da...@lang.hm wrote: On Thu, 13 Aug 2015, John kerry wrote: But i dont think so this driver might be the problem, Because when i am doing using GUI its working so there will be not driver problem. Just i am not getting how to add this in build config. Normally what will be the wireless config for the repeater mode default. the exact file that you create as a result of the GUI is what you would put in the build config. But you say that you don't want that file because you want to connect to different SSIDs on different channels, so you don't _have_ any one file that you want to put in the default. When you use LUCI to scan and attach to a different SSID, you say that it looses the config for the local systems to connect to it. This could be a LUCI problem, or it could be that the driver requires that this be reset afterwords. If it's a LUCI problem, you will have to fix that code (or go to where tehy develop it and convince them to fix it). If it's a driver problem you are out of luck. But we can't tell you a file to put in the build that will connect to any remote system because there isn't one file that will automatically connect to any of several remote systems. David Lang On Thu, Aug 13, 2015 at 11:40 AM, David Lang da...@lang.hm wrote: If you want to have one config thaqt will talk to many different APs with different names/configs you are asking for magic. You have to change the config to talk to the different destinations. Since you are using a non-mainline driver, we don't know what the driver s able to do. It sounds as if there is a problem that could either be in the driver or in LUCI that makes it loose the rest of the config when you have it scan for networks. you can probably avoid that by just changing the info in the file to be appropriate for the new environment and restarting wifi/rebooting. If you want to do this via the existing GUI you will need to make code changes to LUCI. But at this point you are talking custom stuff. David Lang On Thu, 13 Aug 2015, John kerry wrote: Hi, Still i am not able to configure wireless config file. The problem i am facing, i cannot add fixed router name and password. It should every time scan and connect to any router. If i used GUI one config its fixed to that router which i connected. So with that configuration we are not able to scan again and connect to any other router next time. On Wed, Aug 12, 2015 at 9:29 AM, John kerry kerry9...@gmail.com wrote: Yes i able to config using GUI, But when i am configuring GUI i scan and connect to one AP and then add one more AP mode to it. So finally i will have wireless configuration. But i cant keep this config in build option because if i load this configuration it will load what i connected last time, so next time i cant scan it anymore it showing the same connected to last AP. On Wed, Aug 12, 2015 at 1:36 AM, David Lang da...@lang.hm wrote: I thought you said a couple posts ago that you were able to configure it through the GUI to work the way you wanted it to, you were just wanting to make something the default. So do you have it working or not? If you have it working, it should keep working after a reboot. What are you meaning when you say that you want to change the default? Are you meaning that you want to create an image that will behave this way when you do a factory reset (or when you first flash it)? If so, then you need to take your working config and make it part of your image via the files/ mechansim. If you are meaning something else, I'm still not understanding what you are trying to do. David Lang On Tue, 11 Aug 2015, John kerry wrote: Date: Tue, 11 Aug 2015 21:20:58 +0800 From: John kerry kerry9...@gmail.com To: David Lang da...@lang.hm Cc: Alex Weedy weedy2...@gmail.com, OpenWrt Development List openwrt-devel@lists.openwrt.org Subject: Re: [OpenWrt-Devel] Fwd: 3-address Wi-Fi bridging (was: Multiple Wi-Fi client/AP interfaces on one radio) Hi, How to config wireless config file for repeater mode. I am not able to config. On Tue, Aug 11, 2015 at 5:34 PM, John kerry kerry9...@gmail.com wrote: When i load firmware the wireless config will be like below: config wifi-device 'wifi0' option type 'qcawifi' option macaddr '00:26:75:bd:37:24' option hwmode '11ng' option txpower '16' option htmode 'HT20' option disabled '0' option channel '1' config wifi-iface option device 'wifi0' option mode 'ap' option ssid 'Test_ap' option network 'lan' option encryption 'psk2' option key 'Test_ap' option wds '1' so
Re: [OpenWrt-Devel] Fwd: 3-address Wi-Fi bridging (was: Multiple Wi-Fi client/AP interfaces on one radio)
Sorry i didn't mentioned fully. I want this to happen, disable WPS if this feature is enabled for the WiFi module On Thu, Aug 13, 2015 at 5:22 PM, David Lang da...@lang.hm wrote: On Thu, 13 Aug 2015, John kerry wrote: Hi, i will check whether this is driver issue or Luci, I have to add disable WPS if this feature is enabled for the WiFi module this in wireless. How i can handle this. ??? is this something you want to happen? something that happens that you don't want? we can't read your mind. David Lang Thanks, On Thu, Aug 13, 2015 at 2:18 PM, David Lang da...@lang.hm wrote: On Thu, 13 Aug 2015, John kerry wrote: But i dont think so this driver might be the problem, Because when i am doing using GUI its working so there will be not driver problem. Just i am not getting how to add this in build config. Normally what will be the wireless config for the repeater mode default. the exact file that you create as a result of the GUI is what you would put in the build config. But you say that you don't want that file because you want to connect to different SSIDs on different channels, so you don't _have_ any one file that you want to put in the default. When you use LUCI to scan and attach to a different SSID, you say that it looses the config for the local systems to connect to it. This could be a LUCI problem, or it could be that the driver requires that this be reset afterwords. If it's a LUCI problem, you will have to fix that code (or go to where tehy develop it and convince them to fix it). If it's a driver problem you are out of luck. But we can't tell you a file to put in the build that will connect to any remote system because there isn't one file that will automatically connect to any of several remote systems. David Lang On Thu, Aug 13, 2015 at 11:40 AM, David Lang da...@lang.hm wrote: If you want to have one config thaqt will talk to many different APs with different names/configs you are asking for magic. You have to change the config to talk to the different destinations. Since you are using a non-mainline driver, we don't know what the driver s able to do. It sounds as if there is a problem that could either be in the driver or in LUCI that makes it loose the rest of the config when you have it scan for networks. you can probably avoid that by just changing the info in the file to be appropriate for the new environment and restarting wifi/rebooting. If you want to do this via the existing GUI you will need to make code changes to LUCI. But at this point you are talking custom stuff. David Lang On Thu, 13 Aug 2015, John kerry wrote: Hi, Still i am not able to configure wireless config file. The problem i am facing, i cannot add fixed router name and password. It should every time scan and connect to any router. If i used GUI one config its fixed to that router which i connected. So with that configuration we are not able to scan again and connect to any other router next time. On Wed, Aug 12, 2015 at 9:29 AM, John kerry kerry9...@gmail.com wrote: Yes i able to config using GUI, But when i am configuring GUI i scan and connect to one AP and then add one more AP mode to it. So finally i will have wireless configuration. But i cant keep this config in build option because if i load this configuration it will load what i connected last time, so next time i cant scan it anymore it showing the same connected to last AP. On Wed, Aug 12, 2015 at 1:36 AM, David Lang da...@lang.hm wrote: I thought you said a couple posts ago that you were able to configure it through the GUI to work the way you wanted it to, you were just wanting to make something the default. So do you have it working or not? If you have it working, it should keep working after a reboot. What are you meaning when you say that you want to change the default? Are you meaning that you want to create an image that will behave this way when you do a factory reset (or when you first flash it)? If so, then you need to take your working config and make it part of your image via the files/ mechansim. If you are meaning something else, I'm still not understanding what you are trying to do. David Lang On Tue, 11 Aug 2015, John kerry wrote: Date: Tue, 11 Aug 2015 21:20:58 +0800 From: John kerry kerry9...@gmail.com To: David Lang da...@lang.hm Cc: Alex Weedy weedy2...@gmail.com, OpenWrt Development List openwrt-devel@lists.openwrt.org Subject: Re: [OpenWrt-Devel] Fwd: 3-address Wi-Fi bridging (was: Multiple Wi-Fi client/AP interfaces on one radio) Hi, How to config wireless config file for repeater mode. I am not able to config. On Tue, Aug 11, 2015 at 5:34 PM, John kerry kerry9...@gmail.com wrote: When i load firmware the wireless config will be like below: config wifi-device 'wifi0' option type 'qcawifi' option macaddr '00:26:75:bd:37:24'
Re: [OpenWrt-Devel] Fwd: 3-address Wi-Fi bridging (was: Multiple Wi-Fi client/AP interfaces on one radio)
On Thu, 13 Aug 2015, John kerry wrote: Hi, i will check whether this is driver issue or Luci, I have to add disable WPS if this feature is enabled for the WiFi module this in wireless. How i can handle this. ??? is this something you want to happen? something that happens that you don't want? we can't read your mind. David Lang Thanks, On Thu, Aug 13, 2015 at 2:18 PM, David Lang da...@lang.hm wrote: On Thu, 13 Aug 2015, John kerry wrote: But i dont think so this driver might be the problem, Because when i am doing using GUI its working so there will be not driver problem. Just i am not getting how to add this in build config. Normally what will be the wireless config for the repeater mode default. the exact file that you create as a result of the GUI is what you would put in the build config. But you say that you don't want that file because you want to connect to different SSIDs on different channels, so you don't _have_ any one file that you want to put in the default. When you use LUCI to scan and attach to a different SSID, you say that it looses the config for the local systems to connect to it. This could be a LUCI problem, or it could be that the driver requires that this be reset afterwords. If it's a LUCI problem, you will have to fix that code (or go to where tehy develop it and convince them to fix it). If it's a driver problem you are out of luck. But we can't tell you a file to put in the build that will connect to any remote system because there isn't one file that will automatically connect to any of several remote systems. David Lang On Thu, Aug 13, 2015 at 11:40 AM, David Lang da...@lang.hm wrote: If you want to have one config thaqt will talk to many different APs with different names/configs you are asking for magic. You have to change the config to talk to the different destinations. Since you are using a non-mainline driver, we don't know what the driver s able to do. It sounds as if there is a problem that could either be in the driver or in LUCI that makes it loose the rest of the config when you have it scan for networks. you can probably avoid that by just changing the info in the file to be appropriate for the new environment and restarting wifi/rebooting. If you want to do this via the existing GUI you will need to make code changes to LUCI. But at this point you are talking custom stuff. David Lang On Thu, 13 Aug 2015, John kerry wrote: Hi, Still i am not able to configure wireless config file. The problem i am facing, i cannot add fixed router name and password. It should every time scan and connect to any router. If i used GUI one config its fixed to that router which i connected. So with that configuration we are not able to scan again and connect to any other router next time. On Wed, Aug 12, 2015 at 9:29 AM, John kerry kerry9...@gmail.com wrote: Yes i able to config using GUI, But when i am configuring GUI i scan and connect to one AP and then add one more AP mode to it. So finally i will have wireless configuration. But i cant keep this config in build option because if i load this configuration it will load what i connected last time, so next time i cant scan it anymore it showing the same connected to last AP. On Wed, Aug 12, 2015 at 1:36 AM, David Lang da...@lang.hm wrote: I thought you said a couple posts ago that you were able to configure it through the GUI to work the way you wanted it to, you were just wanting to make something the default. So do you have it working or not? If you have it working, it should keep working after a reboot. What are you meaning when you say that you want to change the default? Are you meaning that you want to create an image that will behave this way when you do a factory reset (or when you first flash it)? If so, then you need to take your working config and make it part of your image via the files/ mechansim. If you are meaning something else, I'm still not understanding what you are trying to do. David Lang On Tue, 11 Aug 2015, John kerry wrote: Date: Tue, 11 Aug 2015 21:20:58 +0800 From: John kerry kerry9...@gmail.com To: David Lang da...@lang.hm Cc: Alex Weedy weedy2...@gmail.com, OpenWrt Development List openwrt-devel@lists.openwrt.org Subject: Re: [OpenWrt-Devel] Fwd: 3-address Wi-Fi bridging (was: Multiple Wi-Fi client/AP interfaces on one radio) Hi, How to config wireless config file for repeater mode. I am not able to config. On Tue, Aug 11, 2015 at 5:34 PM, John kerry kerry9...@gmail.com wrote: When i load firmware the wireless config will be like below: config wifi-device 'wifi0' option type 'qcawifi' option macaddr '00:26:75:bd:37:24' option hwmode '11ng' option txpower '16' option htmode 'HT20' option disabled '0' option channel '1' config wifi-iface option device 'wifi0' option mode 'ap' option ssid 'Test_ap' option network 'lan' option
Re: [OpenWrt-Devel] [PATCH v2] busybox: lock: implement -n Fail rather than wait
* Alexander Couzens lyn...@fe80.eu [07.08.2015 20:48]: lock -n is similiar to flock -n. If the lock was already taken, fail with exit code = 1 and write error message to stderr. see: http://mywiki.wooledge.org/BashFAQ/045 internally we are using 'mkdir' which is called via a 'lock()' function: if mkdir /tmp/lock_$reason; then return 0 else return 1 fi bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] `git tag` and releases
Summary: `git tag` doesn't currently show releases Hello, After done git clone git://git.openwrt.org/openwrt.git cd openwrt I did git tag to see which tags are in the git repository, but none are there. I hoped the releases where tagged. In SVN repository I found these tags 8.09 8.09_rc2 kamikaze_7.06 whiterussian_rc1 whiterussian_rc5 8.09.1attitude_adjustment_12.09 kamikaze_7.07 whiterussian_rc2 whiterussian_rc6 8.09.2backfire_10.03 kamikaze_7.09 whiterussian_rc3 8.09_rc1 backfire_10.03.1 whiterussian_0.9 whiterussian_rc4 (that I miss chaoscalmer_rcN _now not_ important) Will there be tags in the OpenWRT git repository? Cheers Geert Stappers -- Leven en laten leven ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] busybox: lock: implement -n Fail rather than wait
* Alexander Couzens lyn...@fe80.eu [06.08.2015 19:05]: lock -n is similiar to flock -n. If the lock was already taken, fail with exit code = 1 and write error message to stderr. sorry, forget to ask: is this more atomic than 'mkdir mypath || return'? bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Separate Default SSID for 2.4GHz and 5GHz
Hi, Yes exactly i have one radio which i want to switch between 2.4GHz and 5GHz. GUI side i will add one switch button, But i am not getting how handle backend wireless config. i mean to say where i can add this when selected 2.4GHz load 2.4GHz wireless configuration and same for 5GHz. On Thu, Aug 13, 2015 at 8:21 PM, Bastian Bittorf bitt...@bluebottle.com wrote: * Sami Olmari s...@olmari.fi [07.08.2015 15:48]: In openwrt you are free to configure each and every radio as own unit, so use whatever SSID you see fit for each radio. This is default basic OpenWrt stuff :) seems that Afkar has 1 radio which must be switched between 2.4 and 5 GHz, Afkar? bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Separate Default SSID for 2.4GHz and 5GHz
* Sami Olmari s...@olmari.fi [07.08.2015 15:48]: In openwrt you are free to configure each and every radio as own unit, so use whatever SSID you see fit for each radio. This is default basic OpenWrt stuff :) seems that Afkar has 1 radio which must be switched between 2.4 and 5 GHz, Afkar? bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Ar71xx: Add Minibox v1.0 support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stijn Segers francesco.borrom...@inventati.org wrote: Hi Karl, Thanks for your time. I have reworked the patch and re-ordered where possible (files like ar71xx.sh and diag.sh lack any alphabetical order). I have removed the code that set the led to status_led_off. What file should I be looking at, when you talk about the board file? Is it the minibox-v1.mk file? I diffed from the vendor's code (and added a profile by comparing with other devices) but that was it. I meant target/linux/ar71xx/files/arch/mips/ath79/mach-minibox-v1.c I don't have the hardware myself but I have found a tester willing to run the image (and see how the LED behaves with the default OpenWrt settings). It's not relevant how it behaves for them on their board. My problem here was that you were changing the behaviour for _all_ boards. And by the sound of it, you were working around an active low/high misconfiguration, which should be addressed by properly configuring the polarity of the leds in your board file, target/linux/ar71xx/files/arch/mips/ath79/mach-minibox-v1.c The new patch can be found here: https://volatilesystems.org/dl/openwrt/targets/add-minibox-target-trunk.patch If that doesn't work, a backup: http://sprunge.us/AUbX No-one's looking at that. I'm being helpful by reviewing your earlier mangled patch, but if you want this to be applied, you _will_ need to follow https://dev.openwrt.org/wiki/SubmittingPatches Pay particular attention to item 6. Yes, this is the graybeard stone age, lowest common denominator of email behaviour, but those are the _rules_ I recommend git-send-email to avoid the mangling that most clients will do. I expect the problem here: https://patchwork.ozlabs.org/patch/505479/ was that you trying to use diff manually to generate the patch set (from your .orig directory) While I'm sure that's possible, there's a reason most people use git or svn. Cheers, Karl P -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBAgAGBQJVzJtSAAoJEBmotQ/U1cr2WT4QALzDtq4XEBLaooi/Bu8qr+WI 83MRsoZHHd6GzEq+x8+2P07vPqrOHu6xbKGgx34KbAj4W6YXAUme8HYRm0/rIoYm PnJj5xJzn/JOkQbUU21+Fj+mXFEKWAyNC0byjmzFRIeo7viMSUCuPfU6NPm+aQua iDDj4iZTbgtPVRdBWAu6glBSLFajrS35PFbcLOfX1bvJ/ci930PWymfSWgY0bH+0 AyXzHcRbfM/apf09e3VxicfzmFCWLYMkAdStjPXKuok3hXom7E7gk6iMHE5j9B0A JxTBlahs+yoi4A0eEEGQs+D5+hisFzXB0mbGHqTBmpGyXFzo21V4sZfb00UrGtVx h1lcXKAU3IC4MVRm0I3/Ef0LCBeDCW1w/yNNBt/X4POGPm1ZUYl8B3z27/1AX6M9 /B4f35/A0g1X2sQLv4fZppJVbOhoxlgpxEo+Ms7TgVX/ERTUbN/n37b37UQg6frA MIG5OWHK+9HQk7NYXFvQWoW/jBLfU2HLR9ki1AUJtEfNQpYtOxJjZcF1SMlA46/0 aPUYbu/NObBYpA2CtheJuzb8MgeeE6QQs4D8Ik6de5NeBrO93XCe2nkJg9XCLkM/ a1uCq4R+p35nAq7Vrb94V/LjQasxwIOzJpSVMmAWIjQb8H5j6iYtwJlONrJCQGq2 WtF+/zcBO3X9fFVnlM7Q =zcDx -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] lighttpd 1.4.36 and file descriptors limit issue - OpenWrt related?
There is an issue with handling relatively big (4 MiB+) files in lighttpd after the upgrade to the 1.4.36: https://github.com/openwrt/packages/issues/1658 It seems lighttpd is running out of file descriptors and is replying with: 413 - Request Entity Too Large I also reported this issue upstream: http://article.gmane.org/gmane.comp.web.lighttpd/5370 I received following suggestion (on the IRC) pointing OpenWrt kernel: [19:45] sztanpet i shall blame the openwrt kernel [19:45] rmilecki sztanpet: what exactly? I can modify the config if needed [19:45] rmilecki or the sources if you have anything to test [19:45] sztanpet i have no idea [19:45] rmilecki oh [19:46] sztanpet but since the issue is such a core issue that everyone would be seeing it and that is not the case, that tells me its probably not lighttpd Can you think of anything in OpenWrt kernel that could cause such a problem? -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v4 1/4] sunxi: don't copy DTS files to BIN_DIR
The DTS files aren't useful (other targets don't copy them either) and clutter BIN_DIR with files unrelated to the chosen profile. Signed-off-by: Matthias Schiffer mschif...@universe-factory.net --- target/linux/sunxi/image/Makefile | 30 +- 1 file changed, 5 insertions(+), 25 deletions(-) diff --git a/target/linux/sunxi/image/Makefile b/target/linux/sunxi/image/Makefile index 6fcd61f..b96a360 100644 --- a/target/linux/sunxi/image/Makefile +++ b/target/linux/sunxi/image/Makefile @@ -11,28 +11,12 @@ include $(INCLUDE_DIR)/host.mk FAT32_BLOCK_SIZE=1024 FAT32_BLOCKS=$(shell echo $$(($(CONFIG_SUNXI_SD_BOOT_PARTSIZE)*1024*1024/$(FAT32_BLOCK_SIZE -BOARDS:= \ - sun4i-a10-cubieboard \ - sun4i-a10-olinuxino-lime \ - sun4i-a10-pcduino \ - sun5i-a13-olinuxino \ - sun6i-a31-colombus \ - sun6i-a31-m9 \ - sun7i-a20-bananapi \ - sun7i-a20-bananapro \ - sun7i-a20-cubieboard2 \ - sun7i-a20-cubietruck \ - sun7i-a20-olinuxino-lime \ - sun7i-a20-olinuxino-micro \ - sun7i-a20-pcduino3 \ - sun7i-a20-lamobo-r1 - define Image/BuildKernel mkimage -A arm -O linux -T kernel -C none \ -a 0x40008000 -e 0x40008000 \ -n 'ARM OpenWrt Linux-$(LINUX_VERSION)' \ -d $(KDIR)/zImage $(BIN_DIR)/$(IMG_PREFIX)-uImage - + ifneq ($(CONFIG_TARGET_ROOTFS_INITRAMFS),) $(CP) $(KDIR)/zImage-initramfs $(BIN_DIR)/$(IMG_PREFIX)-zImage-initramfs echo -ne '\x00\x00\x00\x00' $(BIN_DIR)/$(IMG_PREFIX)-zImage-initramfs @@ -42,20 +26,16 @@ define Image/BuildKernel $(BIN_DIR)/$(IMG_PREFIX)-uImage-initramfs \ ) endif - - $(foreach board,$(BOARDS), - $(CP) $(DTS_DIR)/$(board).dtb $(BIN_DIR)/ - ) endef define Image/Build/SDCard rm -f $(KDIR)/boot.img mkdosfs $(KDIR)/boot.img -C $(FAT32_BLOCKS) - + mcopy -i $(KDIR)/boot.img $(BIN_DIR)/uboot-sunxi-$(PROFILE)/$(IMG_PREFIX)-$(PROFILE)-boot.scr ::boot.scr - mcopy -i $(KDIR)/boot.img $(BIN_DIR)/$(2).dtb ::dtb + mcopy -i $(KDIR)/boot.img $(DTS_DIR)/$(2).dtb ::dtb mcopy -i $(KDIR)/boot.img $(BIN_DIR)/$(IMG_PREFIX)-uImage ::uImage - + ./gen_sunxi_sdcard_img.sh \ $(BIN_DIR)/$(IMG_PREFIX)-$(PROFILE)-sdcard-vfat-$(1).img \ $(KDIR)/boot.img \ @@ -124,7 +104,7 @@ endef define Image/Build $(call Image/Build/$(1),$(1)) $(call Image/Build/Profile/$(PROFILE),$(1)) - + dd if=$(KDIR)/root.$(1) of=$(BIN_DIR)/$(IMG_PREFIX)-root.$(1) bs=128k conv=sync endef -- 2.5.0 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v4 2/4] sunxi: fix uboot install location
Install uboot files to KERNEL_BUILD_DIR instead of BIN_DIR to fix ImageBuilder. Similar fixes are necessary for many (all?) other uboot targets. Signed-off-by: Matthias Schiffer mschif...@universe-factory.net --- package/boot/uboot-sunxi/Makefile | 14 +++--- target/linux/sunxi/image/Makefile | 4 ++-- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/package/boot/uboot-sunxi/Makefile b/package/boot/uboot-sunxi/Makefile index 1aeeceb..b08f9ed 100644 --- a/package/boot/uboot-sunxi/Makefile +++ b/package/boot/uboot-sunxi/Makefile @@ -17,7 +17,7 @@ PKG_SOURCE_URL:= \ PKG_MD5SUM:=3dac9a0b46fed77fc768ad3bd2d68c05 -PKG_BUILD_DIR:=$(BUILD_DIR)/$(PKG_NAME)-$(BUILD_VARIANT)/$(PKG_NAME)-$(PKG_VERSION) +PKG_BUILD_DIR:=$(KERNEL_BUILD_DIR)/$(PKG_NAME)-$(BUILD_VARIANT)/$(PKG_NAME)-$(PKG_VERSION) PKG_LICENSE:=GPL-2.0 GPL-2.0+ PKG_LICENSE_FILES:=Licenses/README @@ -138,16 +138,16 @@ define Build/Compile endef define Package/uboot/install/default - $(INSTALL_DIR) $(BIN_DIR)/uboot-$(BOARD)-$(1) $(CP) $(PKG_BUILD_DIR)/u-boot.bin \ - $(BIN_DIR)/uboot-$(BOARD)-$(1)/openwrt-$(BOARD)-$(1)-u-boot.bin + $(KERNEL_BUILD_DIR)/uboot-$(BOARD)-$(1)-u-boot.bin $(CP) $(PKG_BUILD_DIR)/spl/sunxi-spl.bin \ - $(BIN_DIR)/uboot-$(BOARD)-$(1)/openwrt-$(BOARD)-$(1)-spl.bin + $(KERNEL_BUILD_DIR)/uboot-$(BOARD)-$(1)-spl.bin $(CP) $(PKG_BUILD_DIR)/u-boot-sunxi-with-spl.bin \ - $(BIN_DIR)/uboot-$(BOARD)-$(1)/openwrt-$(BOARD)-$(1)-u-boot-with-spl.bin + $(KERNEL_BUILD_DIR)/uboot-$(BOARD)-$(1)-u-boot-with-spl.bin $(CP) uEnv.txt \ - $(BIN_DIR)/uboot-$(BOARD)-$(1)/openwrt-$(BOARD)-$(1)-uEnv.txt - mkimage -C none -A arm -T script -d $(BIN_DIR)/uboot-$(BOARD)-$(1)/openwrt-$(BOARD)-$(1)-uEnv.txt $(BIN_DIR)/uboot-$(BOARD)-$(1)/openwrt-$(BOARD)-$(1)-boot.scr + $(KERNEL_BUILD_DIR)/uboot-$(BOARD)-$(1)-uEnv.txt + mkimage -C none -A arm -T script -d $(KERNEL_BUILD_DIR)/uboot-$(BOARD)-$(1)-uEnv.txt \ + $(KERNEL_BUILD_DIR)/uboot-$(BOARD)-$(1)-boot.scr endef define Package/uboot/install/template diff --git a/target/linux/sunxi/image/Makefile b/target/linux/sunxi/image/Makefile index b96a360..19ab935 100644 --- a/target/linux/sunxi/image/Makefile +++ b/target/linux/sunxi/image/Makefile @@ -32,7 +32,7 @@ define Image/Build/SDCard rm -f $(KDIR)/boot.img mkdosfs $(KDIR)/boot.img -C $(FAT32_BLOCKS) - mcopy -i $(KDIR)/boot.img $(BIN_DIR)/uboot-sunxi-$(PROFILE)/$(IMG_PREFIX)-$(PROFILE)-boot.scr ::boot.scr + mcopy -i $(KDIR)/boot.img $(KDIR)/uboot-sunxi-$(PROFILE)-boot.scr ::boot.scr mcopy -i $(KDIR)/boot.img $(DTS_DIR)/$(2).dtb ::dtb mcopy -i $(KDIR)/boot.img $(BIN_DIR)/$(IMG_PREFIX)-uImage ::uImage @@ -42,7 +42,7 @@ define Image/Build/SDCard $(KDIR)/root.$(1) \ $(CONFIG_SUNXI_SD_BOOT_PARTSIZE) \ $(CONFIG_TARGET_ROOTFS_PARTSIZE) \ - $(BIN_DIR)/uboot-sunxi-$(PROFILE)/$(IMG_PREFIX)-$(PROFILE)-u-boot-with-spl.bin + $(KDIR)/uboot-sunxi-$(PROFILE)-u-boot-with-spl.bin endef define Image/Build/Profile/A10-OLinuXino-Lime -- 2.5.0 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [package] firewall: Adds support for IPv6 DNAT, SNAT, and REDIRECT
From: Timothy Ace openwrt.or...@timothyace.com
Adds support for IPv6 DNAT, SNAT, and REDIRECT.
Signed-off-by: Timothy Ace openwrt.or...@timothyace.com
---
This is a git patch for the firewall3 git repo at git://nbd.name/firewall3.git
Note1: Luci updates still need to be made in a separate patch to support IPv6
address entry on the port forwards page, but this works using manual entries in
/etc/config/firewall for now.
Note2: I changed the section in compare_addr() from this:
- return ((a-address.v4.s_addr a-mask.v4.s_addr) ==
- (b-address.v4.s_addr a-mask.v4.s_addr));
to this:
+ return ((a-address.v4.s_addr a-mask.v4.s_addr) ==
+ (b-address.v4.s_addr b-mask.v4.s_addr));
... because using a-mask instead of b-mask on the second line looked
wrong to me. Please let me know if that was intentional and I'll re-submit a
patch that accounts for that change for the v4 and new v6 sections.
From 83cdcf604b8c81c75065a91f50459721e87740b0 Mon Sep 17 00:00:00 2001
From: Timothy Ace openwrt.or...@timothyace.com
Date: Thu, 13 Aug 2015 00:28:02 -0400
Subject: [PATCH] Adds support for IPv6 DNAT, SNAT, and REDIRECT
---
defaults.c | 8
redirects.c | 42 ++
snats.c | 1 +
ubus.c | 24
utils.c | 10 --
zones.c | 13 -
6 files changed, 75 insertions(+), 23 deletions(-)
diff --git a/defaults.c b/defaults.c
index 396cbf7..45d6de6 100644
--- a/defaults.c
+++ b/defaults.c
@@ -32,10 +32,10 @@ static const struct fw3_chain_spec default_chains[] = {
C(ANY, FILTER, CUSTOM_CHAINS, forwarding_rule),
C(ANY, FILTER, SYN_FLOOD, syn_flood),
- C(V4, NAT,UNSPEC,delegate_prerouting),
- C(V4, NAT,UNSPEC,delegate_postrouting),
- C(V4, NAT,CUSTOM_CHAINS, prerouting_rule),
- C(V4, NAT,CUSTOM_CHAINS, postrouting_rule),
+ C(ANY, NAT,UNSPEC,delegate_prerouting),
+ C(ANY, NAT,UNSPEC,delegate_postrouting),
+ C(ANY, NAT,CUSTOM_CHAINS, prerouting_rule),
+ C(ANY, NAT,CUSTOM_CHAINS, postrouting_rule),
C(ANY, MANGLE, UNSPEC,mssfix),
C(ANY, MANGLE, UNSPEC,fwmark),
diff --git a/redirects.c b/redirects.c
index 5b8d7a9..0751e93 100644
--- a/redirects.c
+++ b/redirects.c
@@ -116,11 +116,26 @@ check_families(struct uci_element *e, struct fw3_redirect
*r)
static bool
compare_addr(struct fw3_address *a, struct fw3_address *b)
{
- if (a-family != FW3_FAMILY_V4 || b-family != FW3_FAMILY_V4)
+ if (a-family != b-family)
return false;
- return ((a-address.v4.s_addr a-mask.v4.s_addr) ==
- (b-address.v4.s_addr a-mask.v4.s_addr));
+ if (a-family == FW3_FAMILY_V4)
+ {
+ return ((a-address.v4.s_addr a-mask.v4.s_addr) ==
+ (b-address.v4.s_addr b-mask.v4.s_addr));
+ }
+ else if (a-family == FW3_FAMILY_V6)
+ {
+ int i;
+ for (i = 0; i 16; i++)
+ {
+ if ((a-address.v6.s6_addr[i] a-mask.v6.s6_addr[i])
!=
+ (b-address.v6.s6_addr[i] b-mask.v6.s6_addr[i]))
+ return false;
+ }
+ return true;
+ }
+ return false;
}
static bool
@@ -278,6 +293,7 @@ fw3_load_redirects(struct fw3_state *state, struct
uci_package *p)
else
{
set(redir-_src-flags, FW3_FAMILY_V4,
redir-target);
+ set(redir-_src-flags, FW3_FAMILY_V6,
redir-target);
redir-_src-conntrack = true;
valid = true;
@@ -293,6 +309,9 @@ fw3_load_redirects(struct fw3_state *state, struct
uci_package *p)
set(redir-_dest-flags, FW3_FAMILY_V4,
FW3_FLAG_ACCEPT);
set(redir-_dest-flags, FW3_FAMILY_V4,
FW3_FLAG_DNAT);
set(redir-_dest-flags, FW3_FAMILY_V4,
FW3_FLAG_SNAT);
+ set(redir-_dest-flags, FW3_FAMILY_V6,
FW3_FLAG_ACCEPT);
+ set(redir-_dest-flags, FW3_FAMILY_V6,
FW3_FLAG_DNAT);
+ set(redir-_dest-flags, FW3_FAMILY_V6,
FW3_FLAG_SNAT);
}
}
}
@@ -309,6 +328,7 @@ fw3_load_redirects(struct fw3_state *state, struct
uci_package *p)
else
{
set(redir-_dest-flags, FW3_FAMILY_V4,
redir-target);
+ set(redir-_dest-flags, FW3_FAMILY_V6,
redir-target);
redir-_dest-conntrack = true;
valid =
[OpenWrt-Devel] TP-Link v3 header format description
Hey Weijie Gao, 2015-08-05 20:07 GMT+02:00 Weijie Gao hackpas...@gmail.com: This patch adds header version 2 option for mktplinkfw. As long as we talk about the same, the new header version is v3. The v2 header is already covered by mktplinkfw2.c. Currently, I'm working on the same topic. Everything that is known so far about the new v3 header is documented in Martins repository: https://github.com/xdarklight/mktplinkfw3/blob/master/README.md (please take care of the not yet merged pull request). Maybe you can confirm/deny what I figured out so far or add missing informations. It would be nice, if you (or anyone else) can extend your v3 header creation patch, using the provided informations. It should be possible the write the complete verification part (-i option). For the creation part, (only) the private key from tp-link is missing. The version 2 header is used for AR/QCA firmwares and is not the same as the header generated by mktplinkfw2. Instead, it is nearly the same as version 1 header except for the header version and the RSA signature. The header version 2 support is used for newer TP-Link routers which have only a 64kb bootloader part, e.g. TL-WDR6500 v2. --- tools/firmware-utils/src/mktplinkfw.c | 25 + 1 file changed, 21 insertions(+), 4 deletions(-) IMHO the v3 header is an extension of the v2 header, since TP-Link switched from v2 to v3 on already deployed devices like the TD-W8980v1. That's why *I* would prefer to either create a mktplinkfw3.c or add the required the changes to mktplinkfw2.c. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v4 3/4] sunxi: create KDIR_TMP, build boot.img in it
It's nice to have a distinction between files which are built during the normal OpenWrt build process and ones that are created by the ImageBuilder (like it already exists on some other targets). This also gives boot.img a profile-specific prefix as it contains profile- specific data. Signed-off-by: Matthias Schiffer mschif...@universe-factory.net --- target/linux/sunxi/image/Makefile | 16 ++-- 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/target/linux/sunxi/image/Makefile b/target/linux/sunxi/image/Makefile index 19ab935..45e8dea 100644 --- a/target/linux/sunxi/image/Makefile +++ b/target/linux/sunxi/image/Makefile @@ -8,10 +8,14 @@ include $(TOPDIR)/rules.mk include $(INCLUDE_DIR)/image.mk include $(INCLUDE_DIR)/host.mk +KDIR_TMP:=$(KDIR)/tmp + FAT32_BLOCK_SIZE=1024 FAT32_BLOCKS=$(shell echo $$(($(CONFIG_SUNXI_SD_BOOT_PARTSIZE)*1024*1024/$(FAT32_BLOCK_SIZE define Image/BuildKernel + -mkdir -p $(KDIR_TMP) + mkimage -A arm -O linux -T kernel -C none \ -a 0x40008000 -e 0x40008000 \ -n 'ARM OpenWrt Linux-$(LINUX_VERSION)' \ @@ -29,16 +33,16 @@ define Image/BuildKernel endef define Image/Build/SDCard - rm -f $(KDIR)/boot.img - mkdosfs $(KDIR)/boot.img -C $(FAT32_BLOCKS) + rm -f $(KDIR_TMP)/$(IMG_PREFIX)-$(PROFILE)-boot.img + mkdosfs $(KDIR_TMP)/$(IMG_PREFIX)-$(PROFILE)-boot.img -C $(FAT32_BLOCKS) - mcopy -i $(KDIR)/boot.img $(KDIR)/uboot-sunxi-$(PROFILE)-boot.scr ::boot.scr - mcopy -i $(KDIR)/boot.img $(DTS_DIR)/$(2).dtb ::dtb - mcopy -i $(KDIR)/boot.img $(BIN_DIR)/$(IMG_PREFIX)-uImage ::uImage + mcopy -i $(KDIR_TMP)/$(IMG_PREFIX)-$(PROFILE)-boot.img $(KDIR)/uboot-sunxi-$(PROFILE)-boot.scr ::boot.scr + mcopy -i $(KDIR_TMP)/$(IMG_PREFIX)-$(PROFILE)-boot.img $(DTS_DIR)/$(2).dtb ::dtb + mcopy -i $(KDIR_TMP)/$(IMG_PREFIX)-$(PROFILE)-boot.img $(BIN_DIR)/$(IMG_PREFIX)-uImage ::uImage ./gen_sunxi_sdcard_img.sh \ $(BIN_DIR)/$(IMG_PREFIX)-$(PROFILE)-sdcard-vfat-$(1).img \ - $(KDIR)/boot.img \ + $(KDIR_TMP)/$(IMG_PREFIX)-$(PROFILE)-boot.img \ $(KDIR)/root.$(1) \ $(CONFIG_SUNXI_SD_BOOT_PARTSIZE) \ $(CONFIG_TARGET_ROOTFS_PARTSIZE) \ -- 2.5.0 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lighttpd 1.4.36 and file descriptors limit issue - OpenWrt related?
On 13 August 2015 at 20:16, Jonas Gorski j...@openwrt.org wrote: On Thu, Aug 13, 2015 at 8:00 PM, Rafał Miłecki zaj...@gmail.com wrote: There is an issue with handling relatively big (4 MiB+) files in lighttpd after the upgrade to the 1.4.36: https://github.com/openwrt/packages/issues/1658 It seems lighttpd is running out of file descriptors and is replying with: 413 - Request Entity Too Large I also reported this issue upstream: http://article.gmane.org/gmane.comp.web.lighttpd/5370 I received following suggestion (on the IRC) pointing OpenWrt kernel: [19:45] sztanpet i shall blame the openwrt kernel [19:45] rmilecki sztanpet: what exactly? I can modify the config if needed [19:45] rmilecki or the sources if you have anything to test [19:45] sztanpet i have no idea [19:45] rmilecki oh [19:46] sztanpet but since the issue is such a core issue that everyone would be seeing it and that is not the case, that tells me its probably not lighttpd Can you think of anything in OpenWrt kernel that could cause such a problem? Have you tried if changing the libc makes any difference? Might be a bug in musl, might a not quite proper usage that glibc allows, but musl doesn't, etc pp. I was actually using 15.05 (which uses uClibc). I tried OpenWrt's trunk (which uses musl) and the problem exists there too. -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/5] kernel: move linux, part-probe dt parsing in generic code
No; I don't think it was. Patches weren't acked afaik and it doesn't seem to be in the next tree. http://lists.infradead.org/pipermail/linux-mtd/2015-May/059226.html -Original Message- From: Rafał Miłecki [mailto:zaj...@gmail.com] Sent: Wednesday, August 12, 2015 9:05 PM To: Mathieu Olivari Cc: Felix Fietkau; Jonas Gorski; John Crispin; OpenWrt Development List Subject: Re: [OpenWrt-Devel] [PATCH 1/5] kernel: move linux, part-probe dt parsing in generic code On 13 August 2015 at 04:37, Mathieu Olivari math...@codeaurora.org wrote: The linux,part-probe dts parsing is a pretty neat generic feature. It has been posted to kernel.org and could easily be reused by all targets. Was it accepted mainline? If so, you should use 0xx prefix for this patch. Otherwise it's OK. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v4 4/4] sunxi: respect CONFIG_TARGET_IMAGES_GZIP
Signed-off-by: Matthias Schiffer mschif...@universe-factory.net --- target/linux/sunxi/image/Makefile | 4 1 file changed, 4 insertions(+) diff --git a/target/linux/sunxi/image/Makefile b/target/linux/sunxi/image/Makefile index 45e8dea..905188b 100644 --- a/target/linux/sunxi/image/Makefile +++ b/target/linux/sunxi/image/Makefile @@ -47,6 +47,10 @@ define Image/Build/SDCard $(CONFIG_SUNXI_SD_BOOT_PARTSIZE) \ $(CONFIG_TARGET_ROOTFS_PARTSIZE) \ $(KDIR)/uboot-sunxi-$(PROFILE)-u-boot-with-spl.bin + + ifneq ($(CONFIG_TARGET_IMAGES_GZIP),) + gzip -f9n $(BIN_DIR)/$(IMG_PREFIX)-$(PROFILE)-sdcard-vfat-$(1).img + endif endef define Image/Build/Profile/A10-OLinuXino-Lime -- 2.5.0 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [kernel] at91: Backport determine_rate prototype fix
From: Ben Whitten ben.whit...@gmail.com
This patch is backport of a fix to a USB prototype mismatch bug found
in 3.18 kernels, originally submitted by Boris Brezillon [1].
The symptom of this bug was that devices attached to the at91 using
at91_ohci on a hub never appeared and failed to initialise.
[1] http://www.spinics.net/lists/linux-usb/msg125969.html
Signed-off-by: Ben Whitten ben.whit...@gmail.com
---
.../201-ARM-at91-usb-determine_rate-backport.patch | 20
1 file changed, 20 insertions(+)
create mode 100644
target/linux/at91/patches/201-ARM-at91-usb-determine_rate-backport.patch
diff --git
a/target/linux/at91/patches/201-ARM-at91-usb-determine_rate-backport.patch
b/target/linux/at91/patches/201-ARM-at91-usb-determine_rate-backport.patch
new file mode 100644
index 000..d083628
--- /dev/null
+++ b/target/linux/at91/patches/201-ARM-at91-usb-determine_rate-backport.patch
@@ -0,0 +1,20 @@
+--- a/drivers/clk/at91/clk-usb.c
b/drivers/clk/at91/clk-usb.c
+@@ -59,7 +59,7 @@ static unsigned long at91sam9x5_clk_usb_
+ static long at91sam9x5_clk_usb_determine_rate(struct clk_hw *hw,
+ unsigned long rate,
+ unsigned long *best_parent_rate,
+- struct clk_hw **best_parent_hw)
++ struct clk **best_parent_clk)
+ {
+ struct clk *parent = NULL;
+ long best_rate = -EINVAL;
+@@ -91,7 +91,7 @@ static long at91sam9x5_clk_usb_determine
+ best_rate = tmp_rate;
+ best_diff = tmp_diff;
+ *best_parent_rate = tmp_parent_rate;
+-*best_parent_hw = __clk_get_hw(parent);
++*best_parent_clk = parent;
+ }
+
+ if (!best_diff || tmp_rate rate)
--
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH packages] lighttpd: backport a fix for running out of filedescriptors
It was breaking uploads of files 4 MiB+. This patch fixes:
https://github.com/openwrt/packages/issues/1658
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
This should be applied to both: master and 15.05 branch.
---
...filedescriptors-when-uploading-large-file.patch | 26 ++
1 file changed, 26 insertions(+)
create mode 100644
net/lighttpd/patches/001-fix-out-of-filedescriptors-when-uploading-large-file.patch
diff --git
a/net/lighttpd/patches/001-fix-out-of-filedescriptors-when-uploading-large-file.patch
b/net/lighttpd/patches/001-fix-out-of-filedescriptors-when-uploading-large-file.patch
new file mode 100644
index 000..6ef9403
--- /dev/null
+++
b/net/lighttpd/patches/001-fix-out-of-filedescriptors-when-uploading-large-file.patch
@@ -0,0 +1,26 @@
+From: =?UTF-8?q?Stefan=20B=C3=BChler?= stbueh...@web.de
+Date: Thu, 13 Aug 2015 18:44:27 +
+Subject: [PATCH] fix out-of-filedescriptors when uploading large files
+ (fixes #2660, thx rmilecki)
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+From: Stefan Bühler stbueh...@web.de
+
+git-svn-id: svn://svn.lighttpd.net/lighttpd/branches/lighttpd-1.4.x@3009
152afb58-edef-0310-8abb-c4023f1b3aa9
+---
+ src/chunk.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/src/chunk.c
b/src/chunk.c
+@@ -432,7 +432,7 @@ static int chunkqueue_append_to_tempfile
+* */
+
+ if (NULL != dest-last
+- FILE_CHUNK != dest-last-type
++ FILE_CHUNK == dest-last-type
+dest-last-file.is_temp
+-1 != dest-last-file.fd
+0 == dest-last-offset) {
--
1.8.4.5
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 6/6] bcm53xx: R8000 handle PEX8603 switch
On Wed, 2015-08-12 at 22:01 +0200, Hauke Mehrtens wrote: On 07/15/2015 12:11 PM, Ian Kent wrote: On Tue, 2015-07-14 at 18:19 +0200, Rafał Miłecki wrote: On 28 June 2015 at 05:37, Ian Kent ra...@themaw.net wrote: Let me rework this using the bus number as you recommend. I'll repost my updated patch series once I've done that. Hi Ian, Is there any chance you'll find a moment for it anytime soon? It'd be awesome to get R8000 support for CC release. I have reworked the patch and a broken package build problem I had is gone but I didn't get time to fix build problems with a third patch I have. Just didn't get time last weekend and this week has been quite busy too. I'll try and get onto this in the next few days. Ian Hi Ian, you patch looks better than the hack Broadcom did in their vendor driver. I thought so, ;) Could you send me a lspci output or the content of /proc/bus/pci/devices of the original firmware or of OpenWrt with your patch applied? I would prefer lspci because it is easier to read but cat from /proc/bus/pci/devices also works. I do not have such a device and want to understand how this PCIe switch looks like on the software side, so we can fix the domain, bus, slot, function mixup. I haven't been able to build OpenWrt for a while now and that's why I haven't been able to test my changes to the patch. I really wish we could avoid committing changes that don't build but I know it isn't that simple. I have got some other lists (around somewhere) based on output, mostly from the Vendor firmware, and one where I went through the devices and listed what they are along with and their pci ids so I could try and understand what was going on. I could try and find that and post it if it would be useful. Note that it was just used to understand what was what so it isn't pretty but should have quite a bit of info in it. There's no question the current patch is wrong so I don't recommend it be used. I can however post my updated patch now on the understanding that it hasn't been tested at all, which might be good for initial review anyway. On the hardware side this SoC has 3 PCIe controllers, but one shares a PHY with the USB 3.0 controller. Instead of using the 3rd PCIe controller they used USB 3.0 and split one of the PCIe controllers into 2 PCIE lanes. Right, I didn't get that, mmm ... Ian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] TP-Link v3 header format description
On 14 August 2015 at 01:49, Mathias Kresin open...@kresin.me wrote: Hey Weijie Gao, 2015-08-05 20:07 GMT+02:00 Weijie Gao hackpas...@gmail.com: This patch adds header version 2 option for mktplinkfw. As long as we talk about the same, the new header version is v3. The v2 header is already covered by mktplinkfw2.c. Currently, I'm working on the same topic. Everything that is known so far about the new v3 header is documented in Martins repository: https://github.com/xdarklight/mktplinkfw3/blob/master/README.md (please take care of the not yet merged pull request). Maybe you can confirm/deny what I figured out so far or add missing informations. It would be nice, if you (or anyone else) can extend your v3 header creation patch, using the provided informations. It should be possible the write the complete verification part (-i option). For the creation part, (only) the private key from tp-link is missing. Hi, Never played with tplink's v3 header. But I found on other devices that the RSA2048-SHA1 implementation there was flawed in that it used pubkeys from firmwares to verifying signatures. Hmm, is it possible that this v3 header from tplink also has such vulnerability? yousong The version 2 header is used for AR/QCA firmwares and is not the same as the header generated by mktplinkfw2. Instead, it is nearly the same as version 1 header except for the header version and the RSA signature. The header version 2 support is used for newer TP-Link routers which have only a 64kb bootloader part, e.g. TL-WDR6500 v2. --- tools/firmware-utils/src/mktplinkfw.c | 25 + 1 file changed, 21 insertions(+), 4 deletions(-) IMHO the v3 header is an extension of the v2 header, since TP-Link switched from v2 to v3 on already deployed devices like the TD-W8980v1. That's why *I* would prefer to either create a mktplinkfw3.c or add the required the changes to mktplinkfw2.c. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] i get no image for TL-WA7510
On Thu, 13 Aug 2015 10:42:17 +0200 Sławomir Demeszko s.demes...@wireless-instruments.com wrote: W dniu 12.08.2015 o 21:29, smile...@gmail.com pisze: I miss not only the TL-WA7510 image. I missing also several images for other 4MB Flash-Router. Is there a Funktion in Openwrt which build images only if the image-size not excite the flash-size? I found there is. I was also wonder for half day why image for my board was not created. I think there should be at least a warning and option to bypass this check it would be helpful to estimate how many bytes we need to reclaim to fit. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel It will be great. pgp6_Iwv06mNc.pgp Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
