Alexander Hübener

I can impl this trait in #397 for the legacy version of the driver.

Thanks for your great answer. Now I understand the system behind and can deal with these problems better. > In your case, the offending consumer is sub_1, as you are...

Thanks again, for clarification. > Mind sharing how exactly you fixed that? I recv() the events in a extra task to empty the queue. I will try it with signal/notification...

Coming back to the `AsyncEventBus`. It must work if I only subscribe to it for the period I need the events for?

Ah ok, good to know. So, info like this belongs to docs at the end, I guess? Or is this knowledge which should be obtained from the esp-idf docs.

Yes, I managed to get it working. I adjusted my driver settings to yours, and it works as well. For this, I use a `netif` with no dhcp, but it...

> @teamplayer3 Could you show full example? ```rust use std::{net::Ipv4Addr, time::Duration}; use anyhow::{bail, Result}; use embedded_svc::ipv4::{self, ClientSettings, Mask, Subnet}; use esp_idf_hal::{gpio::Gpio6, peripherals::Peripherals, spi::Dma, units::FromValueType}; use esp_idf_svc::{ eth::{EspEth, EthDriver, EthWait, SpiEthChipset},...

First I think the error `E (4388) w5500.mac: emac_w5500_transmit(523): free size (42) < send length (0)` is wrong implemented in esp-idf. https://github.com/espressif/esp-idf/blob/master/components/esp_eth/src/esp_eth_mac_w5500.c#L473 I think `free size` and `send length` is...

When you use a bare metal w5500 driver you can use [smoltcp](https://github.com/smoltcp-rs/smoltcp) for the http stuff I think. Or you can test the [w5500](https://github.com/kellerkindt/w5500) device driver. I think this driver...

> Tried to communicate with w5500 manually Can you show your implementation?