|
1 | | -None |
| 1 | + |
2 | 2 | Introduction |
3 | 3 | ============ |
4 | 4 |
|
@@ -101,7 +101,7 @@ approximately 120 kB of extra compiled code to the ``micropython`` |
101 | 101 | can easily shave tens of kB off the firmware. In fact, if only a small |
102 | 102 | sub-set of functions are needed, you can get away with less than 10 kB |
103 | 103 | of flash space. See the section on `customising |
104 | | -ulab <#Custom_builds>`__. |
| 104 | +ulab <#Customising-the-firmware>`__. |
105 | 105 |
|
106 | 106 | Resources and legal matters |
107 | 107 | --------------------------- |
@@ -145,13 +145,13 @@ implementation details only, which all have been sorted out with the |
145 | 145 | generous and enthusiastic support of Jeff Epler from `Adafruit |
146 | 146 | Industries <http://www.adafruit.com>`__. |
147 | 147 |
|
148 | | -There are, however, a couple of instances, where the usage in the two |
149 | | -environments is different at the python level. These are how the class |
150 | | -properties can be accessed. We will point out the differences and |
151 | | -possible workarounds at the relevant places in this document. |
| 148 | +There are, however, a couple of instances, where the two environments |
| 149 | +differ at the python level in how the class properties can be accessed. |
| 150 | +We will point out the differences and possible workarounds at the |
| 151 | +relevant places in this document. |
152 | 152 |
|
153 | | -Customising ``ulab`` |
154 | | -==================== |
| 153 | +Customising the firmware |
| 154 | +======================== |
155 | 155 |
|
156 | 156 | As mentioned above, ``ulab`` has considerably grown since its |
157 | 157 | conception, which also means that it might no longer fit on the |
|
587 | 587 | #define NDARRAY_HAS_BINARY_OP_POWER (0) |
588 | 588 |
|
589 | 589 | definition. |
590 | | - |
591 | | -.. code:: |
592 | | -
|
593 | | - # code to be run in CPython |
594 | | - |
0 commit comments