Re: [OpenWrt-Devel] Is Linksys/Belkin lying (again) about being open source (WRT1200AC router) ?
Hi, I don't get this discussion, few days Imre Kaloz admitted he will work on WRT1200AC so this means that Belkin reached out to him... Regards, Jacek On 16.01.2015 12:45, Bjørn Mork wrote: > Fernando Frediani writes: > >> I'm not entirely sure of the status of WRT1200AC, but if there is >> nothing here in OpenWRT and nothing else much can be found on the web >> they are once again lying. They are publishing intentions as if it was >> something that was already done and consolidated, ready for any buyer >> to enjoy. If there is something going on between them and OpenWRT we >> are not aware, at least not via this list. > > You should probably take a closer look at these two emails. Preferably > in your own list archive if you have one, as the pipermail archive is > missing some of the more interesting details. Like who Marvell chose to > CC the driver announcement to, and which email address they used > > https://lists.openwrt.org/pipermail/openwrt-devel/2014-December/030229.html > https://lists.openwrt.org/pipermail/openwrt-devel/2015-January/030526.html > > I might be reading too much between the lines here, but this looks very > promising to me. > > Yes, I also regularily get frustrated with marketing people overselling > features, and selling them before they are ready. But you should > realize that Belkin is not the only vendor doing that. The really > annoying thing with the "WRTs" is that they oversell a feature we care > so deeply about - opensource support. But I believe we should appreciate > the fact that the marketing people find this feature interesting, and do > our best to keep it that way. And just realize that overselling is part > of the game. > > In any case, we are much better off if this list is used for technical > discussions instead of vendor bashing. > > > Bjørn (with absolutely no shares in neither Belkin, Marvell nor OpenWRT) > ___ > 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] Status of DFS in OpenWrt -> ath9k
Hello, I have CONFIG_PACKAGE_ATH_DFS=y and still cannot use this... any idea how / what should be debugged? Jacek On 03.07.2014 18:14, Martin Garbe wrote: > The command "iw phy ..." only shows hardware capabilities. For DFS > hardware AND software support is needed. In OpenWRT you need hostapd to > support DFS too. The config parameter CONFIG_PACKAGE_ATH_DFS explicitely > activates DFS in hostapd. This parameter is not set by default. > For more information see also the patch with comment in git: > http://git.openwrt.org/?p=openwrt.git;a=commitdiff;h=5fd90c893f86e88150ea81be7afd337ac1b802aa > > Regards, > Martin > > >> > Jacek >> > >> > On 07/02/14 22:50, Martin Garbe wrote: >>> >> On 7/1/14, 10:04 AM, Jacek Kikiewicz wrote: >>>> >>> Hello, >>>> >>> >>>> >>> I have few APs that are using ath9k driver, I've read that now DFS is >>>> >>> supported on that driver, >>>> >>> so I compiled latest revision (yesterday: 41415), and started >>>> >>> playing, basically when as per >>>> >>> manual / howto I run 'iw phy phy1 info' I can see DFS channels, >>>> >>> exactly like in howto on a wiki, problem is however >>>> >>> that I cannot make it work on those channels (I've tried 52,56,100, >>>> >>> 104), after changing config and restarting wifi >>>> >>> I saw in dmesg 'interface wlan1 entered disabled mode) - I tried with >>>> >>> HT20 for the beginning. >>>> >>> So, question here is, should this work in current state or is there >>>> >>> still some support missing? >>>> >>> I can pull any logs / settings that are of interest. >>> >> Have you elected >>> >> CONFIG_PACKAGE_ATH_DFS=y >>> >> when compiling the driver? This way you agree to the fact that your >>> >> hardware supports DFS. After that DFS channels can be selected. >>> >> >>> >> ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Status of DFS in OpenWrt -> ath9k
Hi, I sure selected this option, as I said command 'iw phy phy1 info' does in fact show DFS channels, but I just cannot set them for usage... Jacek On 07/02/14 22:50, Martin Garbe wrote: On 7/1/14, 10:04 AM, Jacek Kikiewicz wrote: Hello, I have few APs that are using ath9k driver, I've read that now DFS is supported on that driver, so I compiled latest revision (yesterday: 41415), and started playing, basically when as per manual / howto I run 'iw phy phy1 info' I can see DFS channels, exactly like in howto on a wiki, problem is however that I cannot make it work on those channels (I've tried 52,56,100, 104), after changing config and restarting wifi I saw in dmesg 'interface wlan1 entered disabled mode) - I tried with HT20 for the beginning. So, question here is, should this work in current state or is there still some support missing? I can pull any logs / settings that are of interest. Have you elected CONFIG_PACKAGE_ATH_DFS=y when compiling the driver? This way you agree to the fact that your hardware supports DFS. After that DFS channels can be selected. Martin Thanks! Jacek ___ 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 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Status of DFS in OpenWrt -> ath9k
Hello, I have few APs that are using ath9k driver, I've read that now DFS is supported on that driver, so I compiled latest revision (yesterday: 41415), and started playing, basically when as per manual / howto I run 'iw phy phy1 info' I can see DFS channels, exactly like in howto on a wiki, problem is however that I cannot make it work on those channels (I've tried 52,56,100, 104), after changing config and restarting wifi I saw in dmesg 'interface wlan1 entered disabled mode) - I tried with HT20 for the beginning. So, question here is, should this work in current state or is there still some support missing? I can pull any logs / settings that are of interest. Thanks! Jacek ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Power line (PLC) support - atheros platform.
Hello Florian, I already ported OpenWRT to it and have it running on this router with 95% functionality, I will install open-plc-tools and play with this. Thanks! Jacek On 25.04.2014 18:48, Florian Fainelli wrote: First things first: do you have OpenWrt installed on your device, or are you using the stock firmware? If the former, you could start installing the open-plc-utils, and query for an AR7400 waiting for a firmware to be loaded. I can't remember which tool does that from the top of my head, but the open-plc-utils github has a fairly extensive documentation on this. If you do not yet have OpenWrt running on your device, you should probably start looking at your device sources and figure out how many modifications you need to make to support it. There is a continuous stream of patches for adding specific board support to the ar71xx, so I would start looking at the recent patches which add support for boards similar to yours. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Power line (PLC) support - atheros platform.
Hello Florian, Thanks for replying. Those chips usually do not require a driver per-se, but just a user space program to load their firmware and configuration blob. Well that would be easier / better. If you can figure out how the AR7400 is connected (presumably via MII to one port of the switch) you surely can extract the firmware image and the PIB (configuration blob). Then you should be able to use the open-plc utilities [1] to load those files and configure your PLC chip (security key etc...), those utilities are already packaged in OpenWrt. [1]: https://github.com/qca/open-plc-utils Any hint how do I do that? :) As I said, unfortunately I am pretty clueless on that front. Jacek ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Power line (PLC) support - atheros platform.
Hello, I am working on porting OpenWRT to D-link DHP-1565 (wiki for it: http://wiki.openwrt.org/toh/d-link/dhp-1565). It's atheros platform, I have inital support ready (with working switch, wifi, usb etc) but as this comes with PLC built-in (Atheros AR7400 chip) it would be pretty nice to have this working, but to be honest I am not sure where to start at all with this (writing driver is way out of my league). So question here, is there any driver for AR7400 in openWRT? Only device with PLC support in openWRT I found is devolo USB extender: http://wiki.openwrt.org/toh/devolo/dlan-usb-extender but this is different platform. There is GPL source for original firmware for my d-link but drivers are obviously binary blobs :( Any help / advice will help :) thanks! Jacek ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [ar71xx] WNDAP360 adding wifi LED support
From: Jacek Kikiewicz Re-sending as previous did not get where it should. I added WIFI LED support (so now AP blinks nicely), I removed WPS button GPIO (as it doesn't exist) and changed GPIO for reset button. Signed-off-by: Jacek Kikiewicz --- Index: target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c === --- target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (revision 40458) +++ target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (working copy) @@ -28,9 +28,7 @@ #define WNDAP360_GPIO_LED_POWER_GREEN 2 /* Reset button - next to the power connector */ -#define WNDAP360_GPIO_BTN_RESET3 -/* WPS button - next to a led on right */ -#define WNDAP360_GPIO_BTN_WPS 8 +#define WNDAP360_GPIO_BTN_RESET8 #define WNDAP360_KEYS_POLL_INTERVAL20 /* msecs */ #define WNDAP360_KEYS_DEBOUNCE_INTERVAL(3 * WNDAP360_KEYS_POLL_INTERVAL) @@ -95,6 +93,9 @@ ARRAY_SIZE(wndap360_gpio_keys), wndap360_gpio_keys); +ap9x_pci_setup_wmac_led_pin(0, 5); +ap9x_pci_setup_wmac_led_pin(1, 5); + ap94_pci_init(art + WNDAP360_CALDATA0_OFFSET, art + WNDAP360_WMAC0_MAC_OFFSET, art + WNDAP360_CALDATA1_OFFSET, ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Cannot get patch into patchwork
Hello, Sorry for sending same patch few times, for some reason I cannot get it to patchwork... I configured my client to send plain text, there are no attachments, format should be good... Can someone advice what am I doing wrong here? Thanks, Jacek ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [ar71xx] WNDAP360 add Wifi LED support
From: Jacek Kikiewicz Re-sending as previous did not get where it should. I added WIFI LED support (so now AP blinks nicely), I removed WPS button GPIO (as it doesn't exist) and changed GPIO for reset button. Signed-off-by: Jacek Kikiewicz --- Index: target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c === --- target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (revision 39638) +++ target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (working copy) @@ -28,9 +28,7 @@ #define WNDAP360_GPIO_LED_POWER_GREEN 2 /* Reset button - next to the power connector */ -#define WNDAP360_GPIO_BTN_RESET3 -/* WPS button - next to a led on right */ -#define WNDAP360_GPIO_BTN_WPS 8 +#define WNDAP360_GPIO_BTN_RESET8 #define WNDAP360_KEYS_POLL_INTERVAL20 /* msecs */ #define WNDAP360_KEYS_DEBOUNCE_INTERVAL(3 * WNDAP360_KEYS_POLL_INTERVAL) @@ -95,6 +93,9 @@ ARRAY_SIZE(wndap360_gpio_keys), wndap360_gpio_keys); +ap9x_pci_setup_wmac_led_pin(0, 5); +ap9x_pci_setup_wmac_led_pin(1, 5); + ap94_pci_init(art + WNDAP360_CALDATA0_OFFSET, art + WNDAP360_WMAC0_MAC_OFFSET, art + WNDAP360_CALDATA1_OFFSET, ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [ar71xx] WNDAP360 add Wifi LED support
From: Jacek Kikiewicz Re-sending as previous did not get where it should. I added WIFI LED support (so now AP blinks nicely), I removed WPS button GPIO (as it doesn't exist) and changed GPIO for reset button. Signed-off-by: Jacek Kikiewicz --- Index: target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c === --- target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (revision 39638) +++ target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (working copy) @@ -28,9 +28,7 @@ #define WNDAP360_GPIO_LED_POWER_GREEN 2 /* Reset button - next to the power connector */ -#define WNDAP360_GPIO_BTN_RESET3 -/* WPS button - next to a led on right */ -#define WNDAP360_GPIO_BTN_WPS 8 +#define WNDAP360_GPIO_BTN_RESET8 #define WNDAP360_KEYS_POLL_INTERVAL20 /* msecs */ #define WNDAP360_KEYS_DEBOUNCE_INTERVAL(3 * WNDAP360_KEYS_POLL_INTERVAL) @@ -95,6 +93,9 @@ ARRAY_SIZE(wndap360_gpio_keys), wndap360_gpio_keys); +ap9x_pci_setup_wmac_led_pin(0, 5); +ap9x_pci_setup_wmac_led_pin(1, 5); + ap94_pci_init(art + WNDAP360_CALDATA0_OFFSET, art + WNDAP360_WMAC0_MAC_OFFSET, art + WNDAP360_CALDATA1_OFFSET, ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH][ar71xx] - WNDAP360 add Wifi LED support
From: Jacek Kikiewicz Re-sending as previous did not get where it should. I added WIFI LED support (so now AP blinks nicely), I removed WPS button GPIO (as it doesn't exist) and changed GPIO for reset button. Signed-off-by: Jacek Kikiewicz --- Index: target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c === --- target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (revision 39638) +++ target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (working copy) @@ -28,9 +28,7 @@ #define WNDAP360_GPIO_LED_POWER_GREEN 2 /* Reset button - next to the power connector */ -#define WNDAP360_GPIO_BTN_RESET3 -/* WPS button - next to a led on right */ -#define WNDAP360_GPIO_BTN_WPS 8 +#define WNDAP360_GPIO_BTN_RESET8 #define WNDAP360_KEYS_POLL_INTERVAL20 /* msecs */ #define WNDAP360_KEYS_DEBOUNCE_INTERVAL(3 * WNDAP360_KEYS_POLL_INTERVAL) @@ -95,6 +93,9 @@ ARRAY_SIZE(wndap360_gpio_keys), wndap360_gpio_keys); +ap9x_pci_setup_wmac_led_pin(0, 5); +ap9x_pci_setup_wmac_led_pin(1, 5); + ap94_pci_init(art + WNDAP360_CALDATA0_OFFSET, art + WNDAP360_WMAC0_MAC_OFFSET, art + WNDAP360_CALDATA1_OFFSET, ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] problem to building image for tp-link wr-841nd
Well it says images are too big so probably your images are... too big :) On 03/21/2014 04:44 PM, Flavio Rodrigo LEonel wrote: > i am trying building the openwrt custom image for wr841nd, but no > complete and report this mensages > > /home/flavio/MCELLOS/staging_dir/host/bin/mktplinkfw -H 0x08410007 -W > 1 -F 4M -N OpenWrt -V r39792 -s -X 0x4 -k > /home/flavio/MCELLOS/build_dir/target-mips_34kc_uClibc-0.9.33.2/linux-ar71xx_generic/tmp/kernel-tl-wr841nd-v7.bin > -r > /home/flavio/MCELLOS/build_dir/target-mips_34kc_uClibc-0.9.33.2/linux-ar71xx_generic/root.squashfs-raw > -a 0x4 -j -o > /home/flavio/MCELLOS/bin/ar71xx/openwrt-ar71xx-generic-tl-wr841nd-v7-squashfs-sysupgrade.bin > [mktplinkfw] kernel length aligned to 1030144 > [mktplinkfw] *** error: images are too big > make[5]: [install] Error 255 (ignored) > [mktplinkfw] kernel length aligned to 1022216 > [mktplinkfw] *** error: images are too big > make[5]: [install] Error 255 (ignored) > [mktplinkfw] kernel length aligned to 1022216 > [mktplinkfw] *** error: images are too big > make[5]: [install] Error 255 (ignored) > > > > can someone help me? > ___ > 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] 12.09.1 build error: rt2x00lib.ko is missing
Hi Alex, If you really don't care about compiling newest version just try some older revision... Not a great solution but should help if you want to get up running quickly it might work... Regards, Jacek On 11/30/2013 06:47 PM, Alex Henrie wrote: > When I try to compile OpenWRT, I get the following error: > > mkdir -p /home/alex/workspace/openwrt/bin/ar71xx/packages > /home/alex/workspace/openwrt/build_dir/linux-ar71xx_generic/compat-wireless-2013-06-27/ipkg-ar71xx/kmod-rt2x00-lib/CONTROL > /home/alex/workspace/openwrt/staging_dir/target-mips_r2_uClibc-0.9.33.2/pkginfo > ERROR: module > '/home/alex/workspace/openwrt/build_dir/linux-ar71xx_generic/compat-wireless-2013-06-27/drivers/net/wireless/rt2x00/rt2x00lib.ko' > is missing. > make[3]: *** > [/home/alex/workspace/openwrt/bin/ar71xx/packages/kmod-rt2x00-lib_3.3.8+2013-06-27-1_ar71xx.ipk] > Error 1 > make[3]: Leaving directory `/home/alex/workspace/openwrt/package/mac80211' > make[2]: *** [package/mac80211/compile] Error 2 > make[2]: Leaving directory `/home/alex/workspace/openwrt' > make[1]: *** > [/home/alex/workspace/openwrt/staging_dir/target-mips_r2_uClibc-0.9.33.2/stamp/.package_compile] > Error 2 > make[1]: Leaving directory `/home/alex/workspace/openwrt' > make: *** [world] Error 2 > > I am running Lubuntu 13.10 x64 and building r38863 for the Buffalo > WZR-HP-AG300H. I followed the instructions at > https://dev.openwrt.org/wiki/GetSource and > http://wiki.openwrt.org/doc/howto/easy.build > > To be honest, all I really want is IPv6 support. Will there be an > official 12.09.1 binary that I can use soon? > > -Alex > ___ > 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] AR9344 wifi dying on WD N600 routers
Hi, No it's not I'm afraid. It is used anyway, if it wasn;t ath9k driver would not bring up wifi interface, it would have wrong mac too. Jacek > Is it useful at all WRT to what Daniel was talking about? > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] AR9344 wifi dying on WD N600 routers
Hi, It's probably having wifi calibration data, wifi MAC etc. I assume it's same as ART is other Atheros based devices. > Would any of these be listed in the actual device flash? > > mtd shows: > [0.75] 0x-0x0004 : "u-boot" > [0.76] 0x0004-0x0005 : "u-boot-env" > [0.77] 0x0005-0x0006 : "devdata" > [0.77] 0x0006-0x0007 : "devconf" > [0.78] 0x0007-0x00ff : "firmware" > [0.81] 2 seama-fw partitions found on MTD device firmware > [0.82] 0x0007-0x001b : "kernel" > [0.82] 0x001b-0x00ff : "rootfs" > [0.83] mtd: partition "rootfs" set to be root filesystem > [0.83] 1 squashfs-split partitions found on MTD device rootfs > [0.84] 0x0037-0x00ff : "rootfs_data" > [0.85] 0x00ff-0x0100 : "radiocfg" > > What info does the radiocfg partition hold? Do we actually read it for > anything? > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WD MyNet N750: ar9344 + ar8327 switch, unclear on phy/mdio/mac wiring
Hi, There is a topic in openwrt forum: https://forum.openwrt.org/viewtopic.php?id=46864 about porting to this router. Would you mind to update it a bit with your progress, please? It would be easier to track for interested parties. Thanks! On 22.10.2013 18:04, Jay Carlson wrote: Since Newegg has dropped the price on the 3T3R Western Digital N750 Atheros wasp/S17 entry to $30, I expect some more interest in this standard-looking ar9344 + ar8327 platform. I've got a couple of n750s lying around, but I haven't made any progress on getting the gigabit switch connected up to the on-chip Ethernet. There's GPL source code for these "Project Seattle" platforms, and N600 support is in trunk. This helps, but the N600 uses the ar934x internal switch which is rather different from the gigabit NAT switch in these. There's GPL source for the N600 and N750 from WD, and it's in fairly good shape, but unfortunately the switch configuration is performed in scripts and/or a binary ag71xx driver. I think I should be able to imitate other ar934x+ar8327 devices, but I think I'm missing some concept, or I need to read some device state out of a stock device in order to replicate it. In the bootloader the ar8327 switch works, but I don't have bootloader source, and one of the last things the bootloader seems to do before boot is shut down the switch. (Perhaps this is to keep Linux from seeing anything from the net until the firewall is up.) And the interaction of MACs, PHYs and mdio buses makes my head hurt. One thing I do see is a bunch of phy_id garbage on mdio0:10-17 and six phy_ids of the ar8327 on mdio1:00-05. My *guess* is that ag71xx.0 is connected directly to port 0 of the ar8327 like the other wasp/s17 devices, but mdio1 is used instead of mdio0. I've made it as far as ag71xx.0 coming up in multi mode, but I seem to get the generic PHY instead of ar8327 despite the phy_ids matching up (and with what I think is a correct boardinfo.) (Also, something seems messed up with the openwrt firstboot squashfs split code: on the next reboot, the bootloader looks at the seama partition info and declares the kernel to not only be corrupt, but to have a non-ASCII md5sum. That kind of thing I feel competent to solve but there is little point if I can't get the wired ethernet up.) Does the switch setup problem sound familiar? I can back out all my printk garbage and post my (clueless) board setup code if it would help. I can mail a box to somebody who's worked with ar934x, although I've never mailed hardware outside this country (US) except for work. Jay Carlson n...@nop.com ___ 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] Add a new Amazon-SE board
On 18.10.2013 10:22, Marco Antonio Mauro wrote: On Fri, Oct 18, 2013 at 10:18 AM, Jacek Kikiewicz wrote: Well, if boot loader is not supported you have 2 choices: 1. Leave it 2. Make boot loader supported with some hard work :) 3. replace bootloader with uboot? Anyways internal pictures are here. https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=526141&fcc_id=RSE-TG585V8 I'm trying to get the source for the device, let's see what I can find. True, but this is risky and it would be good to have JTAG or proper soldering equipment + programmer to play with boot loader. I thin your option is a whole new level (unless there is ready boot loader) :) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Add a new Amazon-SE board
Hi, Well, if boot loader is not supported you have 2 choices: 1. Leave it 2. Make boot loader supported with some hard work :) The devices in linux based so there should be some way... Regards, Jacek On 18.10.2013 10:13, Marco Antonio Mauro wrote: On Thu, Oct 17, 2013 at 1:47 PM, Tomislav Požega wrote: thomson usually sticks with crappy broadcom so don't give much hope for AR9271.. It's a Ralink RT3070 it seems! The console log is here: http://pastebin.com/LCf2rFCv I didn't take it from my device as I'm having problems with the serial adapter which I'll be replacing soon. Should there be any differences between the log I'll take in the next days, as soon as I buy the new adapter, and this one I'll let you know. The bootloader is the Thomson one, and I don't think it's supported sadly. What can I do now? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Add a new Amazon-SE board
Hi, First start with gainig console access... Then you need to check what boot loader is there. Depending on what it is your next steps will vary, let's hope it's supported one :) On 17.10.2013 11:16, Marco Antonio Mauro wrote: Hi everyone, I have a Thomson TG585v8 Amazon-SE device. The device seems almost identical to the Netgear DGN1000B already in openwrt, and I'd like to add support for the specific board. But can't seem to figure out how to do it. I previously added support for a ralink device but the process seems different here. The board has: - Lantiq PSB50601HL v1.2 Processor, supposedly clocked at 266MHz - Winbond W25Q64BV SPI flash, 8MBytes - Winbond W9825G6H SDRAM, 32MBytes total - Broadcom BCM5325E switch - USB2 wifi card for AP, can't remove the EMI shield to confirm model but probably Atheros AR9271 - a couple buttons and leds. Can anyone give me some pointers on what to do? Thank you! PS: I'll add the device with the photos of the board to the wiki later ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] How to enable Seama firmware parser for Ramips?
Don't you have to have partition called rootfs in your definition? Then it should pick it up... Regards, Jacek On 09/24/2013 10:19 PM, Flávio Silveira wrote: > Good evening, > > I've tried trunk r38130 for D-Link DIR-610 A1, which uses Seama. > > Stock firmware accepts my openwrt build fine, but it can't find > rootfs while booting. > > Here is my dts file: http://codepad.org/ONZdgMZ3 > > Here is boot log: http://codepad.org/rLOjLHdy > > If there is any information missing, please ask! > > Thanks in advance, > Flavio ___ > 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
[OpenWrt-Devel] [PATCH] ar71xx Fix of mach file for WNDAP360, removed register USB device
Resending to group as this didn't get to patchwork... Removing one line in mach-wldap360.c Apparently registering usb device on newest trunk causes this AP not to boot... Since there is no USB socket in that device anyway this can be simply removed (and device boots then no problem). Signed-off-by: Jacek Kikiewicz --- Index: target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c === --- target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (revision 37834) +++ target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (working copy) @@ -87,8 +87,6 @@ ath79_register_eth(0); -ath79_register_usb(); - ath79_register_m25p80(NULL); ath79_register_leds_gpio(-1, ARRAY_SIZE(wndap360_leds_gpio), ___ 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
[OpenWrt-Devel] [PATCH] [ar71xx] Fix of mach file for WNDAP360, removed 'register USB device'
Removing one line in mach-wldap360.c Apparently registering usb device on newest trunk causes this AP not to boot... Since there is no USB socket in that device anyway this can be simply removed (and device boots then no problem). Signed-off-by: Jacek Kikiewicz --- Index: target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c === --- target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (revision 37834) +++ target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (working copy) @@ -87,8 +87,6 @@ ath79_register_eth(0); -ath79_register_usb(); - ath79_register_m25p80(NULL); ath79_register_leds_gpio(-1, ARRAY_SIZE(wndap360_leds_gpio), ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Has anyone ported the openwrt on beaglebone?
I can see you are running kernel from memory. I had similar problem when doing this. I'd advice two things to start with: 1. Flash kernel somewhere and try to run it from there OR 2. Put it into different spot in memory and then try booting (I had best results with end of memory). On 06/23/2013 10:57 AM, Artur Wronowski wrote: > I am working on it. > > I have some problem with boot kernel, it hangs: > > U-Boot# bootm 0x8020 > ## Booting kernel from Legacy Image at 8020 ... >Image Name: Linux >Image Type: ARM Linux Kernel Image (uncompressed) >Data Size:1649712 Bytes = 1.6 MiB >Load Address: 80008000 >Entry Point: 80008000 >Verifying Checksum ... OK >Loading Kernel Image ... OK > OK > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > > My target files (need clean up) is at > https://www.dropbox.com/home/Public/bbb/am33x > > Maybe someone can help. > > 2013/5/14 Hui HU : >> Would you share some useful information? Any link or document? Thank you. >> >> Hui >> >> ___ >> openwrt-devel mailing list >> openwrt-devel@lists.openwrt.org >> https://lists.openwrt.org/mailman/listinfo/openwrt-devel >> > > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [ar71xx] Fix for wrong eth0 mac assignment and fix for partition layout on Netgear WNDAP360
Signed-off-by: Jacek Kikiewicz Index: target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c === --- target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (revision 36968) +++ target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (working copy) @@ -76,7 +76,8 @@ ath79_register_mdio(0, ~(WNDAP360_LAN_PHYMASK)); -ath79_init_mac(ath79_eth0_data.mac_addr, art, 0); +// Reusing wifi MAC with offset of 1 as eth0 mac +ath79_init_mac(ath79_eth0_data.mac_addr, art + WNDAP360_WMAC0_MAC_OFFSET, 1); ath79_eth0_pll_data.pll_1000 = 0x; ath79_eth0_data.phy_if_mode = PHY_INTERFACE_MODE_RGMII; ath79_eth0_data.phy_mask = WNDAP360_LAN_PHYMASK; Index: target/linux/ar71xx/image/Makefile === --- target/linux/ar71xx/image/Makefile(revision 36968) +++ target/linux/ar71xx/image/Makefile(working copy) @@ -185,7 +185,7 @@ uap_pro_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,1536k(kernel),14208k(rootfs),256k(cfg)ro,64k(EEPROM)ro,15744k@0x5(firmware) ubdev_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,1024k(kernel),6464k(rootfs),64k(certs),256k(cfg)ro,64k(EEPROM)ro,7488k@0x5(firmware) whrhpg300n_mtdlayout=mtdparts=spi0.0:248k(u-boot)ro,8k(u-boot-env)ro,1024k(kernel),2752k(rootfs),64k(art)ro,3712k@0x4(firmware) -wndap360_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,1728k(kernel),6080k(rootfs),64k(art)ro,7808k@0x5(firmware) +wndap360_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,1728k(kernel),6016k(rootfs),64k(nvram)ro,64k(art)ro,7744k@0x5(firmware) wnr2000v3_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,1024k(kernel),2688k(rootfs),64k(art)ro,3712k@0x5(firmware) wndr3700_mtdlayout=mtdparts=spi0.0:320k(u-boot)ro,128k(u-boot-env)ro,1024k(kernel),6656k(rootfs),64k(art)ro,7680k@0x7(firmware) wndr3700v2_mtdlayout=mtdparts=spi0.0:320k(u-boot)ro,128k(u-boot-env)ro,1024k(kernel),14848k(rootfs),64k(art)ro,15872k@0x7(firmware) @@ -883,7 +883,7 @@ $(eval $(call SingleProfile,MyLoader,$(fs_64k),WPE72_16M,wpe72,,ttyS0,115200,0x100,16M)) # This is used with AthGzip profile for now -$(eval $(call SingleProfile,AthGzip,$(fs_64k),WNDAP360,wndap360,WNDAP360,ttyS0,9600,$$(wndap360_mtdlayout),1769472,6225920,KRuImage)) +$(eval $(call SingleProfile,AthGzip,$(fs_64k),WNDAP360,wndap360,WNDAP360,ttyS0,9600,$$(wndap360_mtdlayout),1769472,6160384,KRuImage)) $(eval $(call SingleProfile,Netgear,$(fs_64k),WNR2000V3,wnr2000v3,WNR2000V3,ttyS0,115200,$$(wnr2000v3_mtdlayout),2003,WNR2000V3,"" NA,)) $(eval $(call SingleProfile,Netgear,$(fs_64k),WNDR3700V1,wndr3700,WNDR3700,ttyS0,115200,$$(wndr3700_mtdlayout),3700,WNDR3700,"" NA,)) $(eval $(call SingleProfile,Netgear,$(fs_64k),WNDR3700V2,wndr3700v2,WNDR3700,ttyS0,115200,$$(wndr3700v2_mtdlayout),3701,WNDR3700v2,"",-H 29763654+16+64)) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [ar71xx] Add support for Netgear WNDAP360
Here is corrected version (only thing not working are wifi LEDs):
Signed-off-by: Jacek Kikiewicz
---
Index: target/linux/ar71xx/image/Makefile
===
--- target/linux/ar71xx/image/Makefile (revision 36156)
+++ target/linux/ar71xx/image/Makefile (working copy)
@@ -185,6 +185,7 @@
uap_pro_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,1536k(kernel),14208k(rootfs),256k(cfg)ro,64k(EEPROM)ro,15744k@0x5(firmware)
ubdev_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,1024k(kernel),6464k(rootfs),64k(certs),256k(cfg)ro,64k(EEPROM)ro,7488k@0x5(firmware)
whrhpg300n_mtdlayout=mtdparts=spi0.0:248k(u-boot)ro,8k(u-boot-env)ro,1024k(kernel),2752k(rootfs),64k(art)ro,3712k@0x4(firmware)
+wndap360_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,1728k(kernel),6080k(rootfs),64k(art)ro,7808k@0x5(firmware)
wndr3700_mtdlayout=mtdparts=spi0.0:320k(u-boot)ro,128k(u-boot-env)ro,1024k(kernel),6656k(rootfs),64k(art)ro,7680k@0x7(firmware)
wndr3700v2_mtdlayout=mtdparts=spi0.0:320k(u-boot)ro,128k(u-boot-env)ro,1024k(kernel),14848k(rootfs),64k(art)ro,15872k@0x7(firmware)
wndr4300_mtdlayout=mtdparts=ar934x-nfc:256k(u-boot)ro,256k(u-boot-env)ro,256k(caldata),512k(pot),2048k(language),512k(config),3072k(traffic_meter),1152k(kernel),24448k(rootfs),25600k@0x6c(firmware),256k(caldata_backup),-(reserved)
@@ -876,6 +877,8 @@
$(eval $(call
SingleProfile,MyLoader,$(fs_64k),WPE72_8M,wpe72,,ttyS0,115200,0x80,8M))
$(eval $(call
SingleProfile,MyLoader,$(fs_64k),WPE72_16M,wpe72,,ttyS0,115200,0x100,16M))
+# This is used with AthGzip profile for now
+$(eval $(call
SingleProfile,AthGzip,$(fs_64k),WNDAP360,wndap360,WNDAP360,ttyS0,9600,$$(wndap360_mtdlayout),1769472,6225920,KRuImage))
$(eval $(call
SingleProfile,Netgear,$(fs_64k),WNDR3700V1,wndr3700,WNDR3700,ttyS0,115200,$$(wndr3700_mtdlayout),3700,WNDR3700,""
NA,))
$(eval $(call
SingleProfile,Netgear,$(fs_64k),WNDR3700V2,wndr3700v2,WNDR3700,ttyS0,115200,$$(wndr3700v2_mtdlayout),3701,WNDR3700v2,"",-H
29763654+16+64))
$(eval $(call
SingleProfile,Netgear,$(fs_64k),WNDR3800,wndr3800,WNDR3700,ttyS0,115200,$$(wndr3700v2_mtdlayout),3701,WNDR3800,"",-H
29763654+16+128))
Index: target/linux/ar71xx/patches-3.8/610-MIPS-ath79-openwrt-machines.patch
===
--- target/linux/ar71xx/patches-3.8/610-MIPS-ath79-openwrt-machines.patch
(revision 36156)
+++ target/linux/ar71xx/patches-3.8/610-MIPS-ath79-openwrt-machines.patch
(working copy)
@@ -1,6 +1,6 @@
--- a/arch/mips/ath79/machtypes.h
+++ b/arch/mips/ath79/machtypes.h
-@@ -16,22 +16,112 @@
+@@ -16,22 +16,113 @@
enum ath79_mach_type {
ATH79_MACH_GENERIC = 0,
@@ -97,6 +97,7 @@
+ ATH79_MACH_WHR_HP_G300N,/* Buffalo WHR-HP-G300N */
+ ATH79_MACH_WHR_HP_GN, /* Buffalo WHR-HP-GN */
+ ATH79_MACH_WLAE_AG300N, /* Buffalo WLAE-AG300N */
++ ATH79_MACH_WNDAP360,/* NETGEAR WNDAP360 */
+ ATH79_MACH_WNDR3700,/* NETGEAR WNDR3700/WNDR3800/WNDRMAC */
+ ATH79_MACH_WNDR4300,/* NETGEAR WNDR4300 */
+ ATH79_MACH_WNR2000, /* NETGEAR WNR2000 */
@@ -216,7 +217,7 @@
config ATH79_MACH_PB44
bool "Atheros PB44 reference board"
select SOC_AR71XX
-@@ -68,6 +148,488 @@ config ATH79_MACH_PB44
+@@ -68,6 +148,498 @@ config ATH79_MACH_PB44
Say 'Y' here if you want your kernel to support the
Atheros PB44 reference board.
@@ -417,6 +418,16 @@
+ select ATH79_DEV_WMAC
+ select ATH79_ROUTERBOOT
+
++config ATH79_MACH_WNDAP360
++ bool "NETGEAR WNDAP360 board support"
++ select SOC_AR71XX
++ select ATH79_DEV_AP9X_PCI if PCI
++ select ATH79_DEV_ETH
++ select ATH79_DEV_GPIO_BUTTONS
++ select ATH79_DEV_LEDS_GPIO
++ select ATH79_DEV_M25P80
++ select ATH79_DEV_USB
++
+config ATH79_MACH_WNDR3700
+ bool "NETGEAR WNDR3700 board support"
+ select SOC_AR71XX
@@ -826,6 +837,7 @@
obj-$(CONFIG_ATH79_MACH_UBNT_XM) += mach-ubnt-xm.o
+obj-$(CONFIG_ATH79_MACH_WHR_HP_G300N) += mach-whr-hp-g300n.o
+obj-$(CONFIG_ATH79_MACH_WLAE_AG300N) += mach-wlae-ag300n.o
++obj-$(CONFIG_ATH79_MACH_WNDAP360) += mach-wndap360.o
+obj-$(CONFIG_ATH79_MACH_WNDR3700) += mach-wndr3700.o
+obj-$(CONFIG_ATH79_MACH_WNDR4300) += mach-wndr4300.o
+obj-$(CONFIG_ATH79_MACH_WNR2000) += mach-wnr2000.o
Index: target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c
===
--- target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (revision 0)
+++ target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (working copy)
@@ -0,0 +1,105 @@
+/*
+ * Netgear WNDAP360 board support (proper leds / button support missing)
+ *
+ * B
Re: [OpenWrt-Devel] [PATCH] [ar71xx] Add support for Netgear WNDAP360
I have prepared newer patch that supports sysupgrade not sure how can I update this? On 04/08/2013 03:19 PM, Jacek Kikiewicz wrote: > Developer's Certificate of Origin 1.1 > > By making a contribution to this project, I certify that: > > (a) The contribution was created in whole or in part by me and I > have the right to submit it under the open source license > indicated in the file; or > > (b) The contribution is based upon previous work that, to the best > of my knowledge, is covered under an appropriate open source > license and I have the right under that license to submit that > work with modifications, whether created in whole or in part > by me, under the same open source license (unless I am > permitted to submit under a different license), as indicated > in the file; or > > (c) The contribution was provided directly to me by some other > person who certified (a), (b) or (c) and I have not modified > it. > > (d) I understand and agree that this project and the contribution > are public and that a record of the contribution (including all > personal information I submit with it, including my sign-off) is > maintained indefinitely and may be redistributed consistent with > this project or the open source license(s) involved. > > Signed-off-by: Jacek Kikiewicz > > --- > > Comments: > Things not working: sysupgrade, WIFI LEDs > System needs to be flashed from uboot. > > > Index: target/linux/ar71xx/base-files/lib/ar71xx.sh > === > --- target/linux/ar71xx/base-files/lib/ar71xx.sh(revision 36156) > +++ target/linux/ar71xx/base-files/lib/ar71xx.sh(working copy) > @@ -447,6 +447,9 @@ > *WPE72) > name="wpe72" > ;; > +*WNDAP360) > +name="wndap360" > +;; > *"WNDR3700/WNDR3800/WNDRMAC") > wndr3700_board_detect "$machine" > ;; > Index: target/linux/ar71xx/base-files/etc/uci-defaults/02_network > === > --- target/linux/ar71xx/base-files/etc/uci-defaults/02_network > (revision 36156) > +++ target/linux/ar71xx/base-files/etc/uci-defaults/02_network > (working copy) > @@ -199,6 +199,7 @@ > tl-wa901nd |\ > tl-wa901nd-v2 |\ > tl-wr703n |\ > +wndap360 |\ > wp543) > ucidef_set_interface_lan "eth0" > ;; > Index: target/linux/ar71xx/base-files/etc/uci-defaults/01_leds > === > --- target/linux/ar71xx/base-files/etc/uci-defaults/01_leds (revision > 36156) > +++ target/linux/ar71xx/base-files/etc/uci-defaults/01_leds (working > copy) > @@ -200,6 +200,10 @@ > ucidef_set_led_wlan "wlan" "WLAN" "wrt160nl:blue:wlan" "phy0tpt" > ;; > > +wndap360) > +ucidef_set_led_power "power" "POWER GREEN" > "wndap360:green:power" "1" > +;; > + > wndr3700) > ucidef_set_led_default "wan" "WAN LED (green)" > "wndr3700:green:wan" "0" > ucidef_set_led_usbdev "usb" "USB" "wndr3700:green:usb" "1-1" > Index: target/linux/ar71xx/base-files/etc/diag.sh > === > --- target/linux/ar71xx/base-files/etc/diag.sh(revision 36156) > +++ target/linux/ar71xx/base-files/etc/diag.sh(working copy) > @@ -158,6 +158,9 @@ > wzr-hp-g300nh2) > status_led="buffalo:red:diag" > ;; > +wndap360) > +status_led="wndap360:green:power" > +;; > wndr3700) > status_led="wndr3700:green:power" > ;; > Index: target/linux/ar71xx/config-3.8 > === > --- target/linux/ar71xx/config-3.8(revision 36156) > +++ target/linux/ar71xx/config-3.8(working copy) > @@ -81,6 +81,7 @@ > CONFIG_ATH79_MACH_UBNT_XM=y > CONFIG_ATH79_MACH_WHR_HP_G300N=y > CONFIG_ATH79_MACH_WLAE_AG300N=y > +CONFIG_ATH79_MACH_WNDAP360=y > CONFIG_ATH79_MACH_WNDR3700=y > CONFIG_ATH79_MACH_WNDR4300=y > CONFIG_ATH79_MACH_WNR2000=y > Index: target/linux/ar71xx/generic/profiles/netgear.mk > === > --- target/linux/ar71xx/generic/profiles/netgear.mk(revision 36156) > +++ target/linux/ar71xx/generic/profiles/netgear.mk(working copy) > @@ -5,6 +5,17 @@ > # See /LI
[OpenWrt-Devel] [PATCH] [ar71xx] Add support for Netgear WNDAP360
Developer's Certificate of Origin 1.1 By making a contribution to this project, I certify that: (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it. (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved. Signed-off-by: Jacek Kikiewicz --- Comments: Things not working: sysupgrade, WIFI LEDs System needs to be flashed from uboot. Index: target/linux/ar71xx/base-files/lib/ar71xx.sh === --- target/linux/ar71xx/base-files/lib/ar71xx.sh(revision 36156) +++ target/linux/ar71xx/base-files/lib/ar71xx.sh(working copy) @@ -447,6 +447,9 @@ *WPE72) name="wpe72" ;; +*WNDAP360) +name="wndap360" +;; *"WNDR3700/WNDR3800/WNDRMAC") wndr3700_board_detect "$machine" ;; Index: target/linux/ar71xx/base-files/etc/uci-defaults/02_network === --- target/linux/ar71xx/base-files/etc/uci-defaults/02_network (revision 36156) +++ target/linux/ar71xx/base-files/etc/uci-defaults/02_network (working copy) @@ -199,6 +199,7 @@ tl-wa901nd |\ tl-wa901nd-v2 |\ tl-wr703n |\ +wndap360 |\ wp543) ucidef_set_interface_lan "eth0" ;; Index: target/linux/ar71xx/base-files/etc/uci-defaults/01_leds === --- target/linux/ar71xx/base-files/etc/uci-defaults/01_leds (revision 36156) +++ target/linux/ar71xx/base-files/etc/uci-defaults/01_leds (working copy) @@ -200,6 +200,10 @@ ucidef_set_led_wlan "wlan" "WLAN" "wrt160nl:blue:wlan" "phy0tpt" ;; +wndap360) +ucidef_set_led_power "power" "POWER GREEN" "wndap360:green:power" "1" +;; + wndr3700) ucidef_set_led_default "wan" "WAN LED (green)" "wndr3700:green:wan" "0" ucidef_set_led_usbdev "usb" "USB" "wndr3700:green:usb" "1-1" Index: target/linux/ar71xx/base-files/etc/diag.sh === --- target/linux/ar71xx/base-files/etc/diag.sh(revision 36156) +++ target/linux/ar71xx/base-files/etc/diag.sh(working copy) @@ -158,6 +158,9 @@ wzr-hp-g300nh2) status_led="buffalo:red:diag" ;; +wndap360) +status_led="wndap360:green:power" +;; wndr3700) status_led="wndr3700:green:power" ;; Index: target/linux/ar71xx/config-3.8 === --- target/linux/ar71xx/config-3.8(revision 36156) +++ target/linux/ar71xx/config-3.8(working copy) @@ -81,6 +81,7 @@ CONFIG_ATH79_MACH_UBNT_XM=y CONFIG_ATH79_MACH_WHR_HP_G300N=y CONFIG_ATH79_MACH_WLAE_AG300N=y +CONFIG_ATH79_MACH_WNDAP360=y CONFIG_ATH79_MACH_WNDR3700=y CONFIG_ATH79_MACH_WNDR4300=y CONFIG_ATH79_MACH_WNR2000=y Index: target/linux/ar71xx/generic/profiles/netgear.mk === --- target/linux/ar71xx/generic/profiles/netgear.mk(revision 36156) +++ target/linux/ar71xx/generic/profiles/netgear.mk(working copy) @@ -5,6 +5,17 @@ # See /LICENSE for more information. # +define Profile/WNDAP360 +NAME:=NETGEAR WNDAP360 +PACKAGES:= +endef + +define Profile/WNDAP360/Description +Package set optimized for the NETGEAR WNDAP360 +endef + +$(eval $(call Profile,WNDAP360)) + define Profile/WNDR3700 NAME:=NETGEAR WNDR3700/WNDR3800/WNDRMAC PACKAGES:=kmod-usb-core kmod-usb-ohci kmod-usb2 kmod-ledtrig-usbdev kmod-leds-wndr3700-usb Index: target/linux/ar71xx/image/Makefile === --- target/linux/ar71xx/image/Makefile(revision 36156) +++ target/linux/ar71xx/image/Makefile(working copy) @@ -185,6 +185,7 @@ uap_pro_mtdlayou
