| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip | 06:53 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds) | 07:13 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 08:30 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 250 seconds) | 09:34 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 09:34 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip | 10:14 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds) | 10:22 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 245 seconds) | 10:40 | |
| *** prabhakalad <prabhakalad!~prabhakar@97e54365.skybroadband.com> has quit IRC (Read error: Connection reset by peer) | 11:03 | |
| *** prabhakalad <prabhakalad!~prabhakar@97e54365.skybroadband.com> has joined #cip | 11:15 | |
| *** masami <masami!~masami@FL1-125-195-92-229.tky.mesh.ad.jp> has joined #cip | 11:57 | |
| *** jki <jki!~jki@62.156.206.52> has joined #cip | 11:57 | |
| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip | 11:57 | |
| jki | hi all | 12:00 |
|---|---|---|
| uli | hello | 12:00 |
| masami | hi | 12:00 |
| pave1 | Hi! | 12:01 |
| patersonc | Hey | 12:01 |
| jki | ok, let's get started | 12:01 |
| jki | #startmeeting CIP IRC weekly meeting | 12:01 |
| collab-meetbot | Meeting started Thu Jan 22 12:01:51 2026 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 12:01 |
| collab-meetbot | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 12:01 |
| collab-meetbot | The meeting name has been set to 'cip_irc_weekly_meeting' | 12:01 |
| *** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 12:01 | |
| jki | #topic AI review | 12:01 |
| *** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 12:01 | |
| jki | list empty, once again | 12:02 |
| jki | 5 | 12:02 |
| jki | 4 | 12:02 |
| jki | 3 | 12:02 |
| jki | 2 | 12:02 |
| jki | 1 | 12:02 |
| jki | #topic Kernel maintenance updates | 12:02 |
| *** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 12:02 | |
| pave1 | It seems we have finally catched up with torrent of Renesas patches. | 12:02 |
| masami | This week reported 2 new CVEs and 6 updated CVEs. | 12:02 |
| jki | nobuhiro wrote: I am reviewing 6.12.66. | 12:02 |
| uli | i'm working on the next 4.19 | 12:02 |
| pave1 | Otherwise reviews: 6.1.66. | 12:03 |
| jki | anything to add? | 12:04 |
| jki | 5 | 12:04 |
| jki | 4 | 12:04 |
| jki | 3 | 12:04 |
| jki | 2 | 12:04 |
| jki | 1 | 12:04 |
| jki | #topic Kernel release status | 12:04 |
| *** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 12:04 | |
| pave1 | So.. we don't have a goot match for 6.1-rt. | 12:04 |
| jki | when would the next 6.1-rt appear, likely? | 12:04 |
| jki | did you ask? | 12:05 |
| pave1 | I asked rt maintainers for information. | 12:05 |
| jki | ok | 12:05 |
| jki | reply? | 12:05 |
| pave1 | I'm waiting for reply, don't ask _when_ I asked :-). | 12:05 |
| jki | ok :) | 12:05 |
| pave1 | But last release is at "Nov 10", so... hopefully one is near. | 12:06 |
| jki | indeed | 12:06 |
| jki | give another week, then discuss if own forward porting is possible | 12:06 |
| pave1 | yep. | 12:07 |
| jki | nobuhiro wrote he plans to release a 6.12 tomorrow | 12:07 |
| jki | ok | 12:07 |
| jki | other issues in sight? | 12:07 |
| jki | 5 | 12:08 |
| jki | 4 | 12:08 |
| jki | 3 | 12:08 |
| jki | 2 | 12:08 |
| jki | 1 | 12:08 |
| jki | #topic Kernel testing | 12:08 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 12:08 | |
| patersonc | No updates from me | 12:08 |
| arisut_ | same | 12:09 |
| jki | the mcom in Prague is getting closer to be online again | 12:09 |
| jki | likely early next week | 12:10 |
| patersonc | Great. Thanks | 12:10 |
| pave1 | Good, that will mean one less "fail" on testing. | 12:10 |
| jki | if there are no other testing topics... | 12:11 |
| jki | 5 | 12:11 |
| jki | 4 | 12:11 |
| jki | 3 | 12:11 |
| jki | 2 | 12:11 |
| jki | 1 | 12:11 |
| jki | #topic AOB | 12:11 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 12:11 | |
| pave1 | I'll be at FOSDEM at end of month, talking about cameras. | 12:11 |
| pave1 | Does anyone else plan FOSDEM? | 12:11 |
| jki | yep, will be there as well | 12:11 |
| jki | my colleague do the work (talking) :) | 12:12 |
| jki | (unified kernel ftrace + lttng-us) | 12:12 |
| pave1 | Nice! | 12:13 |
| jki | pavel: we can meet, just drop me a note, or we see us in the embedded track ;) | 12:13 |
| patersonc | I have a question about linux-stable-rt. I noticed this week there is a v6.12 branch. Are we monitoring this for patches to integrate into 6.12-cip? | 12:13 |
| jki | do my understanding: no. those are out-of-tree /wrt 6.12 mainline | 12:14 |
| pave1 | jki: Yes, I guess it will somehow work out :-). | 12:14 |
| pave1 | patersonc: realtime was merged into mainline in 6.12. | 12:14 |
| jki | the 6.12-rt branch contains rt bits not in 6.12 stable, and we only track stable /wrt rt so far | 12:15 |
| jki | and we have no backports of further rt patches from newer upstream kernels yet | 12:15 |
| jki | once that should change, monitoring stable trees might become useful | 12:15 |
| pave1 | So we don't have separate -cip-rt branch, and we don't monitor 6.12-rt branch ... as those are features, not bugfixes. | 12:15 |
| patersonc | okay | 12:15 |
| patersonc | It looks like they added arm32 support | 12:16 |
| jki | into updstream now as well? | 12:16 |
| patersonc | Into that 6.12 branch | 12:16 |
| jki | in 6.12-rt for sure | 12:16 |
| jki | we are waiting for upstream arm32-rt, then we could backport to 6.12-cip | 12:17 |
| pave1 | So siemens is still interested in arm32? | 12:17 |
| jki | sure | 12:17 |
| jki | and not only us | 12:17 |
| pave1 | Be warned that there are powerful forces trying to get rid of everything 32bit. | 12:17 |
| jki | TI, I guess Renesas as well | 12:17 |
| jki | pavel: we sat in the same talk, and the message was clear: not in the next decade | 12:18 |
| pave1 | :-) | 12:18 |
| jki | hw is still being produced, though not really new one | 12:18 |
| pave1 | Well, I guess those powerful forces really hate HIGHMEM. | 12:19 |
| pave1 | Avoid HIGHMEM and you could be ok. | 12:19 |
| jki | right | 12:19 |
| jki | think Arnd has this on the radar and will communicate plans / ask for further feedback | 12:20 |
| jki | any other business for today? | 12:22 |
| jki | 5 | 12:23 |
| jki | 4 | 12:23 |
| jki | 3 | 12:23 |
| jki | 2 | 12:23 |
| jki | 1 | 12:23 |
| jki | #endmeeting | 12:23 |
| collab-meetbot | Meeting ended Thu Jan 22 12:23:23 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 12:23 |
| collab-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/01/cip.2026-01-22-12.01.html | 12:23 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/01/cip.2026-01-22-12.01.txt | 12:23 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/01/cip.2026-01-22-12.01.log.html | 12:23 |
| *** collab-meetbot changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 13:00 UTC | Find the meeting logs at https://ircbot.wl.linuxfoundation.org/meetings/cip/ and chat logs at https://ircbot.wl.linuxfoundation.org/logs/%23cip/" | 12:23 | |
| jki | thanks all! | 12:23 |
| uli | thanks | 12:23 |
| pave1 | Thank you! | 12:23 |
| masami | thank you | 12:23 |
| *** masami <masami!~masami@FL1-125-195-92-229.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 12:23 | |
| patersonc | Cheers | 12:23 |
| *** jki <jki!~jki@62.156.206.52> has quit IRC (Quit: Leaving) | 12:24 | |
| arnd | pave1, prabhakalad, patersonc, uli: I am currently working on a patch that should allow 2GiB lowmem on platforms with discontiguous RAM like the RZ/G1H. I thought this one as one of the reference platforms for CIP, but it seems I confused it with the G1M board that does not need my patch. Are any of you able to test my patch on a G1H board with 2GiB? | 12:50 |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 12:54 | |
| patersonc | arnd: Yes we (prabhakarlad) can test on RZ/G1H and would be happy to help | 13:00 |
| arnd | thanks patersonc, I'll Cc you both when I have a public version. I had it working previously but am back to debugging after a failed attempt to clean up my patch for submission. | 13:03 |
| arnd | Can you confirm that the memory on your board is indeed discontiguous? IIRC this SoC has the two memory controllers at fixed addresses, with the second one being above 0x1.0000.0000, but I can't find a reference in the manual for that any more. If the DRAM is in one chunk, my patch would not be needed on this hardware | 13:04 |
| patersonc | arnd: Let me brush the dust off the old manuals :) | 13:06 |
| pave1 | arnd: Hi! | 13:14 |
| pave1 | arnd: I don't know that much about renesas stuff, sorry. | 13:15 |
| patersonc | arnd: Yes - the DDR on the RZ/G1H iwg21m board is discontiguous. | 13:53 |
| patersonc | DDR0 is mapped to 0x01_0000_0000, however it is mirrored to 0x4000_0000 for 32-bit access. | 13:53 |
| patersonc | DDR1 is at 0x02_0000_0000. | 13:53 |
| patersonc | RZ/G1H iwg21m has 1GB @ 0x01_0000_0000/0x4000_0000 and 1GB @ 0x02_0000_0000. | 13:53 |
| patersonc | RZ/G1M iwg20m has 512MB @ 0x01_0000_0000/0x4000_0000 and 512MB @ 0x02_0000_0000. | 13:53 |
| patersonc | Memory maps for reference are available here: https://gist.github.com/prabhakarlad/a3e217a54fd7c747980f1bc7a4ba3a13 | 13:53 |
| arnd | patersonc: ok, thanks so much for looking that up. So my patch is indeed required to run G1H and G1M with CONFIG_HIGHMEM disabled | 13:55 |
| patersonc | arnd: Tep. Thank you for working on it :) | 13:55 |
| patersonc | *Yep | 13:55 |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 255 seconds) | 14:10 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 14:11 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection) | 16:10 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 16:10 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 246 seconds) | 16:26 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 16:27 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 244 seconds) | 18:24 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 18:24 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection) | 22:19 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!