|
Description
Luke Kenneth Casson Leighton
2021-02-06 14:32:23 GMT
MAX5834 MAX2830 https://www.reddit.com/r/programming/comments/p0yn45/three_fundamental_flaws_of_simd/h9xhj4k/?utm_source=reddit&utm_medium=web2x&context=3 Draft instructions partially designed: https://libre-soc.org/openpower/sv/bitmanip/ i've added a TODO/preliminary top-level milestone for documentation of sky130 and coriolis2, amount TBD. fortunately as this is an "approved" task, work can go ahead even though the exact MoU has not been agreed yet, and budget will be available once tasks are agreed. I filled out the description and guessed budgets for the tasks here. Appended to the end of the top comment: https://bugs.libre-soc.org/show_bug.cgi?id=589#c0 The task list is shorter than I expected (half of the original tasks were apparently moved to NGI POINTER assuming I'm guessing correctly), so imho the budgets may end up somewhat inflated as a result of trying to split 50000 between them...particularly the algorithm demos one...though I could be wrong. (In reply to Jacob Lifshay from comment #5) > I filled out the description and guessed budgets for the tasks here. > Appended to the end of the top comment: > https://bugs.libre-soc.org/show_bug.cgi?id=589#c0 brilliant. i took off the moved tasks > The task list is shorter than I expected (half of the original tasks were > apparently moved to NGI POINTER assuming I'm guessing correctly), yes. > so imho > the budgets may end up somewhat inflated as a result of trying to split > 50000 between them...particularly the algorithm demos one...though I could > be wrong. we can compensate by adding 3 new tasks, FPGAs Management and Documentation. should do the trick. added the suggested tasks, and rebalanced the budgets. looks good? (In reply to Luke Kenneth Casson Leighton from comment #6) > brilliant. i took off the moved tasks the moved tasks need to be removed from this bug's Depends On list. hilariousness. all good except "useless" bit :) both Michiel and EU Auditors will be reading the milestones, try rewording with a positive spin even if it's blindingly obvious amd bordering on "filler" words. length is fine, positive or neutral is best (In reply to Luke Kenneth Casson Leighton from comment #9) > hilariousness. all good except "useless" bit :) rephrased: # Documentation of designs, code, processes, and other relevant things as needed In order to make it more likely for our project to be understandable and useful, documentation of designs, code, processes, and other relevant things is necessary. moved subtasks (that were moved to ngi pointer) to See Also, rather than Depends On list. (In reply to Jacob Lifshay from comment #10) > In order to make it more likely for our project to be understandable and > useful, > documentation of designs, code, processes, and other relevant things is > necessary. perfect. extra bonus points for including bureaucratic phrases like "promoting outcomes" although that would need conferences or press releases and blogs and blech realistically it is a new milestone and i think we're good. next part literally cutpaste create bugreports, 1st line in title, para as comment0, then edit *this* comment 0 to include full URL. full because the text will be dropped verbatim as Schedule A into MoU (In reply to Luke Kenneth Casson Leighton from comment #12) > next part literally cutpaste create bugreports, 1st line in title, para > as comment0, then edit *this* comment 0 to include full URL. > full because the text will be dropped verbatim as Schedule A into MoU submitted all the bugs and added links. https://it.slashdot.org/story/23/02/08/2239210/us-nist-unveils-winning-encryption-algorithm-for-iot-data-protection this algorithm has become a high-priority for investigation and research, replacing one of the other algorithms formerly selected when the status of this algorithm was not known at the time. https://code.vt.edu/joyuliao/pyascon/-/blob/master/ascon.py#L283 https://github.com/ascon/crypto_aead/blob/master/ascon128v12/ref/ascon.c#L49 (In reply to Luke Kenneth Casson Leighton from comment #14) > https://it.slashdot.org/story/23/02/08/2239210/us-nist-unveils-winning- > encryption-algorithm-for-iot-data-protection > > this algorithm has become a high-priority for investigation and > research, replacing one of the other algorithms formerly selected > when the status of this algorithm was not known at the time. Ok, it will be one of the algorithms I'll prioritise to include for research and test demonstration. > > https://code.vt.edu/joyuliao/pyascon/-/blob/master/ascon.py#L283 Copied, tests seem to run fine. > https://github.com/ascon/crypto_aead/blob/master/ascon128v12/ref/ascon.c#L49 This repo has been deprecated, has been replaced by this one: https://github.com/ascon/ascon-c However the original ascon.c file seems to have been replaced with https://github.com/ascon/ascon-c/blob/main/crypto_aead/ascon128v12/ref/aead.c I copied both repos (crypto_aead and ascon-c), just in case. Will start looking into more next week (still reading on RSA and running ref code for this week). the MoU Schedule A now has the OPF ISA WG taskspartly duplicated here, must sort that out. |