Hi Saverio, Thank you for commenting on my question. My device is Ubiquiti Bullet5. It's a 802.11 modem with 4 MB flash and AR2313 SoC. But, it is the same config file as I was using before. Although, I did "make dirclean" and did svn update. So, can you suggest me some changes that I can do to my build to make the image's size less than 4 MB.
Regards, Siva. On Fri, Oct 26, 2012 at 11:24 AM, <openwrt-devel-requ...@lists.openwrt.org>wrote: > Send openwrt-devel mailing list submissions to > openwrt-devel@lists.openwrt.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > or, via email, send a message with subject or body 'help' to > openwrt-devel-requ...@lists.openwrt.org > > You can reach the person managing the list at > openwrt-devel-ow...@lists.openwrt.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of openwrt-devel digest..." > > > Today's Topics: > > 1. Re: [PATCH] Add support for TP-Link WA7510N (Jonathan Bither) > 2. Re: [PATCH] Add support for TP-Link WA7510N (Stefan Helmert) > 3. Re: openwrt-atheros-ubnt5-squashfs.bin not generated in > openwrt trunk (Saverio Proto) > 4. Re: [PATCH] Add support for TP-Link WA7510N (Jonathan Bither) > 5. Re: Buffalo WZR-HP-AG300H vlan woes (Patrick van Staveren) > 6. Re: [PATCH] Add support for TP-Link WA7510N (Stefan Helmert) > 7. Re: [PATCH] Add support for TP-Link WA7510N (Jonathan Bither) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 26 Oct 2012 09:40:52 -0400 > From: Jonathan Bither <jonbit...@gmail.com> > To: OpenWrt Development List <openwrt-devel@lists.openwrt.org> > Subject: Re: [OpenWrt-Devel] [PATCH] Add support for TP-Link WA7510N > Message-ID: <508a92e4.9060...@gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 10/25/2012 09:31 PM, Stefan Helmert wrote: > > From Stefan Helmert <helst_lis...@aol.de> > > > > It is mostly the same as wr841nd. WLAN and LAN are working. LAN-Led > > ist working. WLAN signal strength Leds are not working yet. > I imagine that you can actually get the signal leds operating correctly > if you add the configuration for the package rssileds. When I get time I > wanted to do the same for various ubiquiti devices. > > > > http://wiki.openwrt.org/toh/tp-link/tl-wa7510n?s[]=wa7510n > > > > Signed-off-by: Stefan Helmert <helst_lis...@aol.de> > > > > > > ------------------------------ > > Message: 2 > Date: Fri, 26 Oct 2012 15:49:32 +0200 > From: Stefan Helmert <helst_lis...@aol.de> > To: OpenWrt Development List <openwrt-devel@lists.openwrt.org> > Subject: Re: [OpenWrt-Devel] [PATCH] Add support for TP-Link WA7510N > Message-ID: <508a94ec.4030...@aol.de> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > I hope this will work. You should know, the leds on ubiquity devices are > connected to the ar7240 main-controller. On TL-WA7510N they are > connected to ar9280 wlan-device as gpio-device. > > Please can you tell me more about rssileds. > > Am 26.10.2012 15:40, schrieb Jonathan Bither: > > I imagine that you can actually get the signal leds operating > > correctly if you add the configuration for the package rssileds. When > > I get time I wanted to do the same for various ubiquiti devices. > > > > ------------------------------ > > Message: 3 > Date: Fri, 26 Oct 2012 15:50:55 +0200 > From: Saverio Proto <ziopr...@gmail.com> > To: OpenWrt Development List <openwrt-devel@lists.openwrt.org> > Subject: Re: [OpenWrt-Devel] openwrt-atheros-ubnt5-squashfs.bin not > generated in openwrt trunk > Message-ID: > <CAPmmg8vXdbFQxfaUFAzcCmQ55Ur65GqwG7=y= > v9axzw_u4o...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > The image that is not generated is for a device with 4Mb flash ? If > your build makes a larger image you will find only 8Mb images > generated but not the smaller ones. > > I hope this help. > > best regards > > Saverio Proto > > > 2012/10/25 Sivateja Patibandla <patibandl...@vcu.edu>: > > Hey guys, > > > > I've updated my openWRT trunk build environment to the latest release > > yesterday by "make dirclean and svn update". Now I configure and compile > the > > kernel as before. But now the binary file for my Atheros based Ubiquiti > > device (openwrt-atheros-ubnt5-squashfs.bin) is not being generated. > Although > > I've other files like openwrt-atheros-root.squashfs in bin directory > being > > generated. Can you guys tell me if I'm missing something? > > > > Regards, > > > > Siva. > > > > _______________________________________________ > > openwrt-devel mailing list > > openwrt-devel@lists.openwrt.org > > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > > > > ------------------------------ > > Message: 4 > Date: Fri, 26 Oct 2012 10:06:09 -0400 > From: Jonathan Bither <jonbit...@gmail.com> > To: openwrt-devel@lists.openwrt.org > Subject: Re: [OpenWrt-Devel] [PATCH] Add support for TP-Link WA7510N > Message-ID: <508a98d1.2060...@gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 10/26/2012 09:49 AM, Stefan Helmert wrote: > > I hope this will work. You should know, the leds on ubiquity devices > > are connected to the ar7240 main-controller. On TL-WA7510N they are > > connected to ar9280 wlan-device as gpio-device. > I imagine that the leds are wired directly to the ar7240 by way of GPIO > and can be controlled as such. > > > > Please can you tell me more about rssileds. > Daniel Golle introduced a daemon that polls the wireless driver's stats > and can adjust external leds to represent their quality. Here's where > it's introduced and the commit log explains it in greater detail. > > https://dev.openwrt.org/browser/trunk/package/rssileds/src/rssileds.c?rev=33163 > > > > Am 26.10.2012 15:40, schrieb Jonathan Bither: > >> I imagine that you can actually get the signal leds operating > >> correctly if you add the configuration for the package rssileds. When > >> I get time I wanted to do the same for various ubiquiti devices. > > > > _______________________________________________ > > openwrt-devel mailing list > > openwrt-devel@lists.openwrt.org > > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > > > ------------------------------ > > Message: 5 > Date: Fri, 26 Oct 2012 22:28:32 +0800 > From: Patrick van Staveren <tr...@vanstaveren.us> > To: OpenWrt Development List <openwrt-devel@lists.openwrt.org> > Subject: Re: [OpenWrt-Devel] Buffalo WZR-HP-AG300H vlan woes > Message-ID: <ab70266e-846f-40f6-8daa-fe6ec1f79...@vanstaveren.us> > Content-Type: text/plain; charset="us-ascii" > > Replying to my own email. I love it when I can solve my own issue. > > There default configuration for this router (and about 20 others) does not > lend itself to multiple VLANs - you have to modify the bridge interface > first. Really simple problem in hindsight. > > Submitted a ticket with a patch that should work: > https://dev.openwrt.org/ticket/12377 > Thanks to mperez on the forums who first came across this: > https://forum.openwrt.org/viewtopic.php?pid=155341#p155341 > > Cheers, > Patrick > > On Oct 22, 2012, at 23:44, Patrick van Staveren wrote: > > > Hello, > > > > Has anyone used multiple VLANs on this device? > > > > I've worked on two other similar Buffalo routers (G300NH2, G450H) which > both have the same AR8316 switch in them, and I've used standard UCI > configs to create a separate VLAN. > > With the AG300H the default switch_vlan config worries me that port 0 > (the CPU) is set to untagged which I've never seen on these devices before. > Of course if I want a second VLAN, I have to set the CPU port to tagged > for both of them. Once I set the CPU port 0 to tagged (even without > creating a second VLAN) the CPU stops receiving packets. The switch is > still operational - I tested it by creating a second VLAN on two ports to > see if traffic passes through, and it does. But it does not reach the CPU. > > > > With this device, it can be tested rather easily because the WAN/uplink > port is a separate physical interface eth1. > > > > Looking in target/linux/ar71xx/base-files/etc/uci-defaults/network I see > that a lot of switches use this config where the CPU port is not tagged by > default. Am I missing something obvious? Perhaps there's some kernel code > that needs to be patched for this device to expect tagged frames to the CPU? > > > > For reference, the stock config is: > > config switch_vlan > > option device 'eth0' > > option vlan '1' > > option ports '0 1 2 3 4' > > > > To make the switch inaccessible, just start tagging on port 0: > > config switch_vlan > > option device 'eth0' > > option vlan '1' > > option ports '0t 1 2 3 4' > > > > Or the configuration I was hoping to achieve: > > config switch_vlan > > option device 'eth0' > > option vlan '1' > > option vid '1' > > option ports '0t 1 2 3 4' > > config switch_vlan > > option device 'eth0' > > option vlan '2' > > option vid '2' > > option ports '0t 1t' > > > > One final note - clearly someone else noticed this, as in the case where > the default network config was added, the submitter's patch was modified to > use untagged on port 0. See: https://dev.openwrt.org/ticket/9607 > > > > Thanks in advance! > > > > Patrick van Staveren > > > > _______________________________________________ > > openwrt-devel mailing list > > openwrt-devel@lists.openwrt.org > > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.openwrt.org/pipermail/openwrt-devel/attachments/20121026/93a6ae48/attachment-0001.html > > > > ------------------------------ > > Message: 6 > Date: Fri, 26 Oct 2012 16:44:29 +0200 > From: Stefan Helmert <helst_lis...@aol.de> > To: OpenWrt Development List <openwrt-devel@lists.openwrt.org> > Subject: Re: [OpenWrt-Devel] [PATCH] Add support for TP-Link WA7510N > Message-ID: <508aa1cd.6060...@aol.de> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > The leds are connected to the ar9280 on WA7510N. The wlan-chip does also > have gpio-support. I checked it out. The only way to control the leds is > to use the ath9k gpio functionality. I hope rssileds will support this > directly. I will read about it. The only led which is connected to the > ar7240 is the lan-led. > > Am 26.10.2012 16:06, schrieb Jonathan Bither: > > On 10/26/2012 09:49 AM, Stefan Helmert wrote: > >> I hope this will work. You should know, the leds on ubiquity devices > >> are connected to the ar7240 main-controller. On TL-WA7510N they are > >> connected to ar9280 wlan-device as gpio-device. > > I imagine that the leds are wired directly to the ar7240 by way of > > GPIO and can be controlled as such. > >> > >> Please can you tell me more about rssileds. > > Daniel Golle introduced a daemon that polls the wireless driver's > > stats and can adjust external leds to represent their quality. Here's > > where it's introduced and the commit log explains it in greater detail. > > > https://dev.openwrt.org/browser/trunk/package/rssileds/src/rssileds.c?rev=33163 > > > >> > >> Am 26.10.2012 15:40, schrieb Jonathan Bither: > >>> I imagine that you can actually get the signal leds operating > >>> correctly if you add the configuration for the package rssileds. > >>> When I get time I wanted to do the same for various ubiquiti devices. > >> > >> _______________________________________________ > >> 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 > > > > ------------------------------ > > Message: 7 > Date: Fri, 26 Oct 2012 11:24:48 -0400 > From: Jonathan Bither <jonbit...@gmail.com> > To: OpenWrt Development List <openwrt-devel@lists.openwrt.org> > Subject: Re: [OpenWrt-Devel] [PATCH] Add support for TP-Link WA7510N > Message-ID: <508aab40.2060...@gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 10/26/2012 10:44 AM, Stefan Helmert wrote: > > The leds are connected to the ar9280 on WA7510N. The wlan-chip does > > also have gpio-support. I checked it out. The only way to control the > > leds is to use the ath9k gpio functionality. I hope rssileds will > > support this directly. I will read about it. The only led which is > > connected to the ar7240 is the lan-led. > The source that you linked to is rather old. I just checked out > wireless-testing again and it looks as though the gpio initialization > only will poll for 1 led. May I ask how you have verified that the led > is wired to the ar9280? Also do you have the boot log of OpenWRT loading > on this device? > > > > Am 26.10.2012 16:06, schrieb Jonathan Bither: > >> On 10/26/2012 09:49 AM, Stefan Helmert wrote: > >>> I hope this will work. You should know, the leds on ubiquity devices > >>> are connected to the ar7240 main-controller. On TL-WA7510N they are > >>> connected to ar9280 wlan-device as gpio-device. > >> I imagine that the leds are wired directly to the ar7240 by way of > >> GPIO and can be controlled as such. > >>> > >>> Please can you tell me more about rssileds. > >> Daniel Golle introduced a daemon that polls the wireless driver's > >> stats and can adjust external leds to represent their quality. Here's > >> where it's introduced and the commit log explains it in greater detail. > >> > https://dev.openwrt.org/browser/trunk/package/rssileds/src/rssileds.c?rev=33163 > >> > >>> > >>> Am 26.10.2012 15:40, schrieb Jonathan Bither: > >>>> I imagine that you can actually get the signal leds operating > >>>> correctly if you add the configuration for the package rssileds. > >>>> When I get time I wanted to do the same for various ubiquiti devices. > >>> > >>> _______________________________________________ > >>> 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 mailing list > > openwrt-devel@lists.openwrt.org > > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > > ------------------------------ > > End of openwrt-devel Digest, Vol 82, Issue 71 > ********************************************* >
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
