From 6331e0868c475b47dd7fc52da3a539ef382858e2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcel=20St=C3=B6r?= Date: Thu, 17 Nov 2016 21:25:33 +0100 Subject: [PATCH] Turn SPI busses note to admonition note --- docs/en/modules/spi.md | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/docs/en/modules/spi.md b/docs/en/modules/spi.md index e4ce71a8..abe3a98f 100644 --- a/docs/en/modules/spi.md +++ b/docs/en/modules/spi.md @@ -6,15 +6,9 @@ All transactions for sending and receiving are most-significant-bit first and least-significant last. For technical details of the underlying hardware refer to [metalphreak's ESP8266 HSPI articles](http://d.av.id.au/blog/tag/hspi/). -## A note on the SPI busses +!!! note -The ESP hardware provides two SPI busses, with IDs 0, and 1, which map to pins -generally labelled SPI and HSPI. - -If you are using any kind of development board which provides flash, then bus -ID 0 (SPI) is almost certainly used for communicating with the flash chip. -You probably want to choose bus ID 1 (HSPI) for your communication, as you -will have uncontended use of it. + The ESP hardware provides two SPI busses, with IDs 0, and 1, which map to pins generally labelled SPI and HSPI. If you are using any kind of development board which provides flash, then bus ID 0 (SPI) is almost certainly used for communicating with the flash chip. You probably want to choose bus ID 1 (HSPI) for your communication, as you will have uncontended use of it. ## High Level Functions The high level functions provide a send & receive API for half- and