Re: [riot-devel] sched_active_thread is a volatile pointer, but volatile is ignored

2019-02-26 Thread Marian Buschsieweke
Hi everyone, > I seem to remember that we tried making sched_active_thread non-volatile > at some point, breaking things, but that has also been a long time ago. I think the reason might be that the compiler reordered access to the variables. See C99 standard section 5.1.3 §5: > The least

Re: [riot-devel] USB PID number

2019-02-26 Thread Dylan Laduranty
Hi all, Le mar. 26 févr. 2019 à 09:51, Koen Zandberg a écrit : > Hi Juan, > > On 2/25/19 3:19 PM, Juan Ignacio Carrano wrote: > > Hi all, > > > > First of all, great work. Now to the VID, PID matter: I don't think we > > should get any VID. A single PID may be ok. > > > > Product numbers are

Re: [riot-devel] USB PID number

2019-02-26 Thread Koen Zandberg
Hi Juan, On 2/25/19 3:19 PM, Juan Ignacio Carrano wrote: > Hi all, > > First of all, great work. Now to the VID, PID matter: I don't think we > should get any VID. A single PID may be ok. > > Product numbers are for products. RIOT is not a product. Rather, it is > used to build product (or at