Re: [riot-devel] Coding conventions amendment
Am Wed, 12 Oct 2016 16:33:11 +0200 schrieb Martin: > Am 10/12/2016 um 12:57 PM schrieb Ludwig Knüpfer: > > Am 12. Oktober 2016 09:48:28 MESZ, schrieb Oleg Hahm > > : > >> as far I'm concerned it has been an undocumented coding convention so > >> far to use `int` or `unsigned int` for iterator variables in a loop > >> instead of > >> fixed width integer types. Does anybody object to adding this to the coding > >> conventions explicitly? > > What about `size_t`? > +1 for size_t Hi, `size_t` is optimal for every architecture that does not use segmented memory. The only platform that I know which used segmented memory was 80286, which was not produced since the mid 90th. According to Wikipedia the last architecture that used segmented memory died out in 1997. So, +1 for size_t from me, too. Cheer René -- Freie Universität Berlin Veterinärmedizinische Bibliothek Oertzenweg 19b, 14163 Berlin Tel.: 030 838 59270 ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] qemu-i386 port
Am Tue, 9 Aug 2016 10:34:19 +0200 schrieb Martine Lenders: > we now have the third person wondering about the qemu-i386 port. Fact > is, it doesn't work (we do not even have the unittests activated > anymore). Is there a reason why we did not drop it yet (except making > all the good work by René void)? Hi Martine, Git does not forget, so even if the "board" is rm -rf'd for now nothing is lost. The current state is probably worse then not having the board at all. Shall I open a PR to pull the port, so it is obvious that the author is OK with the decision? Best, René ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Problem with "make" -lm missing.
Am Tue, 9 Aug 2016 10:21:51 + schrieb MiTsArAs Jimaras: > Because I have told to do so from my university! > > I can't explain further because I DON'T KNOW WHY! Hi, then either ask your prof / TA what your objective is or drop the class. You may quote the author of the qemu-i386 port (that's me) that the port is in a bad shape (that's true). But you are also welcome to bring the port up to speed, but please accept that we won't jump because the need port right now. RIOT has full support for multiple inexpensive boards that might work better for you than emulation. Please see: https://github.com/RIOT-OS/RIOT/wiki/RIOT-Platforms Regards René ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Απ: Απ: Make bootable .elf file!
Hi! Am Fri, 29 Jul 2016 08:40:55 + schrieb MiTsArAs Jimaras: > Now I get this on make all: > > [...] > /usr/lib/gcc/x86_64-linux-gnu/5/../../../../lib32/libm.so: undefined > reference to `__get_cpu_features@GLIBC_PRIVATE' There seems to be something broken. The linker should not care for provided .so files at all. Please post *all* the output of $ git reflog -n10 $ gcc -### $ make BOARD=qemu-i386 QUIET=0 clean all so we can try to find the error. But as others already mentioned, the port is not really maintained for a while now. Might be that it is quite broken for everyone right now. Thanks, René ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] RIOT-ESP8622
Am Fri, 1 Apr 2016 17:56:38 +0200 schrieb Hauke Petersen: > RIOT can certainly be ported to the ESP8622, and it would make for a > very interesting platform. I think some people (including myself) have > briefly looked into this, but there has been created no countable > output, yet. Hi, if someone (here in Berlin) wants to try their porting skills I could offer hardware: - ESP-12E (http://www.ebay.com/itm/171907430053) - ESP-201 (http://www.ebay.com/itm/181846574978) Cheers, René ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Switch to BSD?
Am Tue, 9 Dec 2014 10:36:32 +0100 schrieb Emmanuel Baccelli emmanuel.bacce...@inria.fr: this is a gentle reminder to input your opinions on this thread before Wednesday night (i.e., tomorrow). You cannot use any of my contributions under any BSD license, because I don't think that it is a logic choice. I would welcome Apache v2.0, and would think about MIT, but there is actually nothing that speaks in favor of BSD. -- “My head was aching, and I had a singular feeling—altogether new to me—that some one else was trying to get alice’s configuration” — http://thedoomthatcametopuppet.tumblr.com/post/104397636603/ ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Switch to BSD?
Sorry Adam, I don't know how your name got intermixed into my answer. I had no intention to misquote you, and I like your previous letter very much. -- “My head was aching, and I had a singular feeling—altogether new to me—that some one else was trying to get alice’s configuration” — http://thedoomthatcametopuppet.tumblr.com/post/104397636603/ ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel