Michael Keller

@etracer65: I see your point, but I think it is sufficient that users who use this element and don't want to see the warning in the warning element can disable...

@etracer65: Yeah, an alternate, fully configurable warning element would work too - we could probably reuse pretty much all of the code for it.

I don't have a good idea for naming this at the moment. 'Warnings 1' / 'Warnings 2' is the 'best' I can come up. I wonder if there is a...

@etracer65: Yes please for providing an example. And agreed on the single 32bit flag set for this - the CLI doesn't have to be user friendly, and the names are...

@etracer65: Agreed. The fact that `pg/` needs to be 'middle ground' is unpleasant - we could probably get around this by leaving `pg/` where it is, and adding an explicit...

Agreed that having `drivers/` at the same level as `test/` and 'utils/` isn't right at a logical level - if we move on this we should probably go for `src/main/drivers`...

@hydra: Yes, exactly, with the only exception being headers in `pg/`.

I agree with @etracer65 here. The idea makes sense from a practical perspective, but it should be based off the existing crash detection code, and not off gyro overflow detection.

@alexeystn: What are your thoughts on changing this to trigger attitude recovery based on crash detection?

@alexeystn: Unit tests are failing for this (`make test`).