1 # Tuesday 16th January 17:00 UTC
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]]
9 * reminder of **only 5 weeks** until march 1st deadline
10 for completion of cavatools and cryptoprimitives.
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:
16 * Due to length, moved to separate discussion page:
17 [[discussion/sync_up_2024-01-16_discussion]]
19 After meeting discussion, points agreed upon will be documented
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)
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)
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)
54 - [bug #980](https://bugs.libre-soc.org/show_bug.cgi?id=980)
55 - Still some work required. A few days until
56 - Two types of pseudocode: instructions, python functions
57 - For now provides prototypes for many features
61 - [bug #1157](https://bugs.libre-soc.org/show_bug.cgi?id=1157)
62 - walkthrough code during meeting.
64 Jacob provided great help:
67 maddedu would be useful if you have a packed 130 bit number
68 in words where the non-msb words have 64-bits per word, the
69 code you had last i checked instead has 44-bits per register used
71 this is the pattern used by the x + y remap mode...which
72 isn't working yet, so svindex is suitable for now
74 maddedu also has carry-out, which you don't have here
75 so maddld is sufficient
77 or the x + y remap once that's implemented
78 setup shapes with svindex insn
79 no, those are offset by the register specified in the sv. insn
80 that remap is applied to
82 svindex has element numbers, not x,y,z
83 x,y,z are used for other remap modes
84 yes, use the svindex insn
85 you specify the vector to load element numbers from in the svindex insn
86 but they're accessed with element-sized chunks with element size
89 svindex is if you want only one sv.maddld insn that loops 9 times
90 lemme move to my desktop so i can type easier...
91 ok, so you'll want a mod-3 matrix remap in one SVSHAPE register,
92 and svindex remap in another SVSHAPE register
94 so run svshape to set the matrix remap, then run svindex
95 to overwrite one remap...
97 svshape writes all 4 SVSHAPE registers, svindex can set the SVSHAPE
100 (or all 4, but you don't want that mode)
101 so test_1_sv_index is an example of what you want...
103 encoded in the LSB 2 bits of the operand that's 14
105 see comments immediately above
106 see line 396 of simplev.mdwn for how rmm is used
108 * **SVG** - GPR SVG<<2 to be used for Indexing
109 so if you want the indexes to be in r4,r5,r6... set SVG to 1 which
110 comes out to r4 (1 << 2)
112 yes, a value of zero means use element 0
113 so, if you want remap to use elements 1,2,3,4,5,6,7,8 set the first
114 register to 0x0807060504030201 and use byte elwid
115 the svindex elwid, not the sv.insn elwid, they're independent
116 svremap tells the following sv.insn which SVSHAPE[0-3]
117 register to use for each operand
119 you don't want to set the SVSHAPE register directly, instead put the
120 indexes in GPRs and svindex insn sets SVSHAPE to point to those GPRs
122 ok, so if your indexes are in r4,r5 with byte elements, afaict you
123 want svindex 1, 1, 9, 3, 0, 1, 0 which sets byte mode, sets SVSHAPE1
129 - Recovering from a cold (worst of it already happened on the weekend,
130 now mostly blocked nose).
131 - [Bug #1048](https://bugs.libre-soc.org/show_bug.cgi?id=1048),
132 Luke and Jacob made comments regarding the summary, I'll work on it
134 - Checked that RfP for Red was paid, so added extra commentary on IRC
135 (continued from walkthrough Luke and I did last month).
136 - [[HDL_workflow/rfp_submission_guide]]
138 [IRC messages](https://libre-soc.org/irclog/latest.log.html#t2024-01-15T17:58:17)
139 - Created a discussion page for the "git commit frequency" topic that
140 came up last week: [[discussion/sync_up_2024-01-16_discussion]].
142 [IRC](https://libre-soc.org/irclog/latest.log.html#t2024-01-15T19:05:24)
144 - Change my main email from technepisteme.xyz to the gmail one.
145 - Redo the calendar invites for the sync-up meetings.
149 - suggested that presentations should be submitted much closer to fosdem (few days), since 2 weeks is too early. I will not be ready by 2 weeks before.
150 - (didn't actually get around to during meeting:) not a whole lot, will start working on presentation, helped resolve issue with luke & dmitry, fixed some bugs for dmitry.
154 * Working through Poly1305 assembler.
155 * Poly1305, [bug #1157](https://bugs.libre-soc.org/show_bug.cgi?id=1157)
156 * 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.
157 * TODO: Make comments on bug #1157.
159 * After that, work with the team on presentations as well as my own
162 [[!tag meeting_sync_up]]