Ulf Lilleengen

Thanks, then it's clear that you can't write it, hmm. This line in your log output seems to indicate that it is indeed the Linux side that terminates the connection:...

@peteskubiak So, I've found 2 things that I've fixed on main now, if you care to try. I measured the timings from connection establish and until discovery was complete for...

@petekubiak Let me know when you've been able to retest with your new hardware. Would be great to have this solved before 0.1

Sounds good yeah

Quick update: i've update the bluetooth_trouble example to use the latest developments from trouble and bt-hci would should simplify the integration quite a bit.

Thanks for putting a lot of good ideas on the table everyone. My preference are the inversion of control APIs, as I think they are a better/natural fit for async....

Thanks for the feedback @jrjdavidson ! The non-generic examples cause a lot of code duplication, but we should be able to make them somewhat customizeable by passing embedded-hal traits for...

> Suggestion: such a list could be within Trouble as a "showcase" - that gets occasionally updated, but doesn't _guarantee_ the examples are e.g. up to date with the latest...

> …ystem clock frequency > > NOTE: @Dirbaio, > > The changes seem to work. But I'm concerned that removing the `tick-hz-1_000_000` from the `time-driver` feature may break existing users....

I think this is ready for review now. I've decided to put the 'control logic' into a separate module 'context' which allows running that control logic for a given context,...