sync_up: Add meeting notes page for next week.

diff --git a/meetings/sync_up/sync_up_2024-01-16.mdwn b/meetings/sync_up/sync_up_2024-01-16.mdwn
new file mode 100644 (file)
index 0000000..5b61150
--- /dev/null
+++ b/meetings/sync_up/sync_up_2024-01-16.mdwn
@@ -0,0 +1,91 @@
+# Tuesday 16th January 17:00 UTC
+
+* Previous notes: [[meetings/sync_up/sync_up_2024-01-09]]
+* Next day's notes: [[meetings/sync_up/sync_up_2024-01-17]]
+* Next week's notes: [[meetings/sync_up/sync_up_2024-01-23]]
+
+# Main Agenda
+
+* reminder of **only 5 weeks** until march 1st deadline
+  for completion of cavatools and cryptoprimitives.
+
+Discussion of commit frequency and other points mentioned in
+[this](https://lists.libre-soc.org/pipermail/libre-soc-dev/2024-January/005912.html)
+email thread. Points to be discussed:
+
+* TODO: Will be filled in the next few days
+* ...
+
+After meeting discussion, points agreed upon will be documented
+in the wiki.
+
+FOSDEM:
+
+* will need volunteers for the devroom:
+  - Watch speaker, keep track of time
+  - Carry mic to audience, keep questions short
+  - Watch the door, make sure talk doesn't get disturbed (people come in
+in the middle of a talk)
+* Make sure PDF slides for the talks are:
+  - Uploaded to pretalx platform in good time (two weeks before FOSDEM?)
+  - Resolution set to **1280x800** resolution, preferably 800x600.
+  - Higher-res slides can be uploaded later, but for the actual slides
+to be used during the event, resolution must be as mentioned above.
+  - Put all PDFs on the laptop to be used for presentations. Make sure
+we have copies just in case.
+  - More info on slides from Luke:
+[email archive](https://lists.libre-soc.org/pipermail/libre-soc-dev/2023-December/005892.html)
+
+Meeting notes:
+
+* Outstanding Cavatools tasks:
+  - [bug #980](https://bugs.libre-soc.org/show_bug.cgi?id=980)
+* Outstanding Cryptorouter tasks:
+  - Poly1305, [bug #1157](https://bugs.libre-soc.org/show_bug.cgi?id=1157)
+  [bug #1158](https://bugs.libre-soc.org/show_bug.cgi?id=1158),
+  [bug #1159](https://bugs.libre-soc.org/show_bug.cgi?id=1159)
+  - Ed25519,
+  [bug #1151](https://bugs.libre-soc.org/show_bug.cgi?id=1151),
+  [bug #1166](https://bugs.libre-soc.org/show_bug.cgi?id=1166),
+  [bug #1167](https://bugs.libre-soc.org/show_bug.cgi?id=1167)
+
+# Andrey
+
+- Came back from holiday yesterday.
+- [Bug #1048](https://bugs.libre-soc.org/show_bug.cgi?id=1048),
+  Cleaning up ls011 by using inline ld/st imports. 
+
+# Jacob
+
+- so, not a whole lot of news from me, i fixed a
+extra-parenthesis-in-a-wrong-spot bug for dmitry and fixed a bug
+luke left, but didn't actually make any coding progress beyond
+that.
+
+During call, walked with Sadoon through assembler:
+
+```
+summary: discussing how to best split into sub-word chunks
+for poly1305
+> tbh dsrd isn't better than other shifts here
+It did help with taking the shift remainders and stitching them together which shortened the code quite a bit
+Also considering doing sv.dsrd instead of two dsrd's since we already use setvl=2 here
+> sv.dsrd is 8 bytes, just like 2x dsrd 
+But it's a good demo of setvl anyways
+> yeah, being a good demo doesn't mean there isn't a better demo 
+The better demo is the mul/adds 😃
+> try using a different register than r0, the simulator may be treating that like (RA|0) and just using r0 in both iterations... 
+```
+
+# Sadoon
+
+* Working through Poly1305 assembler.
+* Poly1305, [bug #1157](https://bugs.libre-soc.org/show_bug.cgi?id=1157)
+* Learned to use `dsrd`, done in first half of poly1305_blocks. Had issues with using `sv.dsrd` but it's kind of working now, will use it.
+* TODO: Make comments on bug #1157.
+
+* After that, work with the team on presentations as well as my own
+
+[[!tag meeting2024]]
+[[!tag meeting_sync_up]]
+