Björn Quentin

At least progress - I think the newer drivers added some config parameters - are we sure we set values which make sense (e.g. compared to what esp-idf's defaults are)?...

Many of those settings are a mystery since they are often not well documented - I usually try to align them with the defaults in esp-idf in that case Interesting...

The drivers are updated now - unfortunately you will need to patch esp-hal for now (until the next esp-hal release)

> Thanks for getting the drivers updated! Out of curiosity, after updating did sending and receiving just work? Maybe I just had a bad build. Yes, it just worked for...

Having a way for user code to a) subscribe to events and/or dequeue events b) get event data (see https://github.com/espressif/esp-idf/blob/9106c43accd9f5e75379f62f12597677213f5023/components/esp_wifi/include/esp_wifi_types_generic.h#L1032-L1146) Seems like a good idea. (we don't have it yet)...

In general, `alloc` wouldn't be a problem since we already require alloc - but since it's pushing data from an "internal" callback the memory should be allocated in internal-RAM (not...

> I'm not sure what you mean by the implementation shouldn't allocate on its own. e.g. a `Vec` exceeding its capacity would re-alloc Thinking about it: Is this use-case common...

> It's not a queue of events. Its a linked list of event handlers (blocking functions). The pinning is so the reference to the handler is stable. What would be...

I'd say let's start with a single callback and keep things simple for now. Especially since other APIs are like that and if we go this way here, we should...

> @bjoernQ not sure what `coex` is but I noticed you removed a few examples in esp-rs/esp-wifi-sys#166 Is this issues still valid in that case? Thanks for pointing this out....