Developer Meeting Agenda 2026-09-27 - 20:00 CEST #4566
grandixximo
started this conversation in
Agenda
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
According to our bi-weekly schedule alternating between "early" and "late", this video meeting is next Sunday 2026-Sep-27 at 20:00 CEST.
https://greenlight.bbb.uni-rostock.de/b/ste-c4d-brs-3k6
Access code: 869782
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2026&month=9&day=27&hour=18&min=0&sec=0&p1=319&p2=236&p3=240&p4=136&p5=165&p6=256
I will not be able to attend this one. Anything on my PRs can go in the PR threads and I will pick it up the next day. Please write the conclusions into this agenda as usual.
Agenda
hal: Break the HAL API - Move to 64-bit exclusively #4565 HAL API break, 64-bit only. The big one from the plan agreed last meeting (item 4 of Developer Meeting Agenda 2026-09-13 - 10:00 CEST #4497). First review round done Sep 19, all points fixed on the branch. Points to settle:
~pre2version bump and tag. @BsAtHome holds the bump for the docs PR and wants to tag the tree once all the changes are in, so the CI packages carry the right version. Agree on the tag point.halfileupdate) is draft until the renaming is settled, which hal: Break the HAL API - Move to 64-bit exclusively #4565 settles. Same for hal: Add halcompupdate to migrate .comp files to the new HAL API #4256 (halcompupdate). Do we want these in before or right after the break so users are not left without a converter?.mbccbfiles need recompiling from.mbccsafter the break; where do we tell users (release notes, NEWS, docs)?hal_[gs]et_[us]i32()remain, the tree is not 64-bit clean yet. That is the third phase from last meeting; who takes which components?Signed vs unsigned integers in HAL, discussion The unsigned integer question #4526. Follow-up to the question from @rene-dev. The in-tree evidence is in the discussion; do we keep both
sintanduintor fold to one?Branch protection, discussion Branch Protection #4558. "Require branches to be up to date" was turned off again. Do we make
rip-and-test(or more) a hard requirement, or keep CI as a strong signal with an escape hatch for infrastructure flakes?Include layout, include: use angle brackets for exported headers, and check it #4375 and include: move the exported headers into a directory of their own #4461. Last meeting decided to move all includes after the 64-bit migration. Confirm the order: hal: Break the HAL API - Move to 64-bit exclusively #4565 first, then include: move the exported headers into a directory of their own #4461, then the angle-bracket check include: use angle brackets for exported headers, and check it #4375.
Wayland. gremlin: host the GTK preview on Gtk.GLArea without GLX #4538 hosts the GTK gremlin on
Gtk.GLAreawithout the GLX dlopen hack; @alex-pres reports pncconf and gremlin run on Weston with it, which makes Wayland fix (namely pncconf's sample panel) #4523 unnecessary. The remaining X11-only pieces are GtkSocket in gmoccapy and everything Tk. Do we want a tracking issue for native Wayland?hostmot2 driver fixes, fix safety and correctness bugs in hostmot2 drivers #4488 by @sleepybishop. @BsAtHome asked for a split (sserial and abs_encoder need hardware testing, pktuart/eth can go in a first batch). The author is waiting for guidance on how to split. Can we give a concrete list?
PRs
See PRs for merge/comments.
initf hm2_eth.realtime-initno longer needed. Two-board case untested. hm2_eth: Create support library's #4498 (hm2_eth support libraries) is the design discussion with @BsAtHome about exporting the API from the existing posix/xenomai libraries instead of new .so files.os._exit()concern addressed, timer gone. Ready to merge.use_localizationput back after @BsAtHome's comment.ini parser identifiers vs the xhc-hb04 pendant, inifile: accept dash in section and variable identifiers #4573. The new ini parser restricts identifiers to letters, digits and underscore; that broke the xhc-hb04 sample configs (dashed
[XHC_HB04_BUTTONS]keys likestart-pause) and the pendant comp's own layout cfg files ([XHC-HB04]section). @BsAtHome: dropping the dash was intentional, the pendant was missed. Options: accept the dash again (inifile: accept dash in section and variable identifiers #4573 restores the old behavior, currently draft), or deliberately rename all pendant identifiers to underscores with migration coverage for INI keys, layout cfg files and HAL pin names (xhc-hb04.button-start-pause), in line with the other 2.10 breaks (hal: Break the HAL API - Move to 64-bit exclusively #4565). Decide direction.All reactions