Re: Task Priorities

> On Nov 4, 2015, at 12:30 PM, Sterling Hughes wrote: > > I think this is documentation. You may want it to be the highest > priority task, but what if somebody has two interfaces, and doesn't > care if they miss packets or data on the BLE link? > > I think it should just

Re: Task Priorities

people define task priorities there is a risk that they give the BLE task an incorrect priority. This would be an issue with either approach btw. Anyway, I dont have a strong opinion either way. There are things I like and dislike about both approaches although I slight lean towards #1 as I am more

Task Priorities

by the MCU definition (e.g. hw/mcu/native, or hw/stm, etc.) I think task priorities are something that should be defined on a per-project level. From what I can see, there are two options for doing this: 1- Have the individual packages expect a #define from the project, in the following format