March 2024 - Devel - lists.tockos.org

Call for Tock Meeting Agenda Items
by Hudson Ayers March 29, 2024

March 29, 2024

Please reply to this email with agenda items and +1s for tomorrow’s meeting

3 2

Call for Tock meeting agenda items
by Amit Levy March 22, 2024

March 22, 2024

Please reply with agenda items and +1s for tomorrow's meeting.

2 2

Call for Tock Meeting Agenda Items
by Hudson Ayers March 15, 2024

March 15, 2024

Please reply with agenda items and +1s for tomorrow's meeting. I propose: - tockbot checkin: how do people feel about it so far? - review count requirement for assigned PRs - Rundown of recent PRs waiting on their assignee: - https://github.com/tock/tock/pull/3910 - https://github.com/tock/tock/pull/3906

3 3

Tock meeting agenda 03/08
by Amit Levy March 8, 2024

March 8, 2024

March 8th, 12pm Eastern / 9am Pacific / 6pm CET Join the meeting: https://meetings.dialpad.com/room/tock/1vnk9r3e1b - Updates - Working Groups - Other - Kernel testing: https://github.com/tock/tock/pull/3873 - Any new comments/thoughts? - Two names have been proposed: boards/configuration and boards/variant - Revive Flash HIL work? - libtock-c: u8g2 library: https://github.com/tock/libtock-c/pull/363 - Used for monochromatic screens - TBF header parsing in the kernel: https://github.com/tock/tock/pull/3902 - Issue: the `TbfHeader` object is 368 bytes which makes it hard to pass on the stack. - This PR does some TLV parsing on demand, so the entire structure is not stored in memory.

1 0

Re: Call for Tock meeting agenda items
by Branden Ghena March 7, 2024

March 7, 2024

It would be good to at least discuss moving forward on https://github.com/tock/tock/pull/3822 * Do we want review assignments? (Yes from me) * What are the minimal features for it to start with? (we could add more later) On Thu, Feb 22, 2024 at 1:05 PM Brad Campbell <bradjc(a)virginia.edu> wrote: > Topics I would like to discuss for this week: > > - Digest HIL updates https://github.com/tock/tock/pull/3866 > <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3866__;!!Dq0X…> > - Both digests and digest implementations are now strongly > templated on a particular algorithm, rather than just the length of the > resulting digest. > - This is motivated by being able to strongly type cryptographic > signatures to a particular digest type. > - Kernel testing > - RFC: "Configuration" boards. These would be "mini" boards with > enough functionality to test different configurations of the Tock kernel. > https://github.com/tock/tock/pull/3873 > <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3873__;!!Dq0X…> > - Trait to wrap capsule tests: > https://github.com/tock/tock/pull/3871 > <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3871__;!!Dq0X…>. > This allows the test runner to learn when a test has finished, since the > test might run many async calls. > - Static mut and updating nightly > - We currently cannot compile the kernel on the latest nightly: > https://github.com/tock/tock/issues/3841 > <https://urldefense.com/v3/__https://github.com/tock/tock/issues/3841__;!!Dq…> > - We don't want to get stuck on an old version of rust, and it > seems like rust wants us to tackle this problem now. > - Is anyone willing to develop a "SyncCell" (or whatever the > correct name is)? I propose we put a time bound on this, and use the > rust-suggested "fix" if we don't have anything better so we can update > nightly. > - PRs > - https://github.com/tock/tock/pull/3855 > <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3855__;!!Dq0X…> > - https://github.com/tock/tock/pull/3859 > <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3859__;!!Dq0X…> > - https://github.com/tock/tock/pull/3843 > <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3843__;!!Dq0X…> > - https://github.com/tock/tock/pull/3869 > <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3869__;!!Dq0X…> > - https://github.com/tock/tock/pull/3860 > <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3860__;!!Dq0X…> > > > On Fri, Feb 16, 2024 at 9:28 AM Brad Campbell <bradjc(a)virginia.edu> wrote: > >> Unfortunately I have to leave at half past today. >> >> >> - https://github.com/tock/tock/pull/3849 >> <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3849__;!!Dq0X…> >> - Async process loader >> - How to get PRs commented on or merged? >> - https://github.com/tock/tock/pull/3817 >> <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3817__;!!Dq0X…> >> - https://github.com/tock/tock/pull/3836 >> <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3836__;!!Dq0X…> >> - https://github.com/tock/tock/pull/3843 >> <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3843__;!!Dq0X…> >> - https://github.com/tock/tock/pull/3846 >> <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3846__;!!Dq0X…> >> - Looking for ideas here...do we need a new review process? All >> core members are supposed to comment within 7 days. >> - My forever quest to start supporting signed processes: >> https://github.com/tock/tock/pull/3772 >> <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3772__;!!Dq0X…> >> :( >> - libtock-c refactor proposal >> - >> https://github.com/tock/libtock-c/blob/libtock-folders/doc/guide.md >> <https://urldefense.com/v3/__https://github.com/tock/libtock-c/blob/libtock-…> >> - libtock-c >> - Don't compile extern libraries with -Werror: >> https://github.com/tock/libtock-c/pull/368 >> <https://urldefense.com/v3/__https://github.com/tock/libtock-c/pull/368__;!!…> >> >> >> On Fri, Feb 9, 2024 at 9:21 AM Brad Campbell <bradjc(a)virginia.edu> wrote: >> >>> Ideas for today: >>> >>> >>> - Stable Rust - https://github.com/tock/tock/pull/3802 >>> <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3802__;!!Dq0X…> >>> - Signature HIL - https://github.com/tock/tock/pull/3772 >>> <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3772__;!!Dq0X…> >>> - libtock-c refresh - How to make it more user friendly? >>> - What types of changes would make libtock-c easier to use? Where >>> are the pain points? >>> - Do we need yield-wait-for-x? >>> - Should we copy some existing interface? >>> - We probably aren't going to be able to do an entire rewrite, >>> but are there manageable steps that would make a difference? >>> >>> >>> On Fri, Feb 2, 2024 at 11:24 AM Brad Campbell <bradjc(a)virginia.edu> >>> wrote: >>> >>>> >>>> - Process Checking Infrastructure PRs >>>> - https://github.com/tock/tock/pull/3772 >>>> <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3772__;!!Dq0X…> >>>> - https://github.com/tock/tock/pull/3818 >>>> <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3818__;!!Dq0X…> >>>> - Remove a nightly feature >>>> - https://github.com/tock/tock/pull/3803 >>>> <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3803__;!!Dq0X…> >>>> - Finalize Legal TRD >>>> - https://github.com/tock/tock/pull/3821 >>>> <https://urldefense.com/v3/__https://github.com/tock/tock/pull/3821__;!!Dq0X…> >>>> >>>> >>>> On Fri, Feb 2, 2024 at 11:07 AM Amit Levy <amit(a)amitlevy.com> wrote: >>>> >>>>> Please reply with agenda items and +1s for today's meeting. >>>>> >>>>> Hudson is away today, so I'll be leading, hence the later than usual >>>>> request for agenda items. Luckily I think there are plenty. I suggest at >>>>> least: >>>>> >>>>> - Brad's suggestion for a new documentation working group (there is >>>>> already approval for this, but we can maybe discuss whether/how to support >>>>> this kind of process more generally. could be very brief) >>>>> _______________________________________________ >>>>> Devel mailing list -- devel(a)lists.tockos.org >>>>> To unsubscribe send an email to devel-leave(a)lists.tockos.org >>>>> >>>>

3 3