Move note about CPI/processor speeds in readmes (mostly to force github to know tip of master with CI)

Author: cnlohr

README.md

@@ -103,12 +103,6 @@ Other third party tools are adding lots of examples, etc.  See the following rep
 
 You can open a github ticket or join my Discord in the #ch32v003fun channel.  Right now invites are private, so just ping me @cnlohr for an invite link.  My PMs are open.
 
-## General notes about the CH32V003.
-
-CPI/Processor Speed:
-
-Ignoring branches and load/stores, compressed instructions run at 1 CPI. Non-compressed instructions run at 1 CPI for the first 2 instructions, then further ones take 2 CPI regardless of how many more you have.  Running from RAM and running from FLASH have slightly different performance characteristics depending on wait states that should be measured in-situation.
-
 ### Footnotes/links
 
  * https://raw.githubusercontent.com/openwch/ch32v003/main/RISC-V%20QingKeV2%20Microprocessor%20Debug%20Manual.pdf Debugging Manual

misc/README.md

@@ -10,6 +10,12 @@ At 3.3v, it seems that for all speed configurations, the short drive current is
 
 At 5v the peak current power application is 90-100mA for emitter and collector.
 
+## General notes about the CH32V003.
+
+CPI/Processor Speed:
+
+Ignoring branches and load/stores, compressed instructions run at 1 CPI. Non-compressed instructions run at 1 CPI for the first 2 instructions, then further ones take 2 CPI regardless of how many more you have.  Running from RAM and running from FLASH have slightly different performance characteristics depending on wait states that should be measured in-situation.
+
 ## Building libgcc.a from source.
 
 1. Install prerequisites (for Debian-based systems; similar steps for other systems):