Re: [riot-devel] Periodical (virtual) meetings

2014-11-04 Thread Oleg Hahm
Hi Lotte! Since it turned out that Monday afternoon (CET) is not feasible for everyone willing to attend, I propose to use a polling tool to determine the next date: https://dudle.inf.tu-dresden.de/RIOT-virt-dev-1/ Did you reach any conclusion from this dudle yet? (i.e. will there

Re: [riot-devel] RIOT/OpenWSN and TSCH support

2014-11-06 Thread Oleg Hahm
Hey Thomas! Happy to mention RIOT, I didn't know you were there :-) Yes, tomorrow I'll give a tutorial about RIOT on IoT-Lab. It was very nice talk, by the way. Particular, taking the time of day into account. ;-) Cheers, Oleg -- The best thing about declarative jokes is that you only have

[riot-devel] Help to defend FLOSS trademarks

2014-11-11 Thread Oleg Hahm
Dear rioters! Sorry for the slightly RIOT unrelated mail, but I just came across this call: https://gnome.org/groupon/ I think for us, as an open source community, it should be something we care about. As Lucas Nussbaum from Debian wrote: This legal defense is not just about protecting GNOME's

Re: [riot-devel] iot-lab_M3

2014-11-11 Thread Oleg Hahm
Hi Martin! Sorry, my bad. I'm trying to flash the iot-lab_M3 board and constantly fail on: ``` ... Error: no device found Error: unable to open ftdi device with vid 0403, pid 6010, description 'FITECO M3' and serial '*' ``` I was told that on the newer nodes they changed the device

Re: [riot-devel] iot-lab_M3

2014-11-11 Thread Oleg Hahm
Hi again! So, changing this in boards/iot-lab_M3/dist/iot-lab_M3_jtag.cfg should help. Or try with https://github.com/RIOT-OS/RIOT/pull/1996 - apparently `dev_desc` isn't really necessary. Cheers, Oleg -- printk(Churning and Burning -); linux-2.6.6/drivers/char/lcd.c

Re: [riot-devel] iot-lab_M3

