Re: [riot-devel] module documentation
Hello Haoyang, gnrc_netif_default is a pseudo-module, defined in Makefile.pseudomodules. Pseudo-modules are modules, that don't have code, but are used by the build-system to collect other modules as dependencies or to express a certain build configuration. gnrc can be found in `sys/net/gnrc`. If the directory the module resides in is called the same as the module, the MODULE macro needs not be set in the module's Makefile. Can you rephrase your second question. I have difficulties to understand what you are going at. Cheers, Martine 2015-11-17 21:42 GMT+01:00 Haoyang Yu : > Hi all, > > I followed that information provided by community, but did not find the > MODULE gnrc, and also just find gnrc_netif MODULE in sys, but not > gnrc_netif_default > > # gnrc is a meta module including all required, basic gnrc networking > modules > USEMODULE += gnrc > # use the default network interface for the board > USEMODULE += gnrc_netif_default > > # NOTE: 6LoWPAN will be included if IEEE802.15.4 devices are present > If I just want to get IEEE802.15.4 data, from my perspective I directly > use MODULE of gnrc_netif, right? And add packet header I defined by myself. > > Thanks for your answers. > > Cheers, > Haoyang > > > On Nov 17, 2015, at 10:05, Oleg Hahm wrote: > > > > Hi! > > > > One tiny addition: > > > > Am Tue, Nov 17, 2015 at 01:56:09PM +0100 schrieb Martine Lenders: > >> * gnrc_sixlowpan is the bare minimum implementation of 6LoWPAN for GNRC > >> * gnrc_sixlowpan_frag and gnrc_sixlowpan_iphc implenent 6LoWPAN > >> fragmentation and IP header compression respectively > > > > There is also *grnc_sixlowpan_ctx* for stateful compression (using the > 6co > > flag in RAs). > > > > Cheers, > > Oleg > > -- > > printk (KERN_ALERT "You are screwed! " ...); > >linux-2.6.6/arch/i386/kernel/efi.c > > ___ > > devel mailing list > > devel@riot-os.org > > https://lists.riot-os.org/mailman/listinfo/devel > > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Create a new module
Hello Haoyang, `gnrc_netif_default` is a pseudo module and defined in `Makefile.pseudomodules`. In `Makefile.dep` you can see that it pulls in `gnrc_netif` as a dependency. Best, Cenk On 18.11.2015 04:19, Haoyang Yu wrote: Hi Oleg, I do cannot find any Makefile claim this module as the name gnrc_netif_default. But I found one named gnrc_netif. # use the default network interface for the board USEMODULE += gnrc_netif_default I am wondering where can I find it. I used grep to search. Thank you very much. Cheers, Haoyang On Nov 4, 2015, at 18:22, Oleg Hahm wrote: Hello Haoyang, I am staring to create my own module for RIOT CCN stuff, I am wondering for the USEMODULE in Makefile, Cool, looking forward to this implementation. May I ask what kind of CCN stuff you're going to implement? Are you developing from scratch or do you use any existing CCN implementation as a foundation? How can I add a self-define module in Makefile, and how do we specify the name like? What is the underlying complying mechanism to find the module? Usually, the name and path of the module is derived from its directory name. If you create a folder like `sys/foobar` and put a Makefile there which contains a line like this: `include $(RIOTBASE)/Makefile.base` all C files in this folder will be compiled to something that is usable via `USEMODULE += foobar`. If you want to label your module different from its directory name for some reason, you can add another line to the Makefile before the above mentioned line saying `MODULE := myfoobar`. However, for stuff residing inside a subdirectory of `sys` like `sys/net/...` you will need to some lines to `sys/Makefile` in order to let Make find this module. Just look at the existing examples there. Cheers, Oleg -- printk(KERN_WARNING "Warning: defective CD-ROM (volume sequence number). Enabling \"cruft\" mount option.\n"); linux-2.2.16/fs/isofs/inode.c ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Create a new module
Hi Oleg, I do cannot find any Makefile claim this module as the name gnrc_netif_default. But I found one named gnrc_netif. # use the default network interface for the board USEMODULE += gnrc_netif_default I am wondering where can I find it. I used grep to search. Thank you very much. Cheers, Haoyang > On Nov 4, 2015, at 18:22, Oleg Hahm wrote: > > Hello Haoyang, > >> I am staring to create my own module for RIOT CCN stuff, I am wondering for >> the USEMODULE in Makefile, > > Cool, looking forward to this implementation. May I ask what kind of CCN stuff > you're going to implement? Are you developing from scratch or do you use any > existing CCN implementation as a foundation? > >> How can I add a self-define module in Makefile, and how do we specify the >> name like? What is the underlying complying mechanism to find the module? > > Usually, the name and path of the module is derived from its directory name. > If you create a folder like `sys/foobar` and put a Makefile there which > contains a line like this: > `include $(RIOTBASE)/Makefile.base` > all C files in this folder will be compiled to something that is usable via > `USEMODULE += foobar`. If you want to label your module different from its > directory name for some reason, you can add another line to the Makefile > before the above mentioned line saying `MODULE := myfoobar`. > > However, for stuff residing inside a subdirectory of `sys` like `sys/net/...` > you will need to some lines to `sys/Makefile` in order to let Make find this > module. Just look at the existing examples there. > > Cheers, > Oleg > -- > printk(KERN_WARNING "Warning: defective CD-ROM (volume sequence > number). Enabling \"cruft\" mount option.\n"); >linux-2.2.16/fs/isofs/inode.c > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] module documentation
Hi all, I followed that information provided by community, but did not find the MODULE gnrc, and also just find gnrc_netif MODULE in sys, but not gnrc_netif_default # gnrc is a meta module including all required, basic gnrc networking modules USEMODULE += gnrc # use the default network interface for the board USEMODULE += gnrc_netif_default # NOTE: 6LoWPAN will be included if IEEE802.15.4 devices are present If I just want to get IEEE802.15.4 data, from my perspective I directly use MODULE of gnrc_netif, right? And add packet header I defined by myself. Thanks for your answers. Cheers, Haoyang > On Nov 17, 2015, at 10:05, Oleg Hahm wrote: > > Hi! > > One tiny addition: > > Am Tue, Nov 17, 2015 at 01:56:09PM +0100 schrieb Martine Lenders: >> * gnrc_sixlowpan is the bare minimum implementation of 6LoWPAN for GNRC >> * gnrc_sixlowpan_frag and gnrc_sixlowpan_iphc implenent 6LoWPAN >> fragmentation and IP header compression respectively > > There is also *grnc_sixlowpan_ctx* for stateful compression (using the 6co > flag in RAs). > > Cheers, > Oleg > -- > printk (KERN_ALERT "You are screwed! " ...); >linux-2.6.6/arch/i386/kernel/efi.c > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] TI CC1310 and CC2650
Hi Oleg More a bastardized implementation. We are running RPL and implemented our own channel hopping on the CC1120 with 6LowPAN. We started off many moons ago when Things Squared V1 was available open source and before they went commercial. After many implementations we found that the our current platform on Contiki and associated "libraries" is to difficult and time consuming to maintain in the long run. So we have to think in a different modeso we are in an investigation phase to plot long term goals. B On 2015-11-17 05:06 PM, Oleg Hahm wrote: Hi Ben, a clarification question: Am Mon, Nov 16, 2015 at 11:23:12AM +0200 schrieb b...@vpt-systems.co.za: We are running Contiki on our MSP430 with CC1120 and CC1190 (PA) for our OpenWSN mesh network implementation. Debugging is a major issue on Contiki so I will be loading RIOT and see what is required in terms of porting You're using OpenWSN on top of Contiki? Cheers, Oleg ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] module documentation
Hi, > There is also *grnc_sixlowpan_ctx* for stateful compression (using the 6co flag in RAs). If you want to be precise, `gnrc_sixlowpan_ctx` is just the storage type for the context -> IPv6 prefix mapping. The stateful comression is provided by `gnrc_sixlowpan_iphc`. Cheers, Martine 2015-11-17 16:05 GMT+01:00 Oleg Hahm : > Hi! > > One tiny addition: > > Am Tue, Nov 17, 2015 at 01:56:09PM +0100 schrieb Martine Lenders: > > * gnrc_sixlowpan is the bare minimum implementation of 6LoWPAN for GNRC > > * gnrc_sixlowpan_frag and gnrc_sixlowpan_iphc implenent 6LoWPAN > > fragmentation and IP header compression respectively > > There is also *grnc_sixlowpan_ctx* for stateful compression (using the 6co > flag in RAs). > > Cheers, > Oleg > -- > printk (KERN_ALERT "You are screwed! " ...); > linux-2.6.6/arch/i386/kernel/efi.c > > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > > ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] TI CC1310 and CC2650
Hi Ben, a clarification question: Am Mon, Nov 16, 2015 at 11:23:12AM +0200 schrieb b...@vpt-systems.co.za: > We are running Contiki on our MSP430 with CC1120 and CC1190 (PA) for our > OpenWSN mesh network implementation. Debugging is a major issue on Contiki > so I will be loading RIOT and see what is required in terms of porting You're using OpenWSN on top of Contiki? Cheers, Oleg -- /* This is total bullshit: */ linux-2.6.6/drivers/video/sis/init301.c signature.asc Description: PGP signature ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] module documentation
Hi! One tiny addition: Am Tue, Nov 17, 2015 at 01:56:09PM +0100 schrieb Martine Lenders: > * gnrc_sixlowpan is the bare minimum implementation of 6LoWPAN for GNRC > * gnrc_sixlowpan_frag and gnrc_sixlowpan_iphc implenent 6LoWPAN > fragmentation and IP header compression respectively There is also *grnc_sixlowpan_ctx* for stateful compression (using the 6co flag in RAs). Cheers, Oleg -- printk (KERN_ALERT "You are screwed! " ...); linux-2.6.6/arch/i386/kernel/efi.c signature.asc Description: PGP signature ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Disabled Strider (1 and 2)
+1 for disabling (unless Philipp yells very loud now ;)
On Tue, Nov 17, 2015 at 1:49 PM, Oleg Hahm wrote:
> Hi,
>
> since the results of both Strider CI systems are currently of very limited
> use and confusing for many people, I decided to deactivate them for now. If
> you object, please shout now!
>
> Cheers,
> Oleg
> --
> panic("Lucy in the sky");
> linux-2.2.16/arch/sparc64/kernel/starfire.c
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] Notification: Biweekly virtual meeting @ Wed Nov 18, 2015 2pm - 3pm (RIOT Events)
This is a notification for: Title: Biweekly virtual meeting Developer discussions. Remote participation will be provided. When: Wed Nov 18, 2015 2pm - 3pm Berlin Calendar: RIOT Events Who: * Ludwig Ortmann - creator Event details: https://www.google.com/calendar/event?action=VIEW&eid=Z2tqN2ZyY3NmdnEzOWFkbDdmMXJkb2hrbzhfMjAxNTExMThUMTMwMDAwWiBrM3FsOHNldHY3bDQ4b2Zub2wwdGZ1dTZ0c0Bn Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this email at the account peterschme...@gmail.com because you are subscribed for notifications on calendar RIOT Events. To stop receiving these emails, please log in to https://www.google.com/calendar/ and change your notification settings for this calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] module documentation
Hi, Am 17.11.2015 11:16 schrieb "Emmanuel Baccelli" : > I agree that some text would be very helpful. Actually, the plan was to > indeed provide some such text very soon, right Martine? > yes, we are currently working on making the documentation more precise and helpful for the whole system. Not just IPv6 and 6LoWPAN. Actually, that was what I try to imply with "better documentation is one of our main goals for the next release(s)". > On Tue, Nov 17, 2015 at 11:03 AM, Kaspar Schleiser > wrote: > >> Hey Martine, >> >> […] >> When I saw Ralph's question, I was looking forward to you using the >> opportunity to put some light in how gnrc_ipv6, gnrc_ipv6_router, >> ipv6_router_default, sixlowpan, sixlowpan_nd, sixlowpan_router_nd, >> sixlowpan_border_router_sixlowpan_nd_host, ..., are related. >> > Not to go into much detail (that's what a landing page in our future documentation will be for; but thanks for pointing out, that pseudo-modules will need documentation too :-)), but: * gnrc_ipv6 is the main module implementing IPv6 for GNRC. Building just gnrc_ipv6 gives you the bare minimum you need for IPv6 communication: 1-hop sending and receiving * some sub-modules, like gnrc_ipv6_netif (IPv6-relevant interface data) and gnrc_ipv6_nc (neighbor cache) are independently usable (good for testing) from gnrc_ipv6, but essential to its functionality * gnrc_ipv6_router is a pseudo-module providing build-instructions to include routing capabilities for IPv6 (forwarding of packets + FIB) * gnrc_sixlowpan is the bare minimum implementation of 6LoWPAN for GNRC * gnrc_sixlowpan_frag and gnrc_sixlowpan_iphc implenent 6LoWPAN fragmentation and IP header compression respectively * gnrc_sixlowpan_nd provides base functionality for 6Lo-ND (but no behavior). * gnrc_sixlowpan_nd_host provides host behavior of 6Lo-ND * gnrc_sixlowpan_nd_router provides router behavior of 6Lo-ND * gnrc_sixlowpan_nd_border_router provides border router behavior of 6Lo-ND * either of the nd or router modules can be included or excluded from the build to optimize in a size-feature axis. The stack should still be operational, though the features of the missing modules would also be missing of course. * gnrc_.*_default are convenience modules that provide the required neighbor discoveries of the given mode and other modules needed for (size-wise) ideal full operation. Hope this was more helpful, Martine ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] Disabled Strider (1 and 2)
Hi,
since the results of both Strider CI systems are currently of very limited
use and confusing for many people, I decided to deactivate them for now. If
you object, please shout now!
Cheers,
Oleg
--
panic("Lucy in the sky");
linux-2.2.16/arch/sparc64/kernel/starfire.c
signature.asc
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] module documentation
Hi there, I agree that some text would be very helpful. Actually, the plan was to indeed provide some such text very soon, right Martine? Best, Emmanuel On Tue, Nov 17, 2015 at 11:03 AM, Kaspar Schleiser wrote: > Hey Martine, > > On 11/17/15 09:18, Martine Lenders wrote: > > The module documentation for RIOT can be found here [1]. > > duh. ;) > > When I saw Ralph's question, I was looking forward to you using the > opportunity to put some light in how gnrc_ipv6, gnrc_ipv6_router, > ipv6_router_default, sixlowpan, sixlowpan_nd, sixlowpan_router_nd, > sixlowpan_border_router_sixlowpan_nd_host, ..., are related. > > Sure, it might be in our doxygen, but some words of you might save hours > of clicking through multiple windows of html documentation. > > Kaspar > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] module documentation
Hey Martine, On 11/17/15 09:18, Martine Lenders wrote: > The module documentation for RIOT can be found here [1]. duh. ;) When I saw Ralph's question, I was looking forward to you using the opportunity to put some light in how gnrc_ipv6, gnrc_ipv6_router, ipv6_router_default, sixlowpan, sixlowpan_nd, sixlowpan_router_nd, sixlowpan_border_router_sixlowpan_nd_host, ..., are related. Sure, it might be in our doxygen, but some words of you might save hours of clicking through multiple windows of html documentation. Kaspar ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] RIOT for Zigduino
Greetings, I have been trying to port RIOT for Zigduino board for about a week (On and Off), but I am confused. Has anybody done porting for zigduio? or is there any specific steps I need to follow, besides the general guideline given in documentation? Thank you -- Behailu Shiferaw Negash Turku, Finland ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] module documentation
Hello Ralph, Sorry for the delay. The module documentation for RIOT can be found here [1]. The documentation for the particular modules you requested can be found there too [2] [3]. As better documentation is one of our main goals for the next release(s), we welcome feedback on those. Best regards, Martine [1] http://doc.riot-os.org/ [2] http://doc.riot-os.org/group__net__gnrc__ipv6.html [3] http://doc.riot-os.org/group__net__gnrc__sixlowpan.html 2015-11-12 16:04 GMT+01:00 Ralph Droms (rdroms) : > Where can I find documentation about available modules? > > In particular, I want to learn about the use cases and properties of the > gnrc_ipv6* and gnrc_sixlowpan* modules. > > - Ralph > > > > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > > ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
