Deploying to gh-pages from @ Klipper3d/klipper@1836ec431c 🚀

Benchmarks.html

@@ -2259,7 +2259,7 @@ config_stepper oid=2 step_pin=gpio27 dir_pin=gpio5 invert_step=-1 step_pulse_tic
 finalize_config crc=0
 </code></pre></div>
 
-<p>The test was last run on commit <code>f6718291</code> with gcc version
+<p>The test was last run on commit <code>14c105b8</code> with gcc version
 <code>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</code> on Raspberry Pi
 Pico and Pico 2 boards.</p>
 <table>
@@ -2272,11 +2272,11 @@ Pico and Pico 2 boards.</p>
 <tbody>
 <tr>
 <td>1 stepper</td>
-<td>5</td>
+<td>3</td>
 </tr>
 <tr>
 <td>3 stepper</td>
-<td>22</td>
+<td>14</td>
 </tr>
 </tbody>
 </table>
@@ -2299,9 +2299,9 @@ Pico and Pico 2 boards.</p>
 </tbody>
 </table>
 <p>(*) Note that the reported rp2040 ticks are relative to a 12Mhz
-scheduling timer and do not correspond to its 125Mhz internal ARM
+scheduling timer and do not correspond to its 200Mhz internal ARM
 processing rate. It is expected that 5 scheduling ticks corresponds to
-~47 ARM core cycles and 22 scheduling ticks corresponds to ~224 ARM
+~42 ARM core cycles and 14 scheduling ticks corresponds to ~225 ARM
 core cycles.</p>
 <h3 id="linux-mcu-step-rate-benchmark">Linux MCU step rate benchmark<a class="headerlink" href="#linux-mcu-step-rate-benchmark" title="Permanent link">&para;</a></h3>
 <p>The following configuration sequence is used on a Raspberry Pi:</p>

Features.html

@@ -1667,11 +1667,6 @@ represent total number of steps per second on the micro-controller.</p>
 <td>1622K</td>
 </tr>
 <tr>
-<td>RP2040</td>
-<td>2400K</td>
-<td>1636K</td>
-</tr>
-<tr>
 <td>SAM4E8E</td>
 <td>2500K</td>
 <td>1674K</td>
@@ -1697,6 +1692,11 @@ represent total number of steps per second on the micro-controller.</p>
 <td>2634K</td>
 </tr>
 <tr>
+<td>RP2040</td>
+<td>4000K</td>
+<td>2571K</td>
+</tr>
+<tr>
 <td>RP2350</td>
 <td>4167K</td>
 <td>2663K</td>