* After many long distractions, I have a smoltcp-compatible ethernet driver the RT1062 (Teensy4.1) working: https://github.com/Timvrakas/rt1062-eth-rs/blob/master/src/main.rs

- This is my first time around the block, is there anything I'm doing that is in poor taste, or better accomplished another way?
- In the current implementation, the user instantiates the TX and RX descriptor tables, and then passes `&mut`'s of them to the Device object. This is similar to the stm32-eth driver. I tried for a while to have the Device object instantiate and then use the descriptor tables, but I kept running into issues in the operation that I wasn't able to get to the bottom of. At times the program wouldn't even execute, and the Teensy has no JTAG header (boo!), so I put the issue to the side for now. Is there some deeper reason I'm missing for this approach when dealing with shared-ownership buffers? Here's the delta that causes failure: https://github.com/Timvrakas/rt1062-eth-rs/compare/broken
- How should I eventually try to package this code to make it useful within the ecosystem? How do we package config code that is both board and peripheral specific (pinmux in particular)