Re: [OpenWrt-Devel] dslite interface not getting active
Hello Hans, I finally commited a netifd update yesterday which should take care of that. Regards, Steven ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenWRT on Ubicom Chipsets
I've now based off of trunk and have integrated some actual hardware specific configs/patches, I've made progress on a number of other needed changes but am stuck on one particular error : ERROR: Missing site config for target ubicom32-openwrt-linux-uclibc ! The missing file will cause configure scripts to fail during compilation. Please provide a /home/james/openwrt/include/site/ubicom32-openwrt-linux-uclibc file and restart the build. make[2]: *** [prereq] Error 1 make[1]: *** [prereq] Error 2 make: *** [depends] Error 2 I have no idea what configure scripts actually need this and how to fix it. It does not exist in the oem ubicom buildroot directory as far as I can tell so I think I just need to kill off whatever is asking for the file since it is probably not needed there. On Fri, Oct 18, 2013 at 6:15 AM, James Hilliard james.hillia...@gmail.comwrote: Do I need to submit everything all at once or can I add things slowly so I can confirm all components are in compliance with openwrt formatting etc? The first thing to do would be to revert the removal of the ubicom32 platform here https://dev.openwrt.org/wiki/ubicom32, from there I can work on integrating the device specific patches. Should I submit a patch for that removal? On Thu, Oct 17, 2013 at 6:50 AM, James Hilliard james.hillia...@gmail.com wrote: So, I think i more or less got the boot processes down, however I don't have hardware with me right now. Boot goes from ultraubootlinux more or less. From the looks of it getting a console on uboot should be fairly straight forward. I'm going to attempt to compile an oem build with the uboot console enabled that way we can debug and flash over Ethernet instead of serial. Msg me on gtalk and ill send you some builds(this email). On Thu, Oct 17, 2013 at 2:04 AM, michal-osowie...@o2.pl michal-osowie...@o2.pl wrote: Hi James AFAIR dir-657 soucecode has openwrt's port which compiles but has no ethernet switch enabled/ported. I's hard to test develop anything without flash programmer so i dropped testing. It would be nice if you could add this model to your work Thanks, Michal Dnia 16 października 2013 20:53 James Hilliard james.hillia...@gmail.com napisał(a): I think i#39;ll attempt to support this and get some vendor/deviceconfigs integrated, can the changes that removed arch support bereverted easily in trunk? I#39;ve been working off of 12.09 here https://github.com/Lightsword1942/openwrtubicom and manually merging some things let me know if you have anysuggestions. I#39;m not sure what this is using for include/siteand that#39;s what I#39;m currently hung up on. On Mon, Sep 16, 2013 at 6:11 AM, Florian Fainelli f.faine...@gmail.com wrote: Hello, 2013/9/16 James Hilliard james.hillia...@gmail.com: Anyone interested in OpenWRT on Ubicom? They used OpenWRTinternally so there is already source ready(may be a little outdatedthough). Also have some router specific sources of both it and stock. OpenWrt did support the ubicom32 architecture for awhile, but since this is a very quirky architecture and nobody could step up as a maintainer, it got removed. Unless you are willing to support that architecture, I see no point in supporting it since it reallyrequired a lot of quirks (special hypervisor software,bootloader and !MMU). -- Florian ___ 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
Re: [OpenWrt-Devel] OpenWRT on Ubicom Chipsets
On Sat, Oct 19, 2013 at 11:04 AM, James Hilliard james.hillia...@gmail.com wrote: I've now based off of trunk and have integrated some actual hardware specific configs/patches, I've made progress on a number of other needed changes but am stuck on one particular error : ERROR: Missing site config for target ubicom32-openwrt-linux-uclibc ! The missing file will cause configure scripts to fail during compilation. Please provide a /home/james/openwrt/include/site/ubicom32-openwrt-linux-uclibc file and restart the build. make[2]: *** [prereq] Error 1 make[1]: *** [prereq] Error 2 make: *** [depends] Error 2 I have no idea what configure scripts actually need this and how to fix it. It does not exist in the oem ubicom buildroot directory as far as I can tell so I think I just need to kill off whatever is asking for the file since it is probably not needed there. Have a look at the other files in this directory. They provide the defaults for many standard configure script tests (ac_cv_*). Several of these are usually only found out by running a test program (after compiling it), which fails badly when cross compiling, thus breaking the configure step and therefore compilation. So in conclusion you will need it, and you need to provide the appropriate defaults in it. Regards Jonas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenWRT on Ubicom Chipsets
Yeah, I looked in the directory to try and find what the missing file should like like, I then searched the oem firmware and oem internal openwrt build and I could not find the missing variables anywhere, there's probably a number of patches that I still need to integrate still from those builds, maybe it is generated on the fly by some package. I've rolled back the Ubicom32 removal from a year ago but I think it was missing a lot of patches and was more incomplete than I originally thought. Should I start submitting patches as soon as I can get it to stop breaking the build system? I mirrored the latest oem and internal sources I have here https://github.com/Lightsword1942/ubicom32 although I have older ones with more device configs, that one I mirrored should have support for the dir-655 B variant. I have most of the other device profile configs as well so that shouldn't be too big an issue. Ill look into this more tomorrow and start integrating the patches from the internal openwrt sources. On Sat, Oct 19, 2013 at 5:36 AM, Jonas Gorski j...@openwrt.org wrote: On Sat, Oct 19, 2013 at 11:04 AM, James Hilliard james.hillia...@gmail.com wrote: I've now based off of trunk and have integrated some actual hardware specific configs/patches, I've made progress on a number of other needed changes but am stuck on one particular error : ERROR: Missing site config for target ubicom32-openwrt-linux-uclibc ! The missing file will cause configure scripts to fail during compilation. Please provide a /home/james/openwrt/include/site/ubicom32-openwrt-linux-uclibc file and restart the build. make[2]: *** [prereq] Error 1 make[1]: *** [prereq] Error 2 make: *** [depends] Error 2 I have no idea what configure scripts actually need this and how to fix it. It does not exist in the oem ubicom buildroot directory as far as I can tell so I think I just need to kill off whatever is asking for the file since it is probably not needed there. Have a look at the other files in this directory. They provide the defaults for many standard configure script tests (ac_cv_*). Several of these are usually only found out by running a test program (after compiling it), which fails badly when cross compiling, thus breaking the configure step and therefore compilation. So in conclusion you will need it, and you need to provide the appropriate defaults in it. Regards Jonas ___ 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] OpenWRT on Ubicom Chipsets
Careful, the ubicom32 target that was removed predates the ip8k chipset; it was removed both due to lack of maintainer and because it required a strict nommu userspace -- no calls to fork() and avoid mmap() or risk fragmenting available memory. The ip8k was the first Ubicom chipset to feature an mmu; the ip5k and ip7k had a flat memory model and had to run a nommu version of Linux with a patched userspace -- even after the mmu was introduced there were still traces of nommu due to the shared codebase. The latest version of the Ubicom distribution can be found on Code Aurora, it was uploaded immediately prior to Qualcomm's acquisition of Ubicom at which point development ceased. It appears you've mirrored this right down to the name of the commiter. While I would like to see ip8k merged, I think that running OpenWrt on the earlier chipsets is a mistake, or at the very least a platform waiting to be exploited due to insufficient memory barriers. James Hilliard james.hillia...@gmail.com wrote: ___ 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] OpenWRT on Ubicom Chipsets
You're close; ultra is the name given to the proprietary code that runs on all the threads not running linux. The ubicom chipsets are hardware multithreaded with 8-12 threads -- SMT, think of it as SMP but context switching instead of concurrent. Ultra performs the board initialization and then spawns U-Boot on another thread, and continues to run in parallel with Linux. The U-Boot console should be enabled but it expects to talk to a programming dongle and not an actual serial port. James Hilliard james.hillia...@gmail.com wrote: ___ 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] OpenWRT on Ubicom Chipsets
Hello, 2013/10/19 James Hilliard james.hillia...@gmail.com: I've now based off of trunk and have integrated some actual hardware specific configs/patches, I've made progress on a number of other needed changes but am stuck on one particular error : ERROR: Missing site config for target ubicom32-openwrt-linux-uclibc ! The missing file will cause configure scripts to fail during compilation. Please provide a /home/james/openwrt/include/site/ubicom32-openwrt-linux-uclibc file and restart the build. make[2]: *** [prereq] Error 1 make[1]: *** [prereq] Error 2 make: *** [depends] Error 2 I have no idea what configure scripts actually need this and how to fix it. It does not exist in the oem ubicom buildroot directory as far as I can tell so I think I just need to kill off whatever is asking for the file since it is probably not needed there. You should have a site file in include/site/ubicom32-linux-uclibc similar to what already exists for MIPS, ARM etc... This should be part of the reverted commit and you should be able to dig it. On Fri, Oct 18, 2013 at 6:15 AM, James Hilliard james.hillia...@gmail.com wrote: Do I need to submit everything all at once or can I add things slowly so I can confirm all components are in compliance with openwrt formatting etc? The first thing to do would be to revert the removal of the ubicom32 platform here https://dev.openwrt.org/wiki/ubicom32, from there I can work on integrating the device specific patches. Should I submit a patch for that removal? On Thu, Oct 17, 2013 at 6:50 AM, James Hilliard james.hillia...@gmail.com wrote: So, I think i more or less got the boot processes down, however I don't have hardware with me right now. Boot goes from ultraubootlinux more or less. From the looks of it getting a console on uboot should be fairly straight forward. I'm going to attempt to compile an oem build with the uboot console enabled that way we can debug and flash over Ethernet instead of serial. Msg me on gtalk and ill send you some builds(this email). On Thu, Oct 17, 2013 at 2:04 AM, michal-osowie...@o2.pl michal-osowie...@o2.pl wrote: Hi James AFAIR dir-657 soucecode has openwrt's port which compiles but has no ethernet switch enabled/ported. I's hard to test develop anything without flash programmer so i dropped testing. It would be nice if you could add this model to your work Thanks, Michal Dnia 16 października 2013 20:53 James Hilliard james.hillia...@gmail.com napisał(a): I think i#39;ll attempt to support this and get some vendor/deviceconfigs integrated, can the changes that removed arch support bereverted easily in trunk? I#39;ve been working off of 12.09 here https://github.com/Lightsword1942/openwrtubicom and manually merging some things let me know if you have anysuggestions. I#39;m not sure what this is using for include/siteand that#39;s what I#39;m currently hung up on. On Mon, Sep 16, 2013 at 6:11 AM, Florian Fainelli f.faine...@gmail.com wrote: Hello, 2013/9/16 James Hilliard james.hillia...@gmail.com: Anyone interested in OpenWRT on Ubicom? They used OpenWRTinternally so there is already source ready(may be a little outdatedthough). Also have some router specific sources of both it and stock. OpenWrt did support the ubicom32 architecture for awhile, but since this is a very quirky architecture and nobody could step up as a maintainer, it got removed. Unless you are willing to support that architecture, I see no point in supporting it since it reallyrequired a lot of quirks (special hypervisor software,bootloader and !MMU). -- Florian ___ 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 -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Problem of connectivity with adhoc using wpa
I have recently experienced a problem when using wpa encryption on adhoc interfaces. Description: When both routers power up at the same time everything works without problems and bother can see and communicate with each other on layer 2 (batman-adv) and layer 3; however if one reboots or restarts the wireless interface; communication is no longer possible and both routers stop seeing each other in both layers. Rebooting both at the same time gets them to work again with each other. Someone mentioned that this might be caused due to the latest hostpad not being pulled. Any feedback is welcome. On both routers: option encryption 'psk2' wpad 20130405-1 DISTRIB_REVISION=r38401 DISTRIB_CODENAME=attitude_adjustment DISTRIB_TARGET=ar71xx/generic -- Site: http://wirelesspt.net Mesh: http://tinyurl.com/wirelesspt Admin: http://wirelesspt.net/wiki/Cmsv Twitter: http://twitter.com/wirelesspt Youtube: https://youtube.com/wirelesspt Suporte técnico via sms: 91 19 11 798 Donativos/Paypal: http://tinyurl.com/doar-verba Chave publica PGP/SSH: http://wirelesspt.net/arquivos/pk Licença deste conteúdo: https://creativecommons.org/licenses/by-nc-sa/3.0/pt/ Email assinado digitalmente pelo emissor assegurando autenticidade ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Problem of connectivity with adhoc using wpa
On 2013-10-19 7:30 PM, cmsv wrote: I have recently experienced a problem when using wpa encryption on adhoc interfaces. Description: When both routers power up at the same time everything works without problems and bother can see and communicate with each other on layer 2 (batman-adv) and layer 3; however if one reboots or restarts the wireless interface; communication is no longer possible and both routers stop seeing each other in both layers. Rebooting both at the same time gets them to work again with each other. Someone mentioned that this might be caused due to the latest hostpad not being pulled. Any feedback is welcome. On both routers: option encryption 'psk2' wpad 20130405-1 DISTRIB_REVISION=r38401 DISTRIB_CODENAME=attitude_adjustment DISTRIB_TARGET=ar71xx/generic Here's a backport of mac80211+hostapd: http://nbd.name/gitweb.cgi?p=aa-mac80211.git;a=summary git://nbd.name/aa-mac80211.git Please try integrating that into your build tree and see if it fixes the issue. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] openwrt-devel Digest, Vol 94, Issue 55
on uboot should be fairly straight forward. I'm going to attempt to compile an oem build with the uboot console enabled that way we can debug and flash over Ethernet instead of serial. Msg me on gtalk and ill send you some builds(this email). On Thu, Oct 17, 2013 at 2:04 AM, michal-osowie...@o2.pl michal-osowie...@o2.pl wrote: Hi James AFAIR dir-657 soucecode has openwrt's port which compiles but has no ethernet switch enabled/ported. I's hard to test develop anything without flash programmer so i dropped testing. It would be nice if you could add this model to your work Thanks, Michal Dnia 16 pa?dziernika 2013 20:53 James Hilliard james.hillia...@gmail.com napisa?(a): I think i#39;ll attempt to support this and get some vendor/deviceconfigs integrated, can the changes that removed arch support bereverted easily in trunk? I#39;ve been working off of 12.09 here https://github.com/Lightsword1942/openwrtubicom and manually merging some things let me know if you have anysuggestions. I#39;m not sure what this is using for include/siteand that#39;s what I#39;m currently hung up on. On Mon, Sep 16, 2013 at 6:11 AM, Florian Fainelli f.faine...@gmail.com wrote: Hello, 2013/9/16 James Hilliard james.hillia...@gmail.com: Anyone interested in OpenWRT on Ubicom? They used OpenWRTinternally so there is already source ready(may be a little outdatedthough). Also have some router specific sources of both it and stock. OpenWrt did support the ubicom32 architecture for awhile, but since this is a very quirky architecture and nobody could step up as a maintainer, it got removed. Unless you are willing to support that architecture, I see no point in supporting it since it reallyrequired a lot of quirks (special hypervisor software,bootloader and !MMU). -- Florian ___ 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 -- next part -- An HTML attachment was scrubbed... URL: http://lists.openwrt.org/pipermail/openwrt-devel/attachments/20131019/f2814bed/attachment-0001.html -- Subject: Digest Footer ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- End of openwrt-devel Digest, Vol 94, Issue 55 * ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
