2025-04-22.log

+ arminweigl_ (~arminweig@sourcehut/user/arminweigl)01:14
- arminweigl (QUIT: Ping timeout: 244 seconds) (~arminweig@sourcehut/user/arminweigl)01:14
* arminweigl_ -> arminweigl01:14
+ Gooberpatrol_66 (~Gooberpat@user/gooberpatrol66)01:59
- paperManu (QUIT: Ping timeout: 260 seconds) (~paperManu@172.93.30.55)02:42
- kop316 (QUIT: Remote host closed the connection) (m-6f6zq6@static.138.159.90.157.clients.your-server.de)03:56
+ kop316 (m-6f6zq6@static.138.159.90.157.clients.your-server.de)03:59
- kop316 (QUIT: Remote host closed the connection) (m-6f6zq6@static.138.159.90.157.clients.your-server.de)04:04
+ kop316 (m-6f6zq6@static.138.159.90.157.clients.your-server.de)04:05
- kop316 (QUIT: Remote host closed the connection) (m-6f6zq6@static.138.159.90.157.clients.your-server.de)04:06
+ kop316 (m-6f6zq6@static.138.159.90.157.clients.your-server.de)04:06
- Ar|stote|is (QUIT: Ping timeout: 272 seconds) (~linx@149.210.9.164)04:29
+ Ar|stote|is (~linx@149.210.8.70)04:34
- ZetaR (PART: !!unknown attribute: msg!!) (~user@c-98-58-7-138.hsd1.fl.comcast.net)06:04
+ arminweigl_ (~arminweig@sourcehut/user/arminweigl)10:25
- arminweigl (QUIT: Ping timeout: 276 seconds) (~arminweig@sourcehut/user/arminweigl)10:25
* arminweigl_ -> arminweigl10:25
- gsora (QUIT: Read error: Connection reset by peer) (~gsora@user/gsora)10:34
- jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net)11:04
+ jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net)11:05
- mjw (QUIT: Ping timeout: 268 seconds) (~mjw@gnu.wildebeest.org)11:34
- L29Ah (PART: !!unknown attribute: msg!!) (~L29Ah@wikipedia/L29Ah)12:03
+ mjw (~mjw@gnu.wildebeest.org)12:14
+ L29Ah (~L29Ah@wikipedia/L29Ah)12:16
- L29Ah (PART: !!unknown attribute: msg!!) (~L29Ah@wikipedia/L29Ah)12:26
+ L29Ah (~L29Ah@wikipedia/L29Ah)12:26
- mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org)12:28
+ paperManu (~paperManu@172.93.30.55)12:43
- murphnj (QUIT: Quit: Leaving) (~murph@user/murphnj)12:46
+ gustav28 (~gustav@c-78-82-52-114.bbcust.telenor.se)13:02
sevanwith submitting pull requests on mnt repos, what's the thinking behind hardware requirement for tags? as long as a contribution succeeds in building, that should be sufficient (contributor is not looking to cut a releases)13:17
sevans/hardware/hard13:17
* Guest7078 -> mjw13:39
minutesevan: tags are mostly done for releases13:56
minutealthough firmware release mgmt is severely lacking, mea culpa13:56
- wickedshell (QUIT: Ping timeout: 276 seconds) (~wickedshe@2601:8c0:800:a1c1:ad46:75c:319e:fe3b)14:00
sevanminute: no worries about new releases. Just picking up from a few months ago and wondering why a contributor has to tag stuff for it to pass CI. Even though the proposed changed passes.14:03
sevan(I'm not cutting a new release)14:04
* se6astian_ -> se6astian15:17
- bkeys (QUIT: Ping timeout: 244 seconds) (~Thunderbi@173.186.16.211)15:33
gordon1https://litter.catbox.moe/4qpgt4.png in case of emergency <315:38
gordon1can i truly power it with 5V?15:38
+ bkeys (~Thunderbi@66.110.201.50)15:43
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@66.110.201.50)15:48
+ bkeys (~Thunderbi@66.110.201.50)15:48
- bkeys (QUIT: Client Quit) (~Thunderbi@66.110.201.50)15:50
+ bkeys (~Thunderbi@66.110.201.50)15:51
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@66.110.201.50)15:54
+ bkeys1 (~Thunderbi@66.110.201.50)15:54
sevanno worries, I wont mention the tagging stuff again.15:55
BoostisBetterBeing able to charge the pocket on a 5v dumb source would be a game changer as well. BUT not a super serious one. The pile of things for minute is already full. Just mentioning it because I would really like to see that at some point. 15:56
- bkeys1 (QUIT: Read error: Connection reset by peer) (~Thunderbi@66.110.201.50)15:56
+ bkeys (~Thunderbi@66.110.201.50)15:57
- bkeys (QUIT: Client Quit) (~Thunderbi@66.110.201.50)16:00
+ bkeys (~Thunderbi@66.110.201.50)16:00
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@66.110.201.50)16:06
+ bkeys1 (~Thunderbi@66.110.201.50)16:06
+ wickedshell (~wickedshe@2601:8c0:800:a1c1:ae5c:ef70:2d3c:30f3)16:06
* bkeys1 -> bkeys16:08
+ razzy (~razzy@user/razzy)16:09
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@66.110.201.50)16:11
+ bkeys (~Thunderbi@66.110.201.50)16:11
+ bkeys1 (~Thunderbi@66.110.201.50)16:14
- bkeys (QUIT: Client Quit) (~Thunderbi@66.110.201.50)16:14
* bkeys1 -> bkeys16:14
razzyhello, I am looking for how-to-manual how to use reform FPGA. did not find yet. I might gain value from FPGA. I am looking to try simulators first.16:15
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@66.110.201.50)16:19
+ bkeys (~Thunderbi@66.110.201.50)16:24
- bkeys (QUIT: Client Quit) (~Thunderbi@66.110.201.50)16:26
+ bkeys1 (~Thunderbi@66.110.201.50)16:27
* bkeys1 -> bkeys16:29
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@66.110.201.50)16:39
+ bkeys (~Thunderbi@66.110.201.50)16:39
- bkeys (QUIT: Client Quit) (~Thunderbi@66.110.201.50)16:44
+ bkeys1 (~Thunderbi@66.110.201.50)16:44
- bkeys1 (QUIT: Read error: Connection reset by peer) (~Thunderbi@66.110.201.50)16:46
+ bkeys (~Thunderbi@66.110.201.50)16:47
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@66.110.201.50)16:50
+ bkeys1 (~Thunderbi@66.110.201.50)16:50
razzyhmm found and reading litex16:52
* bkeys1 -> bkeys16:53
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@66.110.201.50)16:57
+ bkeys1 (~Thunderbi@66.110.201.50)16:57
* bkeys1 -> bkeys16:59
+ bkeys1 (~Thunderbi@38-146-94-247.echocast.zone)17:05
- bkeys (QUIT: Ping timeout: 248 seconds) (~Thunderbi@66.110.201.50)17:08
* bkeys1 -> bkeys17:08
+ bkeys1 (~Thunderbi@66.110.201.50)17:09
- bkeys (QUIT: Ping timeout: 248 seconds) (~Thunderbi@38-146-94-247.echocast.zone)17:12
+ bkeys (~Thunderbi@66.110.201.50)17:13
- bkeys1 (QUIT: Client Quit) (~Thunderbi@66.110.201.50)17:13
+ mark_ (~mjw@gnu.wildebeest.org)17:16
minutenow about to try the 6.13 build from the weekend.17:33
minuteslash easeter17:33
minuteeaster17:33
+ bkeys1 (~Thunderbi@38-146-94-247.echocast.zone)17:35
- bkeys (QUIT: Ping timeout: 245 seconds) (~Thunderbi@66.110.201.50)17:38
- bkeys1 (QUIT: Client Quit) (~Thunderbi@38-146-94-247.echocast.zone)17:38
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)17:38
- xha (QUIT: Quit: WeeChat 4.5.2) (~xha@user/xha)17:40
+ bkeys1 (~Thunderbi@66.110.201.50)17:51
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@38-146-94-247.echocast.zone)17:53
* bkeys1 -> bkeys17:53
- mark_ (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org)18:02
+ bkeys1 (~Thunderbi@66.110.201.50)18:09
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@66.110.201.50)18:09
* bkeys1 -> bkeys18:09
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@66.110.201.50)18:13
+ bkeys1 (~Thunderbi@66.110.201.50)18:13
- bkeys1 (QUIT: Read error: Connection reset by peer) (~Thunderbi@66.110.201.50)18:15
+ bkeys (~Thunderbi@66.110.201.50)18:15
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@66.110.201.50)18:19
+ bkeys (~Thunderbi@173.186.16.211)18:39
minutestrange, this linux config change had no effect somehow https://source.mnt.re/mntmn/reform-debian-packages/-/commit/7d86d5c6687c8e6095e61dd21c7eeeb44fb09afd#5371c40c9806dc96e47a1597744488ec4c7cc5f0_87_8318:50
minuteunpacking the resulting deb and inspecting /boot/config...:18:54
minuteCONFIG_ROCKCHIP_DW_MIPI_DSI=y18:54
minute# CONFIG_ROCKCHIP_DW_MIPI_DSI2 is not set18:54
minutebuild-linux.sh has > cat config >> linux/debian/config/arm64/config18:55
minutesorry, linux/build.sh 18:57
minuteah hm:18:58
minutedebian/config/arm64/config: Invalid setting CONFIG_ROCKCHIP_DW_HDMI_QP=m18:58
minutedebian/config/arm64/config: Invalid setting CONFIG_ROCKCHIP_DW_MIPI_DSI2=m18:58
joschsevan: the CI is checking whether what you have as tags matches the information in the files and vice versa. You don't have to tag anything yourself -- just import the tags from the target branch.19:03
minuteah, probably these have to be =y19:03
sevanjosch: ok, but isn't that information just relevant for whoever is cutting a release? not for the person working on changes to functionality19:12
joschsevan: yes, i'd merge a patch which checks the right thing to avoid this check for MRs19:13
joschsevan: if you know more about gitlab than I, please feel free to craft a patch that fixes this :)19:13
sevanjosch: -_- oO(not sure if this is a trap)19:14
joschsevan: I don't understand -- why should it be a trap?19:18
sevanjosch: sorry, I was fooling around, what you basically said is "patches welcome" so if the functionality isn't behaving ideally, and it hasn't been fixed yet, perhaps it's a little arduious. Hence wondering if it's a trap :)19:21
+ gsora (~gsora@user/gsora)19:25
joschsevan: ah i see. I think it depends on how well you know your way around gitlab. You probably just have to check the right variable to figure out what is a MR and what is the thing in main that is about to become tagged as a release.19:32
joschthere are tons of variables with tiny differences to them19:32
+ mark_ (~mjw@gnu.wildebeest.org)19:35
- mjw (QUIT: Killed (tungsten.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c)19:36
* mark_ -> mjw19:36
+ Guest1904 (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c)19:36
+ xha (~xha@user/xha)19:48
- hairu (QUIT: Remote host closed the connection) (m-uotkmd@user/hairu)20:20
+ hairu (m-uotkmd@user/hairu)20:21
- hairu (QUIT: Remote host closed the connection) (m-uotkmd@user/hairu)20:22
+ hairu (m-uotkmd@user/hairu)20:25
- jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net)20:42
+ jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net)20:44
- gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-52-114.bbcust.telenor.se)21:04
+ gustav28 (~gustav@c-78-82-52-114.bbcust.telenor.se)21:04
minutejosch: FYI picotool in debian seems kind of outdated, doesn't have rp2350 support21:31
+ arminweigl_ (~arminweig@sourcehut/user/arminweigl)22:01
- arminweigl (QUIT: Ping timeout: 276 seconds) (~arminweig@sourcehut/user/arminweigl)22:02
* arminweigl_ -> arminweigl22:02
zeha2.x should have the rp2350 support iirc?22:09
- gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-52-114.bbcust.telenor.se)22:10
minutezeha: sdk yes, tool not22:19
minutehmm wait22:19
minuteit's possible that i had an old version in /usr/local/bin!22:20
zehajosch uploaded 2.1.1 in march, which is i think the latest version22:20
zehaheh22:20
minuteyes it is :D22:20
minutemy fault, sorry josch 22:20
zeha:)22:20
minutei can say that porting stuff to rp2350a is quite painless22:20
minute(so far)22:20
minutealso, my latest 6.13 ci build with rk3588-dsi dtb finally works, brings the display up on classic reform22:21
minutequite a successful day today22:27
josch\o/22:31
joschwe must only take care that pico-sdk does not get autoremoved before the release ;)22:33
zehanice. today was indeed a good day22:36
zehai look at the migration tracker every day ;)22:36
joschgood because the reform meta packages depend on so much stuff that there are right now even 5 RC bugs threatening its auto-removal in late May ;)22:38
josch(but i think those bugs are already being taken care of)22:38
zehayeah22:39
zehantpsec is a bit of a problem22:39
zehabut i hope that will be taken care of; not having an ntpd would suck22:39
zeha(... for more than just reform-tools)22:39
- robin (QUIT: Remote host closed the connection) (~robin@user/terpri)22:56
- L29Ah (PART: !!unknown attribute: msg!!) (~L29Ah@wikipedia/L29Ah)23:26
+ arminweigl_ (~arminweig@sourcehut/user/arminweigl)23:39
- arminweigl (QUIT: Ping timeout: 268 seconds) (~arminweig@sourcehut/user/arminweigl)23:40
* arminweigl_ -> arminweigl23:40
+ L29Ah (~L29Ah@wikipedia/L29Ah)23:47

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!