Dear RIOTers,
we are happy to announce the first official bug fixing release of RIOT.
--- * RIOT 2018.10.1 * ---
This is a bug fixing release for the RIOT 2018.10 release.
The following bugs were fixed:
#10757: sock_dns: fix out-of-bound errors
-
Dear RIOTers,
we are happy to announce the 17th official release of RIOT:
--- * RIOT 2018.10 * ---
The 2018.10 release includes new features, like CoAP Resource Directory and
Block2, ESP32 support, rework of I2C interface, EEPROM registry,
Full and
Dear fellow RIOTers,
I've created the 2018.10 release branch, so we are now officially in
feature freeze. This means from now only bugfixes will be merged into
the `2018.10-branch`.
Currently there are 18 open issues tagged for the release [1]. Let's try
to resolve this issues in the
Dear RIOTers,
The 2018.10 release is on its way!
This is my first time taking care of the release process so all feedback is
welcome.
Here is a summary of the important dates
* Preliminary/soft feature release for high impact features: October 16th,
2018.
* Final/hard feature
4:01 PM, Jose wrote:
Here is the issue [1].
Best.
José
[1]: https://github.com/RIOT-OS/RIOT/issues/9856
On 08/29/2018 11:58 AM, Jose wrote:
Hi all,
I've seen some discussions [1] about configurations in GH Issues. It
seems there's interest in the community about exposing these kind
Hello RIOT developers,
Does it make sense to provide a RIOT (git submodule) folder in the
RIOT-OS/applications, pointing to the latest RIOT release?
I can see some reasons:
- Applications will always be in a working state
- Might be easier for new users to clone and use
We would require
Dear RIOT kernel developers,
I just posted the summary [1] of the **configurations breakout session**
we had in the RIOT summit.
In conclusion, we agreed in starting small and work first in per-module
config declarations in header files. Further steps might include tools
on top for
Hi all,
It seems there's a trend with storing the img files close to the code
instead of using an external repo (wiki, etc). I will refactor [1] and
continue the discussion there.
All comments and feedback are appreciated.
Cheers,
José
[1]: https://github.com/RIOT-OS/RIOT/pull/9818
On
the
`https://raw.githubusercontent.com/wiki/RIOT-OS/RIOT/images/` prefix to
their Doxygen pictures).
Is this ok for all?
Cheers,
José
On 8/22/18 3:01 PM, Jose wrote:
Hi all,
Check this attempt [1] using git-lfs. It also uses "a hidden repo"
like the wiki, but it's t
el as network stacks => Where should
these be located?
Anyway, we could already start migrating some obvious `lib` modules
(hashes, crypto, parsers, etc).
Cheers,
José
On 08/30/2018 02:47 PM, Kaspar Schleiser wrote:
Hi,
On 8/29/18 11:13 AM, Jose wrote:
1. Move the `net` folder to
Hi Emmanuel,
I suppose you mean '/sys/net' ->'/net'
Oops, yes. I meant `/net` folder.
Cheers,
José
On 08/29/2018 02:28 PM, Emmanuel Baccelli wrote:
Hi José,
thanks for tackling this!
On Wed, Aug 29, 2018 at 11:16 AM Jose <mailto:jose.ala...@haw-hamburg.de>> wrote:
Dear RIOT developers,
While working on the documentation refactor, I've had the impression the
`sys` folder has turned into a "everything that doesn't match core, cpu,
etc" folder.
I've seen some implicit categories:
- Actual sys (auto_init, event queues, C++ wrapper, power management,
31, Kaspar Schleiser kas...@schleiser.de a écrit :
On 8/21/18 11:28 AM, Jose wrote:
I personally think 2. (put them in the RIOT wiki) is the fastest way to
go and doesn't bloat the RIOT repository. But I would like to hear some
comments about this topic.
+1. Don't forget, the Wiki is a git repo
of symlinks.
Are the benefits greater than the drawbacks? If so, I can open a PR.
Cheers,
José
On 08/21/2018 01:06 PM, Jose wrote:
Hi all,
Thank you for your responses!
So, it seems we are converging to have them close to the code (RIOT
repo). I will give a look to git-lfs in the meantime
August 2018 at 11:31:37, Jose (jose.ala...@haw-hamburg.de) wrote:
Hi all,
After some time since the board entries were moved to the doxygen
documentation [1], we are facing the problem on where to put board pictures.
I see 2 cases:
1. We don't have the rights to distribute the picture
Dear RIOT maintainers,
Since #8516 [1] got finally merged, now we have the board documentation
in Doxygen [2]. The information will still be available in the wiki for
a while, but will be removed in further steps. I wrote some deprecation
messages pointing to [2] so users can follow the new
Dear maintainers,
Last Friday we had an offline discussion with some RIOT people about he
lack of a mechanism to configure Kernel parameters as well as
application specific configurations (private keys, timer values, etc).
Although RIOT is configurable via CFLAGS, there's no way to (easily)
Hello,
There is this PR [1] about moving all board documentation (specs, how to
flash, etc) from the wiki to Doxygen, which I would like to know your
thoughts since it's a major change in the RIOT documentation.
As stated there, the main motivation is to help developers keep the
documentation up
OK, I will go with the #ifdef proposal. Thanks :)
Cheers
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
Dear RIOTers,
I noticed the 'make flash' recompiles everything before flashing. What's
the reason behind this?
I'm working with some packages that require some time to configure/compile,
and everytime I run 'flash' I have to wait the whole process to finish. I
cannot even flash 2 boards at the
Hello cr0s,
Thank you for the information. I just noticed Emmanuel asked about the same
thing a couple of days ago. Great to hear that! :)
We just did some test on the PR and it's working OK for us.
We are really interested in the development of the netdev2 adoption for the
SX1276 driver. We
Hi Baptiste
Yes, I'm still working on it.
I'm planning to show a demo of the port in RIOT summit.
Cheers.
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
Hi,
I was wondering if there's a way to send raw data between nodes running on
native. I need to send OpenThread packets between nodes (through a radio
abstraction), and I'm having problems with TAP interface since they only
process ethernet frames.
I tried to hack a little bit (put these OT
now.
Best regards,
Jose
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
Hi community,
I'm porting the OpenThread stack to RIOT. I have hooks for sending and
receiving frames and for transmision/reception "Done" signals (TransmitDone
and ReceiveDone)
In their examples they are manually checking/sending IEEE802.15 ACK before
calling the corresponding Done hook, but
Thank you Kaspar! :)
I will check it.
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
Hi community!
I have been working on a SIM900 [1] driver and a PPP stack for allowing GSM
internet access in RIOT. The driver has to handle AT commands (for
accessing modem's data mode) through UART and manage the PPP connection.
Since most mobile devices work in the same way, I was thinking
Hello community!
I'm implementing a PPP stack for communication with a GPRS module.
Each PPP frame is different, can carry control data or IP data, and each
one has a lot of options and sub options (nested headers, etc). For
example, a control frame looks like this:
|--HDLC frame--|--LCP
Hi Bernhard:
I think power consumption is a good reason for having a RIOT border router.
I worked in some WSNs that measured the isotherm level of snow in a
mountain (data sent via GPRS), it was not easy to get there and you don't
have power lines. So you need batteries.
Considering you are
29 matches
Mail list logo
