Scott Lahteine

With an `M112`-style stop the host should get some clue that the machine is stopped when it no longer replies with "ok" and starts replying with "stopped." I don't know...

> foreshadowing The cogent exploration here is whether `const float &` is still helpful with the most recent AVR compilers. The old advice was that function calls are faster/smaller because...

- Are there some boards with an onboard SD card – or more than one – wired to use both SPI and SDIO? - If a board only has `media_driver_sdiocard`...

> I'm not sure what that achieves for the normal user since the menu would just mount the same media from before It ensures that an `M21` after an `M22`...

I suggest that we defer to the board's definition of `SDIO_SUPPORT` and assume that the onboard SD Card is SDIO in that instance. If it's not SDIO it should still...

Have a look at #25715 where I'm exhibiting a new concept for configuring drives that aims to simplify the user-level configuration of multiple volumes. It's not meant to compile successfully...

The parameters `G` and `M` are verboten. The `N` parameter is also best avoided, though we sometimes begrudgingly allow it. If XY count parameters are needed, the usual choice is...

Anyway, we already use `X` and `Y` parameters with LINEAR leveling to set the number of points in X and Y so that will simply be reused here with BILINEAR....

Other areas where this change will be taking effect include: - EEPROM code in `settings.cpp` will need to save/load the number of points in X and Y. - The `ABL_BILINEAR_SUBDIVISION`...

> You removed the whole G29 parameter logic... what should happen with that? You should reuse the logic already implemented for LINEAR but extend it to BILINEAR. > You rewrote...