2014-11-11 Thread Oleg Hahm
Hi Martin! thx for the reply and the PR, its better now, but now fails with: ``` ... Info : clock speed 1000 kHz Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3) Info : JTAG tap: stm32f1x.bs tap/device found: 0x06414041 (mfg: 0x020, part:

Re: [riot-devel] Problem with RPL-UDP example for SAMR21

2014-12-04 Thread Oleg Hahm
Hi! I downloaded it on the Riot master branch today But since https://github.com/RIOT-OS/RIOT/pull/1997 isn't merged, how do you access the radio? Cheers, Oleg -- /* These are the most dangerous and useful defines. They do printk() during * the interrupt processing routine(s), so if you

Re: [riot-devel] Problem with RPL-UDP example for SAMR21

2014-12-04 Thread Oleg Hahm
Hi! Yes right, I work on this branch : https://github.com/Troels51/RIOT/tree/samr21-transceiver-port Ok, I'll try tomorrow if I can find one to borrow me another board. Cheers, Oleg -- T he bes thin gabou tTCPfl owcontr oljokesi sthatthey knowwhento backo ff pgpXRQAHeNbaU.pgp

Re: [riot-devel] Switch to BSD?

2014-12-15 Thread Oleg Hahm
Hi! On Mon, Dec 15, 2014 at 01:08:24PM +0100, Kaspar Schleiser wrote: On 12/15/2014 11:10 AM, Ludwig Ortmann wrote: I'd rather add a static linking exception to our current license (or switch to GPL with linking exception which amounts to the same as far as I remember) What kind of

Re: [riot-devel] Switch to BSD?

2014-12-15 Thread Oleg Hahm
Hi Kaspar! 1. The entity distributing such a product must mention the use of RIOT. Isn't that the case also for some non-copyleft licenses (e.g. some BSD-style licenses)? Not sure, just asking. This requires the device to be field-upgradable I still seriously doubt this. We're talking about

Re: [riot-devel] Periodical (virtual) meetings

2014-12-15 Thread Oleg Hahm
Hi Martine! Yes, I'm not among those (though I have to admit, that I missed the last to meetings too :() + all the worlds not Berlin and Hamburg. If you see each other you can join in bulk and the rest will join virtually. How about that? That will probably not work out, because we won't

Re: [riot-devel] Switch to BSD?

2014-12-15 Thread Oleg Hahm
Hey Hauke! In an ideal world I would personally want RIOT to be even published under GPL, as of RIOT should be free. But we all know that world does not exist. I would say: In an ideal world RIOT should have been published as public domain. Cheers, Oleg -- panic(smp_callin()

Re: [riot-devel] Switch to BSD?

2014-12-16 Thread Oleg Hahm
Hey Kaspar! IMHO this is not a oooh how nice, someone found a way to make money out of this! good for them! situation. It has the possiblity to become a Oh nice. Those contributers write code we can sell and they don't want anything in return situation. I think it is both. And I understand

Re: [riot-devel] Switch to BSD?

2014-12-16 Thread Oleg Hahm
Hi Ludwig! So in that case, you can't even (legally) sell a product based on RIOT without it (and you) being mentioned. Referring to a discussion I had with Hauke over lunch: would have RIOT to be mentioned only in the code or on the sold product (let's say an Internet connected toy dinosaur)?

Re: [riot-devel] Periodical (virtual) meetings

2014-12-17 Thread Oleg Hahm
Hi! PlaceCam is go at: http://placecam.de/call.php?c=VBYEpXi43MZ2MOrV~pegsMm6Z7woUbw.VRY0Qxal2pE- Cheers, Oleg Am Mon, Dec 15, 2014 at 05:03:52PM +0100 schrieb Oleg Hahm: Hi Martine! Yes, I'm not among those (though I have to admit, that I missed the last to meetings too :() + all

[riot-devel] Merry Christmas and a Happy New Year

2014-12-24 Thread Oleg Hahm
Dear romantic IoTlers, for those of you not using Twitter (regularly), let me point to https://twitter.com/RIOT_OS/status/547442255456649217 Thanks for a very successful year, great work and fruitful discussions in an awesome community. Let's hope for another amazing year with RIOT in 2015. Have

Re: [riot-devel] Network Stack Task Force

2015-01-16 Thread Oleg Hahm
Hey Hauke! For the workshop I propose January 27-28, but its just a proposal... Keep in mind, that the next HA is scheduled for January 27. Cheers, Oleg -- The bad thing about Kerberos jokes is that I can't tell them to you because I don't trust you and I don't know your name!

Re: [riot-devel] Network Stack Task Force

2015-01-16 Thread Oleg Hahm
Hi! - who is interested (and/or) wiling to joing this effort? Count me in. - are there any ideas on the concrete organization of such a task-force? I think this depends on the size and distribution of the group. - are there technical aspects I forgot? Did one of your proposed aspects

Re: [riot-devel] Network Stack Task Force

2015-01-16 Thread Oleg Hahm
Hey! For the workshop I propose January 27-28, but its just a proposal... Keep in mind, that the next HA is scheduled for January 27. Of course I did not. :-) But I think thats a perfect fit! I'm not so convinced about that. To my understanding the HA is mostly about speeding up the merge of

Re: [riot-devel] Network Stack Task Force

2015-01-16 Thread Oleg Hahm
Hi! Is it going to be in cbase or somewhere else? It's gonna be C-Base again. Cheers, Oleg -- The best thing about Appletalk is that nobody is using it any more. pgpqLzeBIH85k.pgp Description: PGP signature ___ devel mailing list devel@riot-os.org

Re: [riot-devel] OTA meetup 11.2.2015

2015-02-16 Thread Oleg Hahm
Hi! the minutes from the meeting have been added to our wiki: https://github.com/RIOT-OS/RIOT/wiki/minutes-OTA-meetup-13.2.2015 Have there any concrete next steps been identified? Did you conclude in some kind of a schedule for upcoming tasks and who is gonna work on what? Cheers, Oleg -- /*

[riot-devel] About function pointers

2015-02-18 Thread Oleg Hahm
Dear remodeling IoTlers! Ludwig just made me aware that Joakim's PR for NVRAM [1] introduces function pointers as part of the device driver struct. This made me remember that there were already similar function pointers introduced as part of netdev. As I was always opposed to use function

Re: [riot-devel] About function pointers

2015-02-18 Thread Oleg Hahm
Hi Pekka, thanks for your input. Of course, some care is needed to make sure that the compiler does the right thing. It is relatively easy to break the pattern. I see your point, but actually, I don't want to build a whole system model based on any assumption about what the compiler might

Re: [riot-devel] About function pointers

2015-02-18 Thread Oleg Hahm
Hi Kévin! I began to use function pointers in the 'radio_driver.h' when trying to create a unified model for radio drivers. I guess it went over later to the whole netdev effort. Yes, I remember that, but why can't this be implemented in a similar way we did for most of the peripheral drivers

Re: [riot-devel] About function pointers

2015-02-18 Thread Oleg Hahm
Hi Ryan! In my opinion this is a cleaner abstraction, and leads to clearer parallel composition (or wiring) of modules, rather than the oft used vertical composition. So, basically you're saying that trading some performance for a cleaner design is a good thing, is that right? I would say

Re: [riot-devel] LGPL compliance testing

2015-02-16 Thread Oleg Hahm
Hey Kaspar! While I personally wouldn't use such restricting development environments in the first place, using RIOT for proprietary development here probably wouldn't be feasible. Well, that's not always feasible. I remember that my old company was somehow forced to use a proprietary IDE (we

Re: [riot-devel] PlaceCam on Linux with echo-cancellation

2015-02-16 Thread Oleg Hahm
Hi! PS: Open Research Topic: Find out how to automatically or at least super-conveniently (I'm thinking push-to-talk) mute the microphone when not speaking. Well, you can mute yourself, whenever you're not speaking, so it would be something like click-to-talk. I would like to add a

Re: [riot-devel] About function pointers

2015-02-19 Thread Oleg Hahm
Hi Kaspar! On 02/18/15 22:50, Oleg Hahm wrote: but we don't know which weird compilers on some esoteric hardware platform might be used for RIOT somewhere sometime, so I rather rely on optimized C code than on optimized compilers. this keeps popping up as an excuse not to do some elegant

Re: [riot-devel] LGPL compliance testing

2015-02-20 Thread Oleg Hahm
Hey Kaspar! Using a weird compiler that cannot output the required object files because it is closed source and proprietary is purely political. That compiler could be changed trivially *if it would be open source* or the vendor was inclined to do so. This doesn't count as technical reason.

Re: [riot-devel] Searchable devel@riot-os.org archive

2015-01-05 Thread Oleg Hahm
Hi Adam! Am Tue, Dec 30, 2014 at 06:53:22PM + schrieb Adam Hunt: I've been meaning to let everyone know that RIOT's development list is now archived on Gmane http://gmane.org. The group name is gmane.os.riot.devel http://news.gmane.org/gmane.os.riot.devel/ and it includes every message

[riot-devel] Hack'n'ACK - 2015.01

2015-01-05 Thread Oleg Hahm
Dear RIOTers, I know it's a little bit short-termed, but the Hamburg and the Berlin RIOT crowd is planning to start the new year with another cracking Hack'n'ACK TOMORROW! Starting at 4pm (CET) at HAW and FU Berlin. Cheers, Oleg -- I saw your POST, but could only respond with OK - I guess I

Re: [riot-devel] Network refactoring

2015-01-05 Thread Oleg Hahm
Hi Baptiste, hi Martine! Maybe we can discuss a tentative schedule and set some milestones for the refactoring during a (PlaceCam) conf call this week? What do you think? Cheers, Oleg -- panic(esp: what could it be... I wonder...); linux-2.2.16/drivers/scsi/esp.c pgp9tyZuQums6.pgp

Re: [riot-devel] Hack'n'ACK - 2015.01

2015-01-06 Thread Oleg Hahm
Hey! In order to channel our efforts tonight, I setup a new label in the RIOT issue tracker and assigned it to some PRs that I consider as important to be merged first. See https://github.com/RIOT-OS/RIOT/labels/Hack'n'ACK%20candidate and feel free to add or remove PRs here. Cheers, Oleg -- A

Re: [riot-devel] reserve main and let application define thread(s)

2015-02-13 Thread Oleg Hahm
Hi! My proposal: Let the application Makefile export one or possibly several names to be used for the initial application thread(s). kernel_init will then take care of creating those. The function name main will be reserved for boards/cpus to implement. In case of native/PsoC, the cpu's

[riot-devel] IoT OS must be open

2015-01-07 Thread Oleg Hahm
...says the CEO of Samsung: http://www.channelnomics.com/channelnomics-us/news/2388743/iot-os-must-be-open-samsung-ceo -- I had an Ethernet joke, but somebody else told it at the same time. So I exponentially backed off and tried again. pgpEsGl6VXXIw.pgp Description: PGP signature

Re: [riot-devel] Benchmarks

2015-03-18 Thread Oleg Hahm
Hi Ludwig! I think our only m0+/802.15.4 board is the samr21-xpro and there are problems with the current/old network stack because of its memory demands. I haven't followed the discussion about RPL and UDP on the SAMR21 lately, but doesn't these memory problems only exist when using with RPL

Re: [riot-devel] Virtual GSOC Meeting

2015-03-18 Thread Oleg Hahm
Oops, synchronization problem I guess. We'll use this link then! Am Wed, Mar 18, 2015 at 02:01:57PM +0100 schrieb Hauke Petersen: Hi everyone, as promised we will have a dedicated GSOC meeting now. To join please follow this link:

Re: [riot-devel] Virtual GSOC Meeting

2015-03-18 Thread Oleg Hahm
Dear GSOC participants and mentors, please join the meeting at http://placecam.de/call.php?c=VBYEpXi43MZ2MOrV~pegsMm6Z7woUbw.VRY0Qxal2pE- (see https://github.com/RIOT-OS/RIOT/wiki/Instructions-for-remote-participation for instructions how to use PlaceCam) Cheers, Oleg Am Mon, Mar 16, 2015 at

Re: [riot-devel] Virtual GSOC Meeting

2015-03-18 Thread Oleg Hahm
Dear GSOC enthusiasts, please find the minutes from our meeting at http://pad.spline.de/Ouide7Nzd8 Cheers, Oleg -- panic(If this is a 64-bit machine, please try a 64-bit kernel.\n); linux-2.6.6/arch/parisc/kernel/inventory.c pgpYdZZJZK5WD.pgp Description: PGP signature

[riot-devel] More convenient access to the IoT-LAB from a RIOT application

2015-03-18 Thread Oleg Hahm
Dear rewewing IoTlers, I just opened a pull request in RIOT that should ease the work with RIOT applications on the IoT-LAB testbed a little bit: https://github.com/RIOT-OS/RIOT/pull/2640 Including the proposed Makefile like include $(RIOTBASE)/dist/Makefile.iot-lab in an application's

Re: [riot-devel] Need help about RIOT radio communicate example

2015-03-16 Thread Oleg Hahm
Hi Chen! I connect 2 telosb to 2 USB port and used 2 terminal to make term to each telosb board. I guess you're using the default example, right? Then I use one board to txtsnd to other board address. But there is no reaction from the other board. (For native mode, the other should show

Re: [riot-devel] board-specific development

2015-03-16 Thread Oleg Hahm
Hi Ralph! I don't think I see redbee-econotag listed as a supported board on the wiki home page. Is it no longer actively supported? I think the support for the econotag in RIOT has always been rather poor. I'm not aware that support for it was dropped officially, but considering the state of

Re: [riot-devel] NFC Atmel AT86RF232B

2015-03-19 Thread Oleg Hahm
Hi Thomas! I got me some NXP pn532 modules some time ago as I heard there is work on specifying 6LoWPAN over ISO 14443 (which NFC is part of). Indeed, there is. See https://tools.ietf.org/html/draft-ietf-6lo-nfc-00 Sadly, I didn’t come too far with the driver, as it includes a (more)

Re: [riot-devel] Benchmarks

2015-03-19 Thread Oleg Hahm
Hi Simon! Yes I tried to compile the rpl_udp example for the samr21-xpro but it did not have enough RAM. Even with RPL in non-storing mode and a very small routing table it would not fit. Well, in non-storing you basically don't need any routing table (except for the root node), but still it

Re: [riot-devel] More convenient access to the IoT-LAB from a RIOT application

2015-03-20 Thread Oleg Hahm
Kaspar, How can I select some nodes? The current version of this Makefile only allows you to specify the number, the type, and the testbed site of the nodes. I don't know how sensible it would be to add a more concrete node selection process to this feature. You can pretty easily specify the

Re: [riot-devel] Biweekly virtual meeting

2015-03-21 Thread Oleg Hahm
Dear radioing IoTlers, the next regular bi-weekly PlaceCam meeting would usually be scheduled next Wednesday at 10am CET. However, since we have some potential participants in other timezones (including me), I would like to ask if we could reschedule the meeting to 2pm CET again? This would be

Re: [riot-devel] Iotivity, AllJoyn, Thread, Ipso Alliance

2015-03-21 Thread Oleg Hahm
Hi! I just realized that I'll probably learn something about IoTivity and AllJoyn today at the T2TRG meeting: https://github.com/t2trg/2015-ietf92/blob/master/agenda.md I guess there won't be now audio stream, but at least the slides should be online later this day. Concerning IoTBase, I

[riot-devel] Removing thirdparty repositories

2015-03-21 Thread Oleg Hahm
Dear rousing IoTlers, since we don't need the thirdparty repositories for CPUs and boards any more for quite some time, I think we should finally remove them. Any objections? Can anyone with some experience with the Cortex ports take a look at the PRs in these repos that are still open and see if

Re: [riot-devel] Build issue on Windows (8.1)

2015-03-16 Thread Oleg Hahm
Hi! well written guide :) Thanks for the effort! Yes, indeed. Thanks a lot. I added a link to it to the wiki start page. Cheers, Oleg -- printk(KERN_WARNING Hey who turned the DMA off?\n); linux-2.6.6/drivers/net/wan/z85230.c pgpKbBav5Lv7z.pgp Description: PGP signature

Re: [riot-devel] GSoC 2015 Introduction - N1 BLE Project

2015-03-16 Thread Oleg Hahm
Hi Alexis! Welcome to RIOT! I'm Alexis, from Lyon, France, student in Telecom Engineering. I'm fond of IoT, embedded development, FOS Projects, and I'm currently doing a master thesis in Barcelona, wich focus on Thread ( http://www.threadgroup.org/) protocols stack. May I ask you what

Re: [riot-devel] printing uint64_t

2015-03-09 Thread Oleg Hahm
Hi Ralph! Is there something I'm doing that's obviously wrong? I guess this problem is related to the Newlib-Nano [1] we're using if the toolchain supports it. This library doesn't support 64-bit printing. If it's required for you, you could try to disable it in the Makefile (e.g.

Re: [riot-devel] printing uint64_t

2015-03-09 Thread Oleg Hahm
Hi Ralph! I guess this problem is related to the Newlib-Nano [1] we're using if the toolchain supports it. This library doesn't support 64-bit printing. If it's required for you, you could try to disable it in the Makefile (e.g. boards/samr21-xpro/Makefile.include, for the Atmel board),

Re: [riot-devel] Biweekly virtual meeting

2015-03-12 Thread Oleg Hahm
Hi David! Did you try with the new link from me? We're right about to start to talk about GSOC topics. Cheers, Oleg Am Wed, Mar 11, 2015 at 05:35:48AM -0400 schrieb David Reinert: So I was in the meeting and then I restarted PlaceCam in order to try and remove any echo from my microphone.

Re: [riot-devel] TLS

2015-03-11 Thread Oleg Hahm
Hi Matthias! There is also a port of the Relic library toolkit https://code.google.com/p/relic-toolkit/ including an extension for modern Edwards Curves (ECC). For the current status of the Relic porting see https://github.com/RIOT-OS/RIOT/pull/2213 - I think it's only a matter of a few days

Re: [riot-devel] Build issue on Windows (8.1)

2015-03-11 Thread Oleg Hahm
Hi Murat! make BOARD=mbed_lpc1768 arm-none-eabi-gcc.exe: error: /cygdrive/d/developments/RIOT/examples/ipc_pingpong/main.c: No such file or directory arm-none-eabi-gcc.exe: fatal error: no input files I have currently no Windows machine to test at hand, but could test to build with

Re: [riot-devel] Gsoc 2015

2015-03-07 Thread Oleg Hahm
Dear Kausthub! I wanted to know if i can work on my Linux system itself or do I need to get a separate system to run it ? For basic familiarization with RIOT and higher layer implementations, you can use RIOT's native port [1]. However, for concrete driver development you will need real

Re: [riot-devel] Biweekly virtual meeting

2015-03-11 Thread Oleg Hahm
Hi! I am not able to join via the new link either. Its says RIOT not online. Can you try with http://placecam.de/call.php?c=lmakKMrDG8a35aIBNqLBvOnApExkKFntj9xXawGNgTc- Cheers, Oleg -- panic(Unable to find empty mailbox for aha1542.\n); linux-2.2.16/drivers/scsi/aha1542.c

Re: [riot-devel] Build issue on Windows (8.1)

2015-03-12 Thread Oleg Hahm
Hi Murat! I have used MinGW instead of Cygwin and problem is solved. Glad to hear. Following link was very helpfull for setting MinGW : http://www.jann.cc/2013/10/10/embedded_development_with_open_source_tools_on_windows.html Would you mind to maybe add a brief description to the RIOT

Re: [riot-devel] Notification: Biweekly virtual meeting @ Every 2 weeks from 10am to 11am on Wednesday (RIOT Events)

2015-03-24 Thread Oleg Hahm
Hi Peter! just to avoid confusion: Didn't we agree to have the meeting tomorrow at 2pm CET? Thanks for asking: Yes, we did, but I think no one cared to update the calendar. PlaceCam will be on at 2pm CET! Cheers, Oleg -- I'm working on a bittorrent joke, but I only have about 30% and

[riot-devel] Upcoming ETSI Plugtests

2015-03-24 Thread Oleg Hahm
Dear reading IOTlers, the next upcoming Plugtests organized by ETSI which are of interest for RIOT are announced as follows: * July 17-19, 2015 - 6tisch in Prague co-located with IETF 93 * October 30 - November 1, 2015 - 6lo in Yokohama co-located with IETF 94 * March 2016

Re: [riot-devel] Build issue on Windows (8.1)

2015-03-31 Thread Oleg Hahm
. -Original Message- From: devel [mailto:devel-boun...@riot-os.org] On Behalf Of Oleg Hahm Sent: Thursday, March 12, 2015 5:26 PM To: RIOT OS kernel developers Subject: Re: [riot-devel] Build issue on Windows (8.1) Hi Murat! I have used MinGW instead of Cygwin and problem

[riot-devel] Force Push on master

2015-03-31 Thread Oleg Hahm
Hi, FYI there was a mishap by an anonymous RIOT maintainer this morning which got fixed by a force push to restore the correction version RIOT master. Therefore, I had to remerge https://github.com/RIOT-OS/RIOT/pull/2742 and Cenk's merge commit got lost. Sorry for any inconvenience! Cheers,

Re: [riot-devel] Build issue on Windows (8.1)

2015-04-01 Thread Oleg Hahm
Hi Murat! I did not see any issue about picture. I have re-added same picture(address) to page again. Funny! Yesterday the picture was showing a red car... Thanks, Oleg -- The sad thing about IPv6 jokes is that almost no one understands them and no one is using them yet. pgpXgw6z1_u4r.pgp

Re: [riot-devel] Wakaama LWM2M

2015-03-26 Thread Oleg Hahm
Hi! Sorry, forgot my last post, used the wrong link. Cheers, Oleg Am Thu, Mar 26, 2015 at 11:30:09AM -0500 schrieb Oleg Hahm: Hi Ludwig! are they willing to support this endeavor in the form of a license change? I don't think it's necessary, it seems to be licensed under EDL (which

Re: [riot-devel] Wakaama LWM2M

2015-03-26 Thread Oleg Hahm
Hi Benjamin! Sorry if I missed some previous conversations, but what's wrong with BSD 3-clause? Nothing, but Wakaama is now licensed under EPL. Cheers, Oleg -- DPRINTK(FAILURE, CAPUT\n); linux-2.6.6/drivers/net/tokenring/ibmtr.c pgpc5ynNyN5by.pgp Description: PGP signature

Re: [riot-devel] Wakaama LWM2M

2015-03-26 Thread Oleg Hahm
Hi Ludwig! are they willing to support this endeavor in the form of a license change? I don't think it's necessary, it seems to be licensed under EDL (which is a BSD license) and not the GPL incompatible EPL. Cheers, Oleg -- /* * Hash table gook.. */ linux-2.4.0-test2/fs/buffer.c

Re: [riot-devel] Iotivity, AllJoyn, Thread, Ipso Alliance

2015-03-23 Thread Oleg Hahm
Hi! At least for IoTivity it should be fairly simple to port it to RIOT according to the response I got on their mailing list: http://lists.iotivity.org/pipermail/iotivity-dev/2015-March/000600.html The only problem I see is the incompatible license of their implementation. (Btw. the Contiki

Re: [riot-devel] Removing thirdparty repositories

2015-03-23 Thread Oleg Hahm
Hi! Okay, I removed it from the organization on Github. To be on the safe side I just moved it to my personal repos. Cheers, Oleg -- printk(KERN_DEBUG %s: Flex. T...\n, DRV_NAME); linux-2.6.6/drivers/net/wan/dscc4.c pgpPOJlgt5sAT.pgp Description: PGP signature

Re: [riot-devel] Feedback from emworld and future plans (partnerships AND licensing)

2015-02-27 Thread Oleg Hahm
Hi Jan! In addition to the other replies: - RIOT is an OS that is mostly powered by the community with alot of students of european universities(?) That's only half the truth: a big portion of the contributions to RIOT actually came from people paid by universities or research institutes (as

[riot-devel] Hack'n'ACK 2015-03-04

2015-03-01 Thread Oleg Hahm
Dear rolling IoTlers, the next RIOT HA party is almost here. You have only to sleep twice until we meet again in Hamburg (at HAW) and in Berlin (at c-base) - and who knows where else? If you're not lucky enough being able to join our local events or having at least one or two RIOTers living close

[riot-devel] This week's developer meeting

2015-02-23 Thread Oleg Hahm
Dear rocking IoTlers, due to the embedded world this week, several maintainers won't be available for this week's PlaceCam meeting. Hence, I have two questions: 1.) Is there anything urgent to discuss or can we skip the meeting? 2.) If we don't want to skip the meeting, is there anyone available

Re: [riot-devel] Repository for Docker builds

2015-02-23 Thread Oleg Hahm
Hi Joakim! I'm completely fine with that. Thanks for the effort! Cheers, Oleg Am Mon, Feb 23, 2015 at 09:18:42AM +0100 schrieb Joakim Gebart: I'd like to hear if anyone is strongly opposed to this, otherwise I will go ahead and create a new repository tomorrow. Best regards, Joakim Gebart

Re: [riot-devel] Repository for Docker builds

2015-02-23 Thread Oleg Hahm
Hi Joakim! What is a suitable name for the new repo? I have been using riotbuild for my Docker development at https://github.com/gebart/riotbuild I don't have any particular ideas for the name, so, for me riotbuild (or riotdocker) would be fine. Also, I need to have an organisation owner

Re: [riot-devel] Changing the workflow.

2015-02-24 Thread Oleg Hahm
Hi Martine! In general I like the concept and I think various people (including myself) proposed a similar workflow already in the past, but it was always rejected (IMO for good reasons), because of the introduced overhead and missing personal resources. I don't get this argument: With my

Re: [riot-devel] Switch to BSD?

2015-02-24 Thread Oleg Hahm
Dear RIOTers, I just found the eCos license: [1] http://ecos.sourceware.org/license-overview.html It's basically a modified version of the GPL with linker exception. The interesting point: it is officially recognised as a GPL-compatible Free Software License:

Re: [riot-devel] Switch to BSD?

2015-02-24 Thread Oleg Hahm
Hi Matthias! I thought that we already decided to exclude exotic licenses. Yes. GPL + Linker Exception is not exotic. With respect to this specific license: (1) We cannot use the license because the license text is specific to eCos (e.g., eCos is distributed [...]). And original

Re: [riot-devel] Wakaama LWM2M

2015-03-26 Thread Oleg Hahm
Hi Benjamin! Actually, it is dual-licensed under EPL and EDL (BSD). See https://projects.eclipse.org/projects/technology.wakaama Maybe that's a dumb question, but it doesn't seem obvious to me: does this dual-license allow to just chose between the two licenses? Cheers, Oleg -- The bad thing

Re: [riot-devel] Riot Software Update

2015-03-24 Thread Oleg Hahm
Hi Ludwig! yes, we agreed that in order to get software updates we need a foundation for activating new firmware images first. The working assumption for the first incarnation/iteration of this is that an image has been saved to some memory of the device already. Okay, basically my question

[riot-devel] [y...@isoc.org: [92all] Live video stream available - Re: Reminder: IETF 92 Lunch Host Speaker Series Tomorrow]

2015-03-25 Thread Oleg Hahm
FYI -- /* vsprintf.c -- Lars Wirzenius Linus Torvalds. */ * * Wirzenius wrote this portably, Torvalds fucked it up :-) */ linux-2.2.16/lib/vsprintf.c ---BeginMessage--- FYI, if you want to invite other people who are not in Dallas to view this session, you can direct them to:

Re: [riot-devel] Upcoming ETSI Plugtests

2015-03-26 Thread Oleg Hahm
Hi! * July 17-19, 2015 - 6tisch in Prague co-located with IETF 93 Some more detailed information about this plugtest and the roadmap towards this event is available as part of the 6tisch slides: http://www.ietf.org/proceedings/92/slides/slides-92-6tisch-2.pdf, slide 51 ff. Cheers,

[riot-devel] ENABLE_DEBUG per module?

2015-04-21 Thread Oleg Hahm
Dear reflecting IOTlers, some time ago Martine proposed to move the `ENABLE_DEBUG` macro from file to module context [1]. Since this would effect the whole RIOT printf debugging, I would like to call on the mailing list if someone thinks that this would be a bad idea. Cheers, Oleg [1]

Re: [riot-devel] Testing Task Force

2015-04-20 Thread Oleg Hahm
Hi! I realized that it is often the BUILDTEST_MCU_GROUP=cortex_m3_1 that run into a timeout or other weird issues that can mostly be solved by restarting this run. Any idea why this particular run seems to have resource problems? It's not even the biggest group. (But maybe the one with least

[riot-devel] NSTF - Naming the stack

2015-05-02 Thread Oleg Hahm
Dear roaring IOTlers, after some discussion with Kaspar yesterday, we came to the conclusion that it would probably make sense to give a name to the new IPv6 network stack. The rational (aside from making it easier to refer to it) is that some parts of its implementation can serve as common

Re: [riot-devel] NSTF - Naming the stack

2015-05-04 Thread Oleg Hahm
Hi! giving the ng_stack a name sounds like a very good idea to me (and as far as I remembered I already mentioned this last summer...). Though finding a name is tough and I don't like the obvious once (flexnet_, default_, riotnet_, etc...). To make it easier, I think we can even discard the

Re: [riot-devel] NSTF - Naming the stack

2015-05-02 Thread Oleg Hahm
Hi! What do you think? Due to its known meaning ng is as bad a name as new or next, because it will loose this meaning in the foreseeable future. Star Trek TNG hasn't lost its meaning even after twenty years... But I'm really not in favor of any particular name. I'm not sure if naming is

Re: [riot-devel] NSTF - Naming the stack

2015-05-03 Thread Oleg Hahm
Hi! I'm not in favor of keeping the prefix. Three reasons: Forget about the ng, that's unrelated to the question that we need a name for the stack. Cheers, Oleg -- printk(NONONONOO\n); linux-2.6.6/drivers/atm/zatm.c pgph9eCWJfIRE.pgp Description: PGP signature

Re: [riot-devel] Fwd: 64bit and multi core support

2015-05-07 Thread Oleg Hahm
Hi, forwarding to Alex, because he has not yet subscribed AFAIK. Alex, please subscribe to devel in order to get the replies. Cheers, Oleg On Thu, May 07, 2015 at 09:03:06PM +0200, Kaspar Schleiser wrote: Hi, On 05/07/15 20:33, Alex Mavrin wrote: We are considering using RIOT on our ARM

Re: [riot-devel] LPM idle_thread

2015-05-10 Thread Oleg Hahm
Hi! DEVELHELP should not be used to change the semantics of things. Can you elaborate? The system should behave the same whether develhelp is used or not. I would claim that this is impossible. Even a simple puts() already affects the timings, calls peripheral drivers, and may cause

Re: [riot-devel] LPM idle_thread

2015-05-10 Thread Oleg Hahm
Hi Kaspar! I would claim that this is impossible. Even a simple puts() already affects the timings, calls peripheral drivers, and may cause interrupts. the same was bad wording. I meant semantically, like Martine initially stated. I guess you mean Ludwig. I just wanted to point out that

Re: [riot-devel] Implementing a new MAC protocol for IEEE 802.15.4

2015-05-12 Thread Oleg Hahm
Hi Daniel! Is this not a requirement of the routing? Did you have a look at the IEEE 802.15.4 specification? It's assumed to have a so called PAN coordinator that forces the network to a star topology. It's extendable to a tree of stars, but still you need a PAN coordinator in every region.

Re: [riot-devel] LPM idle_thread

2015-05-09 Thread Oleg Hahm
Hi Frank! why is LPM_SLEEP or LPM_POWERDOWN is commented out? I think it's mostly commented out for debugging. Debugging with power save modes can become really nasty (even printf() debugging). However, I agree this shouldn't be solved like this. Another case for DEVELHELP, maybe? Cheers,

Re: [riot-devel] Network API task force

2015-05-08 Thread Oleg Hahm
Hi Kaspar! Actually, how a network stack internally communicates should be kept to that stack. I was talking exactly for the upper layers, e.g., applications. How do I bind to a UDP or TCP port? How do I write to a TCP connection? Well, no, than you're talking exactly about the second type

Re: [riot-devel] Network API task force

2015-05-08 Thread Oleg Hahm
Hi! That doesn't answer the question. A udp_send could in one implementation fill a pktbuf and use netapi, in another implementation just call the underlying send functions and return only when the payload has been copied into the send buffer, not malloc'ing extra memory. That should be

Re: [riot-devel] Network API task force

2015-05-08 Thread Oleg Hahm
Hi Kaspar! int ng_netapi_send(kernel_pid_t pid, ng_pktsnip_t *pkt); If we omit the messaging, and the pktbuf dependency, it is not netapi anymore. For me netapi are basically four functions send(), set_receive_cb(), get() and set(). This can be implemented as wrapper functions around IPC

Re: [riot-devel] NSTF - Naming the stack

2015-05-12 Thread Oleg Hahm
Hi, I just stumbled across ng_netconf - we should rename this to avoid confusion with RFC 6241 [1]. If the stack would have a name, we could simply call it NAME_conf... Cheers, Oleg [1] https://tools.ietf.org/html/rfc6241 -- panic(Alas, I survived.\n);

Re: [riot-devel] Implementing a new MAC protocol for IEEE 802.15.4

2015-05-12 Thread Oleg Hahm
Hi Daniel! As it seems that there are only 2 MAC implementations for now [1,2], both not what I'm searching for and also not merged, I decided to try this on my own. There's a third inside the OpenWSN stack using the TSCH (Time Slotted Channel Hopping) as specified in the IEEE 802.15.4e

Re: [riot-devel] NSTF - Naming the stack

2015-05-12 Thread Oleg Hahm
Hi! what about `ipc_stack` due to its utilization of the former? But still: I'm still not convinced of the reason to give it a name. All operating systems have a default stack but no one is bound to use it and can use their `ultra` stack etc. (in Linux e.g. as a library). The naming of uIP is

Re: [riot-devel] NSTF - Naming the stack

2015-05-18 Thread Oleg Hahm
Hey Kaspar! +1 for generic, but do we need the abbrevation? Aren't you usually the one arguing for short variable names and the like? Cheers, Oleg -- WHO HAS ANY ARP JOKES? pgpGuwdlBaDTu.pgp Description: PGP signature ___ devel mailing list

Re: [riot-devel] Support for Stellaris Launchpad LM4F120 board.

2015-05-18 Thread Oleg Hahm
Hi! Also, can someone help me with list of functions RIOT is actually using from Newlib. ? The RIOT core itself mainly uses printf for debugging. If you disable that (or provide your own minimal version of printf), it should compile without any C library. Apart from that, some modules

Re: [riot-devel] Implementing a new MAC protocol for IEEE 802.15.4

2015-05-12 Thread Oleg Hahm
Hi Daniel! PAN coordinators are only required for the beacon enabled mode in IEEE 802.15.4. 6LoWPAN, for instance, does not require this mode (I'm not even sure if it is supported by the spec) and thus, there is no need for a PAN coordinator or star topology. That's unfortunately not the

  1   2   3   4   >