meetings/sync_up/sync_up_2024-01-16.mdwn

   1 # Tuesday 16th January 17:00 UTC
   2
   3 * Previous notes: [[meetings/sync_up/sync_up_2024-01-09]]
   4 * Next day's notes: [[meetings/sync_up/sync_up_2024-01-17]]
   5 * Next week's notes: [[meetings/sync_up/sync_up_2024-01-23]]
   6
   7 # Main Agenda
   8
   9 * reminder of **only 5 weeks** until march 1st deadline
  10   for completion of cavatools and cryptoprimitives.
  11
  12 Discussion of commit frequency and other points mentioned in
  13 [this](https://lists.libre-soc.org/pipermail/libre-soc-dev/2024-January/005912.html)
  14 email thread. Points to be discussed:
  15
  16 * TODO: Will be filled in the next few days
  17 * ...
  18
  19 After meeting discussion, points agreed upon will be documented
  20 in the wiki.
  21
  22 FOSDEM:
  23
  24 * will need volunteers for the devroom:
  25   - Watch speaker, keep track of time
  26   - Carry mic to audience, keep questions short
  27   - Watch the door, make sure talk doesn't get disturbed (people come in
  28 in the middle of a talk)
  29 * Make sure PDF slides for the talks are:
  30   - Uploaded to pretalx platform in good time (two weeks before FOSDEM?)
  31   - Resolution set to **1280x800** resolution, preferably 800x600.
  32   - Higher-res slides can be uploaded later, but for the actual slides
  33 to be used during the event, resolution must be as mentioned above.
  34   - Put all PDFs on the laptop to be used for presentations. Make sure
  35 we have copies just in case.
  36   - More info on slides from Luke:
  37 [email archive](https://lists.libre-soc.org/pipermail/libre-soc-dev/2023-December/005892.html)
  38
  39 Meeting notes:
  40
  41 * Outstanding Cavatools tasks:
  42   - [bug #980](https://bugs.libre-soc.org/show_bug.cgi?id=980)
  43 * Outstanding Cryptorouter tasks:
  44   - Poly1305, [bug #1157](https://bugs.libre-soc.org/show_bug.cgi?id=1157)
  45   [bug #1158](https://bugs.libre-soc.org/show_bug.cgi?id=1158),
  46   [bug #1159](https://bugs.libre-soc.org/show_bug.cgi?id=1159)
  47   - Ed25519,
  48   [bug #1151](https://bugs.libre-soc.org/show_bug.cgi?id=1151),
  49   [bug #1166](https://bugs.libre-soc.org/show_bug.cgi?id=1166),
  50   [bug #1167](https://bugs.libre-soc.org/show_bug.cgi?id=1167)
  51
  52 # Andrey
  53
  54 - Came back from holiday yesterday.
  55 - [Bug #1048](https://bugs.libre-soc.org/show_bug.cgi?id=1048),
  56   Cleaning up ls011 by using inline ld/st imports.
  57
  58 # Jacob
  59
  60 - so, not a whole lot of news from me, i fixed a
  61 extra-parenthesis-in-a-wrong-spot bug for dmitry and fixed a bug
  62 luke left, but didn't actually make any coding progress beyond
  63 that.
  64
  65 During call, walked with Sadoon through assembler:
  66
  67 ```
  68 summary: discussing how to best split into sub-word chunks
  69 for poly1305
  70 > tbh dsrd isn't better than other shifts here
  71 It did help with taking the shift remainders and stitching them together which shortened the code quite a bit
  72 Also considering doing sv.dsrd instead of two dsrd's since we already use setvl=2 here
  73 > sv.dsrd is 8 bytes, just like 2x dsrd
  74 But it's a good demo of setvl anyways
  75 > yeah, being a good demo doesn't mean there isn't a better demo
  76 The better demo is the mul/adds 😃
  77 > try using a different register than r0, the simulator may be treating that like (RA|0) and just using r0 in both iterations...
  78 ```
  79
  80 # Sadoon
  81
  82 * Working through Poly1305 assembler.
  83 * Poly1305, [bug #1157](https://bugs.libre-soc.org/show_bug.cgi?id=1157)
  84 * 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.
  85 * TODO: Make comments on bug #1157.
  86
  87 * After that, work with the team on presentations as well as my own
  88
  89 [[!tag meeting2024]]
  90 [[!tag meeting_sync_up]]
  91