Re: [OpenWrt-Devel] Chaos Calmer 15.05-rc2
Can i get the exact commit hash and description of the 15.05-rc2 please ? Thank you very much in advance. Kind Regards, Arturo ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Chaos Calmer 15.05-rc2
Thank you Rafał ! ! ! Regards, Arturo ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Chaos Calmer 15.05-rc3
which is the exact git hash of the RC3 release ? Thank you in advance Kind Regards, Arturo ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Chaos Calmer 15.05-rc3
please give me the exact *git commit HASH* of 15.05-rc3. I need to make my own snapshot based on that. Kind Regards, Arturo ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Chaos Calmer 15.05-rc3
after running the git 'reset' command : /$ git reset --hard 171f0fd10830acd3259f7c229f1b65b95595f388/ in the trunk directory returns me : / //fatal: Could not parse object '171f0fd10830acd3259f7c229f1b65b95595f388' /is by any chance the right commit the one updating openssl to v1.0.2.d ? Kind Regards ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] fix for ticket #20087
Hello folks, has anyone find a quick solution for the ticket #20087 ? https://dev.openwrt.org/ticket/20087 I'm still experiencing this issue when building a system with uClibc. In my case, the broken package is *glib2* as also reported in the tickets itself. I could use also a simple patch to fix my building issue. Regards, Arturo ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Chaos Calmer 15.05
First of all, congratulations to all of you for the great effort. I just want to post a simple questionI have noticed that the the LUCI control panel still returns a null MAC Address for both the wired and wireless network cards. If I remember well, the developers are well aware of this issue which is related to UBUS and LuCi itself. Any chance to get this bug solved in one of the next maintenance commits ? Regards, Arturo 2015-09-11 18:19 GMT+02:00 elektra : > Congratiulations and thank you all very much! > > You rock! > > Cheers, > Elektra > ___ > 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] embed TEXINFO in the latest trunk as build tool
Hello guys, if was wondering if you have ever considered to embed the *TEXINFO* package as one of the *HOST* build tools. I have bumped a couple of times, when compiling, into some issue related to its binaries especially when the standard build tools launch the docs generation. would you consider to insert it in as a next future trunk commit ? Please think about it Best, Arturo ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] XORG and PHONE feeds are down
Hello forks, I have noticed that the feeds in the object are still broken (it has been a couple of days now since then). Any chance to get alternative mirrors for PHONE and XORG packages ? Best, Arturo ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] a little of confusion about the official trunk....
Hello folks, I have noticed that now there are currently two openwrt trunk repos : 1. https://github.com/openwrt/openwrt 2. https://git.openwrt.org/?p=openwrt.git;a=summary is the official development continuing officially on the first one since the latest commit on the second one (private git hosted repo) goes back to the latest June 30th ? I also tried to pull the code of the repo 1 on repo 2 to update the code but I got a git mismatch, so I suppose the two repos does not share the same code ? Could give me more info about this ? thanks in advance. Best, Arturo ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] building a mips/uclibc toolchain relying on gcc 4.9
Hello folks, I need to build a mips-uclicbx-ar71xx toolchain based on the gcc v4.9 series for purposes of my own. I reverted the trunk to this commit with : /commit d39916a2a31fa41c5e2dc5a1941d3b5337ad9dd4// //Author: nbd // //Date: Sun Sep 6 09:57:02 2015 +// // //uboot-ar71xx: fix gcc 5.2 compile errors// //Signed-off-by: Felix Fietkau // //git-svn-id: svn://svn.openwrt.org/openwrt/trunk@46797 3c298f89-4303-0410-b956-a3cf2f4a3e73/ which is the latest one, I think, allowing the selection of gcc v4.9 from the toolchain advanced options. Altough I run : / //$ make distclean V=99/ before launching the "make menuconfig" command, I am still not able to select the gcc v4.9 to build my toolchain. I have double-checked and the patches and the configuration option files residing in : /$(ROOT)/toolchain/gcc// / seems to be ok. Please give me some pointers about it. Kind Regads, Arturo ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] meetup for beer on Tuesday 11 Oct, Berlin
It is a good idea! should we just show up there or confirm our presence so you have to reserve a booth/table ? Best, Arturo ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] meetup for beer on Tuesday 11 Oct, Berlin
thank you Alexander ! Looking forward to get to know all of you ! Best, Arturo 2016-10-06 23:22 GMT+02:00 Alexander Couzens : > On Thu, 06 Oct 2016 20:30:24 +0200 > Arturo Rinaldi wrote: > > > It is a good idea! should we just show up there or confirm our > > presence so you have to reserve a booth/table ? > no, just show up. if you can not find us, ask where we are at the bar, > because that space station is a big place with lot's of rabbit holes to > hide. > > best, > lynxis > -- > Alexander Couzens > > mail: lyn...@fe80.eu > jabber: lyn...@fe80.eu > mobile: +4915123277221 > gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604 > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [LEDE-DEV] [OpenWrt] Project proposal: The GNUnet of autonomous Things
Hello folks, as Kathy mentioned as first answer to Daniel, a proper setup running GNUnet on our boards could give us a boost in the IoT world. During the last years we have developed a new approach to the arduino "bridge" interaction with CIAO : http://www.arduino.org/learning/tutorials/advanced-guides/ciao this is of course requires the use of Python as high level language since it is designed around it but transparent to any kind of connectors. If I understand well from this first email exchange, since *ubus* will be the running engine of the new it is a completely native approach being it an underlying running service of OpenWRT. Am I wrong or didn't John show something similar that night at C-base in Berlin as first attempt of creating a sort of new approach to the bridge itself ? This leads me to think about the possibility to use this solution in combination with *lininoIO*, our new approach for exposing the MCU gpio(s) as filesystem devices and using them to interact with sensors, actuators and so on (it was one of the topics of my talk in Berlin). Would this be a reasonable approach for you ? Please let us know what you think about it and in case we'll discuss it in the scheduled call. Best Regards Arturo 2016-12-01 16:51 GMT+01:00 Felix Fietkau : > On 2016-12-01 16:38, Daniel Golle wrote: > > Hi Felix, > > > > On Thu, Dec 01, 2016 at 04:12:38PM +0100, Felix Fietkau wrote: > >> On 2016-12-01 16:05, Daniel Golle wrote: > >> > I was following your posts and do believe there is quite some overlap. > >> > It would thus be feasible to generalize the common parts (ubus call > >> > proxy, ubus service proxy, ubus remote monitor) by agreeing on a > shared > >> > interface the actual implementations shall use. In that way, people > >> > can choose whether they want WebSockets, TR-069 or a suitable P2P > >> > framework depending on their specific needs. > >> > Has anything of your current approach at IOPSYS been made available > >> > publicly (eg. on github?) > >> > > >> > From what I can tell there is also some overlap with Felix' proposed > >> > System Configuration Abstraction Layer, just that my envisioned use > >> > exceeds system configuration as it includes sensors, events and actors > >> > rather than just access to a configuration model. > >> If it makes sense, I'd be open to extending my abstraction layer to make > >> it suitable for your use case as well. > >> Feel free to propose changes to it if you like. > > > > Having a first deeper look at scal I believe that access to sensors > > and actors could be implemented inside scal similar to the existing > > shell and system backends. That would be nice, as then scal would > > make things available on ubus and provide the ACL mechanics. > Nice. Maybe we can reinterpret the acronym as "System Communication > Abstraction Layer". I'd be fine with renaming it to something else as > well, I just didn't find a better name for it yet. > > I think a good approach would be to add a dlopen plugin API to the json > plugin itself, so you can use json files to parameterize access to > sensors and other devices. > > Event handling could also be scripted through .json files using > json_script. > > > I'll have a deeper look and play with it to see whether that can > > work. > > > > Ideally, data collection (think: interface counters and such things > > which need to be polled) and triggering events (think: link status > > updates) should also be made accessible. > > > > A local database which exceeds UCI state as suggested by Luka could > > also be very useful, eg. for renewable energy or other applications > > where loss of connectivity should never imply loss of collected data. > Makes sense. > > - Felix > ___ > 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
