Add minutes for 2024-01-30

Author: adamgreig

minutes/2024-01-30.md

@@ -0,0 +1,58 @@
+# Embedded Working Group Meeting 2024-01-30
+
+* [Coordination Repository]
+* Meetings: Tuesday 8pm Europe/Berlin time
+* [Join the Chat]
+* Today's date: 2024-01-30
+* [Nominated issues](https://github.com/search?q=org%3Arust-embedded+label%3Anominated+is%3Aopen&type=Issues)
+* [IRC logs]
+
+[Coordination Repository]: https://github.com/rust-embedded/wg
+[Join the Chat]: https://matrix.to/#/#rust-embedded:matrix.org
+[IRC logs]: https://libera.irclog.whitequark.org/rust-embedded/2024-01-30
+
+## Attendance
+
+Write your GH username or Matrix handle here!
+
+* adamgreig
+* jannic
+* newAM
+* eldruin
+* GrantM11235
+* therealprof
+* BartMassey
+* greengenie
+* dirbaio
+
+## Agenda
+
+* Announcements
+    * RustNL embedded embedded impl days/unconference
+        * 2 days attached to the https://2024.rustnl.org/ conference
+        * likely Thu + Fri (May 9 + May 10) in Delft, NL
+    * rp2040-hal 0.9.2 released
+    * rtic v2 working on stable rust: https://github.com/rtic-rs/rtic/pull/888
+* Embedded HAL
+    * Infallible SPI CS pins https://github.com/rust-embedded/embedded-hal/pull/574
+* Cortex-M
+    * Bad c-m-rt errors?
+        * https://github.com/rust-embedded/cortex-m/issues/509
+        * Have linker errors changed since these were written?
+
+## Last Week's Minutes
+
+* Announcements
+    * svdtools 0.3.9 released
+* Embedded HAL
+    * ADC/voltmeter/ammeter traits https://github.com/rust-embedded/embedded-hal/pull/569
+        * Having volts and amps seems a bit arbitrary; should we also have temperature and light level and etc etc?
+        * There might be some value in such a set of traits but it doesn't seem like they belong in e-h
+        * Probably the original plan of an ADC trait is a better fit for embedded-hal, but there are design questions to resolve
+    * SPI sharing with fallible CS pins https://github.com/rust-embedded/embedded-hal/issues/573
+        * Perhaps the whole shared bus could be poisoned to reduce the runtime overhead
+        * But given the rarity of requiring fallible pins and not being able to just wrap them in a panicking wrapper, perhaps option 1 remains the best option for e-h-bus, with users requiring more sophisticated sharing/error handling able to roll their own
+        * @GrantM11235 to write a PR
+* svd2rust
+    * Safe/unsafe writers https://github.com/rust-embedded/svd2rust/pull/788
+* Continue last week's discussion on interrupt macro syntax across crates