final release step (was: [RESULT][VOTE] Release Apache Mynewt ...)

On Fri, Dec 2, 2016 at 8:33 PM, Christopher Collins wrote: > Hello all, > > Voting for Apache Mynewt 1.0.0-b1-incubating-rc2 is now closed. Hi all, I was looking at prior releases, and noticed that the final step to publish the release appears to have been done wrong. No

Re: yield() and os_eventq_run()

On Sun, Dec 11, 2016 at 11:13:47AM -0800, Sterling Hughes wrote: > Hi, > > As a part of developing the sensor interface, I want to register a > “listener” on the event queue: > > listener.sl_sensor_type = type; > listener.sl_func = sensor_shell_read_listener; > listener.sl_arg =

Re: System init and OS eventq ensure

Hi, On Dec 11, 2016, at 10:55 AM, Christopher Collins wrote: On Sun, Dec 11, 2016 at 10:11:44AM -0800, will sanfilippo wrote: Personally, I keep wanting to try and have the OS start up right away. I wonder if this could solve the problem that Sterling raised (no

Re: System init and OS eventq ensure

I guess, for no really great reason, I thought it would be weird to malloc, say, 1024 bytes, then free, say, 960 bytes. No weirder than what I was suggesting. :-) I guess there a number of things we could do here: malloc a temporary stack and free that whole thing and either do another malloc

yield() and os_eventq_run()

Hi, As a part of developing the sensor interface, I want to register a “listener” on the event queue: listener.sl_sensor_type = type; listener.sl_func = sensor_shell_read_listener; listener.sl_arg = rc = sensor_register_listener(sensor, ); if (rc != 0) { goto

Re: System init and OS eventq ensure

On Sun, Dec 11, 2016 at 10:11:44AM -0800, will sanfilippo wrote: > Personally, I keep wanting to try and have the OS start up right away. I wonder if this could solve the problem that Sterling raised (no default event queue during sysinit). The control flow in main() might look like this: 1.

Re: System init and OS eventq ensure

Personally, I keep wanting to try and have the OS start up right away. There are definitely “issues” with this: a) We do not want to waste idle task stack. b) When tasks are started they would start running right away. This might cause issues where a task does something to a piece of memory that