2025-06-14.log

+ vkoskiv (~vkoskiv@109-204-186-7.cust.valoonet.fi)00:11
- mjw (QUIT: Quit: zzz) (~mjw@gnu.wildebeest.org)00:16
+ gachikuku (~gachikuku@kamil.gr)00:24
- chomwitt (QUIT: Quit: WeeChat 3.8) (~chomwitt@2a02:85f:9a08:a800:1ac0:4dff:fedb:a3f1)01:07
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)01:27
+ potash5 (~potash@user/foghorn)01:33
- potash (QUIT: Ping timeout: 248 seconds) (~potash@user/foghorn)01:33
* potash5 -> potash01:37
- potash (QUIT: Quit: Ping timeout (120 seconds)) (~potash@user/foghorn)01:42
+ potash (~potash@user/foghorn)01:42
joschbkeys: you can list the blobs in the efi file using: objdump -h /boot/EFI/BOOT/bootaa64.efi02:12
joschbkeys: you can extract sections using: objcopy -O binary -j.cmdline /boot/EFI/BOOT/bootaa64.efi /tmp/outfile02:12
joschthe section for the device tree is called .dtb02:13
joschit should look like this: https://paste.debian.net/1379605/02:13
- Gooberpatrol66 (QUIT: Quit: Konversation terminated!) (~Gooberpat@user/gooberpatrol66)02:41
bkeysjosch: Yeah, but what I'm finding now is that Fedora Rawhide actually has the reform device tree files in it; but it still doesn't boot for some mysterious reason03:02
- nsc (QUIT: Ping timeout: 265 seconds) (~nicolas@43-98-142-46.pool.kielnet.net)03:12
+ nsc (~nicolas@i5C74DCC1.versanet.de)03:14
joschbkeys: i'll have something new for you to try tomorrow03:16
joschit's 3:00 AM over here so in around 6 hours :)03:16
bkeysAlright no problem, I know Fedora isn't your issue, but it'd be nice for me to have it03:16
joschfor me, this is not about fedora at all03:16
joschbut to create an image that edk2 can boot :)03:17
bkeysYes I'm totally fine with testing that, I'm trying to get the Fedora ARM maintainer to debug this with me but he's an australian I'm pretty sure03:17
bkeysI'm fine to test for you tomorrow though03:17
joschnice, thank you!03:18
- paperManu_ (QUIT: Ping timeout: 244 seconds) (~paperManu@72.10.128.164)03:39
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)04:24
- nsc (QUIT: Ping timeout: 244 seconds) (~nicolas@i5C74DCC1.versanet.de)05:02
+ nsc (~nicolas@19-96-142-46.pool.kielnet.net)05:04
- wiedi (QUIT: Read error: Connection reset by peer) (~wiedi@ip5f581498.dynamic.kabel-deutschland.de)05:06
- RandyK (QUIT: Remote host closed the connection) (~RandyK@user/randyk)06:12
+ RandyK (~RandyK@user/randyk)06:13
- aloo_shu (QUIT: Ping timeout: 272 seconds) (~aloo_shu@90.166.193.10)07:06
+ aloo_shu (~aloo_shu@90.166.98.218)07:09
+ gustav28 (~gustav@c-78-82-55-148.bbcust.telenor.se)08:22
joschbkeys: new day new image: https://source.mnt.re/reform/reform-system-image/-/jobs/10908/artifacts/raw/pocket-reform-system-rk3588.img.gz08:48
joschi verified that this one has the rk3588 pocket reform device tree in the .dtb section of /boot/EFI/BOOT/bootaa64.efi08:49
+ wiedi (~wiedi@95.88.20.152)09:31
minutejosch: bkeys has a classic reform i think10:16
minute(or am i mistaken?)10:16
+ robin_ (~robin@user/terpri)10:24
+ cobra_ (~cobra@user/Cobra)10:25
+ Gooberpatrol_66 (~Gooberpat@user/gooberpatrol66)10:26
- aakast (QUIT: Ping timeout: 260 seconds) (~aakast@87-49-44-126-mobile.dk.customer.tdc.net)10:27
- BoostisBetter (QUIT: Ping timeout: 260 seconds) (4a410829d7@irc.cheogram.com)10:27
- cobra (QUIT: Ping timeout: 260 seconds) (~cobra@user/Cobra)10:27
- SavagePeanut (QUIT: Ping timeout: 260 seconds) (59eaa45ac7@irc.cheogram.com)10:27
- wiedi (QUIT: Ping timeout: 260 seconds) (~wiedi@95.88.20.152)10:27
- Gooberpatrol66 (QUIT: Ping timeout: 260 seconds) (~Gooberpat@user/gooberpatrol66)10:27
- vkoskiv (QUIT: Ping timeout: 260 seconds) (~vkoskiv@109-204-186-7.cust.valoonet.fi)10:27
- xha (QUIT: Ping timeout: 260 seconds) (~xha@user/xha)10:27
- Ar|stote|is (QUIT: Ping timeout: 260 seconds) (~linx@149.210.5.33)10:27
- chrcav (QUIT: Ping timeout: 260 seconds) (~chrcav@user/chrcav)10:27
- lanodan (QUIT: Ping timeout: 260 seconds) (~lanodan@2a01:e0a:d6:9930::35)10:27
- robin (QUIT: Ping timeout: 260 seconds) (~robin@user/terpri)10:27
+ chrcav (~chrcav@user/chrcav)10:28
+ lanodan (~lanodan@2a01:e0a:d6:9930::35)10:28
+ vkoskiv (~vkoskiv@109-204-186-7.cust.valoonet.fi)10:28
+ xha (~xha@user/xha)10:29
+ Ar|stote|is (~linx@149.210.5.33)10:31
+ wiedi (~wiedi@ip5f581498.dynamic.kabel-deutschland.de)10:34
+ BoostisBetter (4a410829d7@irc.cheogram.com)10:45
- BoostisBetter (QUIT: Ping timeout: 260 seconds) (4a410829d7@irc.cheogram.com)11:00
- vkoskiv (QUIT: Ping timeout: 260 seconds) (~vkoskiv@109-204-186-7.cust.valoonet.fi)11:00
+ vkoskiv (~vkoskiv@109-204-186-7.cust.valoonet.fi)11:00
+ BoostisBetter (4a410829d7@irc.cheogram.com)11:15
+ mjw (~mjw@gnu.wildebeest.org)11:29
- gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-55-148.bbcust.telenor.se)11:35
+ aakast (~aakast@80-62-116-40-mobile.dk.customer.tdc.net)12:00
joschminute: sorry you are right! I am maintaining a list of which IRC user has which device because I regularly get confused and I still had bkeys listed with A311D classic reform but irc history indeed says rk3588 classic reform.12:03
joschbkeys: then it's this one: https://source.mnt.re/reform/reform-system-image/-/jobs/10908/artifacts/raw/reform-system-rk3588.img.gz12:04
joschunless you need the dsi variant XD12:04
+ Core1951 (~aakast@80-62-116-34-mobile.dk.customer.tdc.net)12:16
+ chomwitt (~chomwitt@2a02:85f:9a08:a800:1ac0:4dff:fedb:a3f1)12:16
- aakast (QUIT: Ping timeout: 248 seconds) (~aakast@80-62-116-40-mobile.dk.customer.tdc.net)12:17
minutejosch: i think bkeys needs this hdmi variant because edk2 isn't visible yet on dsi12:40
- Ar|stote|is (QUIT: Quit: No Ping reply in 180 seconds.) (~linx@149.210.5.33)12:46
+ Ar|stote|is (~linx@149.210.5.33)12:46
+ paperManu (~paperManu@72.10.128.164)12:52
- Ar|stote|is (QUIT: Quit: No Ping reply in 180 seconds.) (~linx@149.210.5.33)13:16
+ Ar|stote|is (~linx@149.210.5.33)13:21
grimmwareI wonder if we could maintain a community spreadsheet where people can add their setups along with software and hardware mods they’ve done, what issues they’re facing and what they’re working on13:44
grimmwareBy we I mean the community, not MNT13:44
- chomwitt (QUIT: Ping timeout: 268 seconds) (~chomwitt@2a02:85f:9a08:a800:1ac0:4dff:fedb:a3f1)14:46
bkeysminute, josch: I don't think I need hdmi variant because edk2 is visible on the internal display?14:57
bkeysUnless I'm misunderstanding14:57
minutebkeys: in your laptop, the internal display runs via hdmi converter14:58
minutebkeys: that's why you can see anything on screen with edk2.14:58
bkeysBut yes for the record I have classic reform with rk3588 and edk2 on the emmc14:59
bkeysminute: So will josch's image work?15:00
minutebkeys: i don't know, but reform-system-rk3588 is the correct variant for your system.15:01
bkeyshttps://source.mnt.re/reform/reform-system-image/-/jobs/10908/artifacts/raw/reform-system-rk3588.img.gz15:01
bkeysAlright I'm downloading this one15:02
joschnice!15:02
bkeysjosch: That image booted flawlessly I didn't have to go into EFI shell or anything15:49
bkeysjosch: So since this boots, Fedora doesn't so it's not edk2's fault. I have to run my bike shop for just 2 hours today since it's Saturday. Can you show me what all you do to the kernel to make it work on the Reform2? Because the Rawhide kernel already has the proper reform2 .dtb files with it; so it must be something else15:51
bkeysWhen I get home I will do a serial connection to see if I can read further into this15:51
joschYEEEEES!!! \o/15:52
joschmagic? :D15:52
+ chomwitt (~chomwitt@2a02:85f:9a08:a800:1ac0:4dff:fedb:a3f1)15:54
bkeysjosch: Are there any reform2 patches that would interfere with the boot process?15:54
bkeysI'm at a sunk cost with this, I have waited to run Fedora on this thing for so long and spent so much time I will do whatever it takes at this point15:55
joschsunk cost fallacy? :D15:55
bkeysYes15:55
joschbkeys: i hope i can be of help with respect to the efi thing15:55
joschbear in mind, that most magic comes from scripts and tools not written by me15:55
joschwould it maybe help you to see the diff for reform-system-image which enables efi booting?15:56
bkeysWell, if I just boot Rawhide which has the DTB it will unpack the kernel then hang, the LED on the USB disk even turns off15:56
bkeysSure?15:56
bkeysWell Fedora kernel already boots from EFI that's the default15:56
joschbkeys: you have the collabora patch stack with your kernel as well, right?15:56
bkeysBut if I go into EFI shell and specify both DTB and the initramfs the LED doesn't die but the boot still hangs15:56
bkeysjosch: I'm assuming Fedora does not have said patches?15:57
joschdebian has neither15:57
bkeysI assume Reform kernel does?15:57
joschwe apply the rk3588 patch stack from collabora to the debian linux kernel15:57
bkeysLink to said patches?15:57
joschand then enable some config options15:57
bkeysLink the info, I gotta go to the bike shop then I'll be back on (although I got a vintage adult trike I gotta start restoring)15:57
joschbkeys: here is the full patch stack we add on top of debian's: https://source.mnt.re/reform/reform-debian-packages/-/tree/main/linux/patches6.1415:58
joschthe rk3588 specific patches are in the rk3588-mnt-reform2 folder15:58
joschand then you need some config options which are at the bottom here: https://source.mnt.re/reform/reform-debian-packages/-/blob/main/linux/config15:59
joschsome of these only make sense with the collabora patches15:59
joschbkeys: i would suspect that you can boot fedora successfully once you patch the fedora kernel to support rk358815:59
joschbkeys: note also, that the rk3588-mnt-reform2 dtb in vanilla linux is *not* the same that we use in Debian16:00
joschbkeys: the dtb in upstream linux is the subset which was required for u-boot. I think it was contributed to linux upstream by bluerise aka Patrick Wildt (u-boot & bsd developer i think)16:02
joschi am maintaining the diff from upstream linux rk3588 dtb to the one used by MNT repos here: https://source.mnt.re/reform/reform-debian-packages/-/merge_requests/89/diffs16:03
- bkeys (QUIT: Ping timeout: 272 seconds) (~Thunderbi@h211.16.186.173.dynamic.ip.windstream.net)16:05
joschminute: so... efi boot via edk2 works now apparently -- does that mean anything for the system images? Since efi needs a fat32 partition and since fat32 cannot do symlinks this unfortunately is incompatible with flash-kernel and the symlinks it creates in /boot -- is efi booting any important to you or do we stick with u-boot and extlinux.conf?16:05
joschminute: i'm also in karlsruhe next saturday, so we might run into each other maybe :)16:06
+ bkeys (~Thunderbi@66.110.201.50)16:19
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@66.110.201.50)16:26
ZabaI’d say trying to support efi boot officially would just further complicate the already pretty expansive testing matrix, even though in theory it is kind of neat to be able to do it16:27
Zabaif all supported variants could consistently use uboot with bootstd/extlinux.conf that would already be a massive win - and a more robust starting point for perhaps adding efi support in the future 16:28
joschZaba: extlinux.conf everywhere is where we are right now16:29
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)16:31
Zabaonly if people go through the process of updating their device and making sure there’s no stray boot.scr around, right?16:32
joschZaba: no, upgrading will not switch your boot method -- i'm talking about fresh installations from the system images provided by MNT and on reform.d.n16:32
Zabaright, which means you can’t really say that is where you’re at right now, unless you discount the actual devices in the field, i.e., the important ones :)16:34
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@38-146-94-247.echocast.zone)16:39
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)16:39
joschZaba: okay, but if you define "where we are right now" like that then we will always be stuck with boot.scr because we are not going to automatically convert users away from that via an apt upgrade16:42
- bkeys (QUIT: Ping timeout: 248 seconds) (~Thunderbi@38-146-94-247.echocast.zone)16:44
- Ar|stote|is (QUIT: Ping timeout: 248 seconds) (~linx@149.210.5.33)16:49
+ Ar|stote|is (~linx@149.210.5.33)16:54
+ bkeys (~Thunderbi@66.110.201.50)16:54
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@66.110.201.50)17:04
+ bkeys (~Thunderbi@66.110.201.50)17:05
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@66.110.201.50)17:07
+ bkeys (~Thunderbi@66.110.201.50)17:07
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@66.110.201.50)17:12
+ aakast (~aakast@87-49-43-63-mobile.dk.customer.tdc.net)17:20
- Core1951 (QUIT: Ping timeout: 268 seconds) (~aakast@80-62-116-34-mobile.dk.customer.tdc.net)17:24
+ bkeys (~Thunderbi@66.110.201.50)17:44
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@66.110.201.50)17:51
+ bkeys (~Thunderbi@66.110.201.50)17:51
+ bkeys1 (~Thunderbi@38-146-94-247.echocast.zone)17:56
- bkeys (QUIT: Ping timeout: 265 seconds) (~Thunderbi@66.110.201.50)18:00
- bkeys1 (QUIT: Ping timeout: 265 seconds) (~Thunderbi@38-146-94-247.echocast.zone)18:04
+ bkeys (~Thunderbi@h211.16.186.173.dynamic.ip.windstream.net)18:09
bkeysAlright I am back18:11
bkeysjosch: Do I blindly apply all patches?18:30
joschbkeys: "blindly"?18:30
bkeysIs there any patch in your link that I don't apply?18:30
bkeysSome say MERGED18:30
bkeysDo I omit those?18:30
bkeyshttps://source.mnt.re/reform/reform-debian-packages/-/tree/main/linux/patches6.14/rk3588-mnt-reform218:31
joschbkeys: MERGED means that they are merged with linux upstream but those patches are for kernel 6.14 and we are already beyond 6.15, so 6.14 is already "old news" :)18:31
bkeysYeah I was thinking I wanted to do at least 6.15 because then the reform2 .dtb was included, but you said they don't match anyway18:32
bkeysSo I can get rid of any patch that says MERGED?18:32
joschbkeys: if you checked that they are actually applied in your tree, sure18:34
joschbkeys: for the dtb, you can just grab the one from the source.mnt.re git18:35
bkeysI will18:35
joschif you want to use 6.15 you will have to rebase the patches first18:35
joschand then instead of rebasing the 6.14 patches you might want to grab the latest stack from collabora git instead18:36
bkeysI'll just stick with 6.14 I have to mess with the .dtb files anyway18:36
bkeysAre these patches identical to collabara's patches?18:37
joschbkeys: most of them are. We named them so that you can easily identify them with the collabora git next to it.18:38
joschThe patches that start with 00 are those from collabora and those that sort after are from MNT18:38
bkeysAlright let me sit here and think about what version I want exactly18:38
bkeysPreferably I could pick an LTS kernel and just worry about that version of it18:38
joschin that case, 6.12 is lts and we have a patch stack for that as well18:39
joschi am building that one for reform.debian.net and can verify whether it indeed works with rk3588 classic reform tomorrow18:40
bkeysI can't really make a decision, ideally it'd be nice and integrated and I can have whatever kernel version I want but I don't know packaging on that level18:53
bkeysAs cool as maintaining it sounds, I really want to just get on with using Fedora on my Reform, I don't want maintaining it to be a huge burden18:55
bkeysI think for now I will do 6.14 because that's what Fedora 42 uses, and I will branch out from there once that's verified to work and solve the problem18:58
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@h211.16.186.173.dynamic.ip.windstream.net)19:00
- Ar|stote|is (QUIT: Quit: No Ping reply in 180 seconds.) (~linx@149.210.5.33)19:10
+ Ar|stote|is (~linx@149.210.5.33)19:15
- vkoskiv (QUIT: Ping timeout: 244 seconds) (~vkoskiv@109-204-186-7.cust.valoonet.fi)19:23
- Ar|stote|is (QUIT: Quit: No Ping reply in 180 seconds.) (~linx@149.210.5.33)19:29
+ Ar|stote|is (~linx@149.210.5.33)19:34
- Ar|stote|is (QUIT: Quit: No Ping reply in 180 seconds.) (~linx@149.210.5.33)20:02
+ Ar|stote|is (~linx@149.210.5.33)20:08
+ Core1951 (~aakast@net-93-65-57-194.cust.vodafonedsl.it)20:35
- aakast (QUIT: Read error: Connection reset by peer) (~aakast@87-49-43-63-mobile.dk.customer.tdc.net)20:35
+ bkeys (~Thunderbi@134.22.115.162)20:48
+ SavagePeanut (59eaa45ac7@irc.cheogram.com)20:56
+ aakast (~aakast@87-49-43-63-mobile.dk.customer.tdc.net)21:25
- Core1951 (QUIT: Ping timeout: 252 seconds) (~aakast@net-93-65-57-194.cust.vodafonedsl.it)21:28
joschbkeys: i'm afraid that maintaining this patch stack is quite a bit of time investment at least for debian -- i would imagine it to be similar for fedora21:43
bkeysWell if I get a working system I don't really care if the kernel updates beyond LTS ones21:44
bkeysI'm gonna document all my steps of doing this by having it done via script21:57
joschnice, i like having my documentation be a script :)21:59
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)22:18
vagrantcjosch: so, reform-debian-packages contains more linux/patches6.12/ that are not git am-able ... i do not know appropriate authorship, but could list the files ... or i could propose a pull request with just dummy authorship info22:25
vagrantcsome of them are easy enough22:25
vagrantcworking on trying to get the patches to work on 6.12.31+ (an old version worked fine up until 6.12.30)22:26
vagrantcupstream backported changes to drivers/gpu/drm/rockchip/rockchip_drm_vop2.c that seem to be different/partial implementations of similar things22:28
vagrantc6.14 reached EOL already ...22:29
kfxI don't know why they even bother with 'stable' releases22:31
vagrantcrk3588-mnt-reform2/0029-WIP-drm-rockchip-vop2... might just require dropping the parts that dont apply22:31
kfxthree-month eol does nobody any good22:31
bkeysUgh, I hate adding the config file22:31
bkeysFedora doesn't like me just adding the config22:31
vagrantcrk3588-mnt-reform2/4001-mnt-rk35880dyal-hdmi-vop2-pll needs some work22:32
vagrantcthere's a reason i tend to go for LTS releases ... although even those tend to get some surprises22:34
vagrantcrk3588-mnt-reform2/0016-vop2-Add-clock-resets-support.patch also needs a fairly trivial rebase22:35
vagrantcbut other than that ... but for the most part they apply to 6.12.3322:35
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@134.22.115.162)22:40
- aakast (QUIT: Read error: Connection reset by peer) (~aakast@87-49-43-63-mobile.dk.customer.tdc.net)22:53
+ aakast (~aakast@net-93-65-57-194.cust.vodafonedsl.it)22:53
joschvagrantc: if you have a list, then i can add some dummy headers listing minute as author23:00
joschvagrantc: alternatively, if you have git format-patch files i also take those via email or pastebin :)23:00
joschvagrantc: you read my u-boot-menu community forum post from a few days ago? The problem is that if u-boot-menu is run via a trigger on a system that does not have the dtb symlink yet, then it will not add the fdtfile entry to extlinux.conf because the flash-kernel trigger which creates the dtb files is ordered *after* the u-boot-menu trigger23:01
+ bkeys (~Thunderbi@134.22.115.162)23:07
- bkeys (QUIT: Client Quit) (~Thunderbi@134.22.115.162)23:07
vagrantcjosch: hah. just went through and added some headers23:07
+ bkeys (~Thunderbi@134.22.115.162)23:07
joschvagrantc: if you have a diff of that, i take it :)23:07
vagrantcjosch: yeah, sounds like similar symptoms ... could be different cause23:07
joschyes, for example i don't understand how this situation occurred for abortretryfail who had an existing install23:08
vagrantcjosch: would you prefer a pastebin or a proper pull request? i'm nearly to the pull request already...23:08
joschand in that case, the dtb symlink should never disappear, no?23:08
joschvagrantc: whatever you prefer :)23:08
vagrantcjosch: well, in the case of mobian, the dtb was not a symlink but a directory ...23:08
joschoh how can that happen?23:08
joschvagrantc: i also wish that u-boot-menu would print more on stderr so that it would be easier to see what is going on just from reading /var/log/apt/term.log23:09
- bkeys (QUIT: Remote host closed the connection) (~Thunderbi@134.22.115.162)23:09
vagrantcjosch: because mobian ... did something that *looked* similar, but was actually different23:10
vagrantcjosch: i am surprised to see it outside of mobian, though23:10
joschvagrantc: you heard that MNT wants to produce a  tablet thing? We need to get mobian with its touch interface running on that one. :)23:11
vagrantccurrent mobian works fine ... they've fixed it23:12
vagrantcbut yeah, curious how the tablet will pan out23:12
vagrantchonestly, there is probably not anything left in mobian you couldn't just do in mnt reform repositories ... nearly everything is in debian23:12
joschvagrantc: i'm not touching mobian yet because i think it would not make much sense on devices without a touch screen, right?23:13
vagrantcjosch: at this point it is mostly just cutom kernels and a few metapackages ... maybe a few configuration packages ... nothing really different from what mnt/reform is doing23:13
vagrantcoh, looks like i am not set up to push to source.mnt.re repositories ... sounds like i send you a diff for this one :)23:15
joschokay! :)23:15
vagrantcjosch: https://paste.debian.net/plain/137969023:18
vagrantcjosch: some i just used the attribution information from when they were added ... which is probably wrong as we all know these were probably added by minute  :)23:18
joschvagrantc: haha yes, but i can easily just s/josch/minute/ in your diff no problem :)23:19
vagrantci swear i've done merge requests or whatever before on source.mnt.re... will see if i can set this up for when i *hopefully* get it rebased against 6.12.3323:20
joschvagrantc: https://source.mnt.re/reform/reform-debian-packages/-/commit/0bfb985268e89f85deea384cd264b4787a0ea856 thank you!23:21
joschi'll create a follow-up commit for 6.14 in a similar way23:21
vagrantccool23:22
vagrantci swear we have done this dance at least once before :)23:22
joschvagrantc: wow look, magic: https://source.mnt.re/reform/reform-debian-packages/-/commit/4dfa8c1d3b3339738ec55dd19a5c07f305c696b1 :D23:22
joschvagrantc: we did!23:23
vagrantc:)23:23
joschmy hope is that by adding it to 6.14 as well at least most of these changes will survive the next rebase of the patch stack (to 6.15)23:23
vagrantcteaching minute about git format-patch might help too :)23:24
joschnah if it just takes a few drive-by commits from us to fix issues like this, i'm 100% fine with minute spending their time on all the other todo things of the day :D23:25
vagrantctrue enough :) ... all the same, it is a small change probably23:26
joschyup23:26
joschi should do the 6.15 rebase... i didn't yet because there is no linux6.15 branch from collabora23:27
joschi pinged sebastian reichel about this without effect23:27
vagrantcoh, wonder if they have rebased against more recent 6.12.x ?23:27
joschi think i'll just use the rockchip-devel branch23:28
joschvagrantc: nope23:28
vagrantcrather than me clumsily trying to do this :)23:28
joschi'm also interested in 6.12 because it's the trixie kernel23:28
vagrantcright ... at least in git debian is already up to 6.12.33 for trixie23:28
vagrantcpretty sure the thing that is breaking it was done by collabora upstream23:29
joschyes and that will kept being bumped during the trixie lifetime23:29
vagrantceverything was fine up till 6.12.31 ... pesky backports23:29
joschupstream is already at 6.16 rc1...23:31
vagrantcgot tired of reverting the updates in Guix back to 6.12.30 ...23:31
vagrantcand they are about to drop 6.14.x and switch to 6.15... so ... here goes!23:31
joschXD23:31
- RandyK (QUIT: Remote host closed the connection) (~RandyK@user/randyk)23:38
+ RandyK (~RandyK@user/randyk)23:39
joschhehe "Initial support Cadence MHDP8501(HDMI/DP) for i.MX8MQ" is going to get a v21 :)23:39
vagrantcwell ... i made all the patches apply ... but partly just by removing parts of the patches :/ ... it did look like the problem was something was backported that might actually fix the issue23:45

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