Hi all,
the link is not static but it needs to permanently point to a fresh
etherpad, according to this explanation in the wiki:
Minutes from past meetings are listed further below. If a meeting actually took
place, the link to the minutes will move downwards to the archive and a new
link f
Hey Paco!
On Wed, Jul 27, 2016 at 02:10:41PM +0200, Francisco Javier Acosta Padilla wrote:
> Not in my knowledge… Do you want to discuss something special? As the
> release is taking place I don’t know about the availability of people to
> discuss.
No reason for meeting from my side.
Cheers,
Ole
Hi Peter!
On Wed, Jul 27, 2016 at 02:09:22PM +0200, Peter Kietzmann wrote:
> as always you can find the link to an etherpad here:
>
> https://github.com/RIOT-OS/RIOT/wiki/Meetings
Thanks! Didn't know that there was a permanent link. (Or I forgot.)
> under point "Agenda for the next virtual meet
Hello!
Not in my knowledge… Do you want to discuss something special? As the release
is taking place I don’t know about the availability of people to discuss.
Cheers,
--
Francisco Javier Acosta Padilla
Research Engineer at INRIA Saclay
INFINE Team
On 27 July 2016 at 14:02:56, Oleg Hahm (olive
Hi,
as always you can find the link to an etherpad here:
https://github.com/RIOT-OS/RIOT/wiki/Meetings
under point "Agenda for the next virtual meeting". There is not topic on
the agenda so we skip this meeting.
Best
Peter
Am 27.07.2016 um 14:01 schrieb Oleg Hahm:
Dear release-preparing
Dear release-preparing IOTlers,
do we have an Etherpad with an agenda for today's meeting?
If not, do we need one?
Cheers,
Oleg
On Tue, Jul 26, 2016 at 12:00:07PM +, Google Calendar wrote:
> This is a notification for:
>
> Title: Biweekly virtual meeting
> Developer discussions that will o
Hi,
as said, the radio driver uses the CPUID for hardware address
generation, so yes. See this line and following:
https://github.com/RIOT-OS/RIOT/blob/master/drivers/at86rf2xx/at86rf2xx.c#L77
Best
Peter
Am 27.07.2016 um 10:35 schrieb Adeel Mohammad Malik:
Hi again,
I was talking about t
Hi again,
I was talking about the HWaddr. I want to run the CCN stack directly over the
radio without any IP stack. Does the CPUID module also configure the hardware
addresses?
/Adeel
> -Original Message-
> From: devel [mailto:devel-boun...@riot-os.org] On Behalf Of Peter
> Kietzmann
>
Hi Adeel,
not sure I fully understand you previous mail. The driver will generate
a default hardware address which is based on the CPUID.
USEMODULE += at86rf233
AFAIK one of these modules is actually responsible for that
USEMODULE += gnrc_netdev_default
USEMODULE += auto_init_gnrc_netif
You
Hi Peter,
Do you mean I should get an address on my interface without having to configure
it manually? If so, which module (USEMODULE) is it exactly that has this effect?
/Adeel
> -Original Message-
> From: devel [mailto:devel-boun...@riot-os.org] On Behalf Of Peter
> Kietzmann
> Sent:
10 matches
Mail list logo
