15:00:23 #startmeeting Fedora ARM and AArch64 Status Meeting 15:00:23 Meeting started Tue Apr 7 15:00:23 2020 UTC. 15:00:23 This meeting is logged and archived in a public location. 15:00:23 The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:23 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:23 The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting' 15:00:23 #chair pwhalen pbrobinson jlinton 15:00:23 #topic roll call 15:00:23 Current chairs: jlinton pbrobinson pwhalen 15:00:31 Good morning folks, who's here today? 15:00:35 * jlinton waves 15:00:40 howdy jlinton 15:02:35 * pbrobinson is here now 15:03:38 ok, lets get started 15:03:48 #topic 1) ==== Userspace Status ==== 15:03:59 any new user space issues? 15:04:31 I think we're looking pretty good, on all releases. Anyone else? 15:05:23 #info No problems reported. 15:07:11 #topic 2) ==== Kernel Status ==== 15:07:44 I think we're mostly good here 15:07:57 like everything it can always be better 15:07:59 #info Latest kernel-5.6.2-300.fc32 15:07:59 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1488519 15:08:25 Right, looks pretty good in my testing as well. 15:08:27 I have pushed a few fixes for RPi to the f32 branch which will be in the next kernel build 15:08:44 I will be doing more testing on other HW 15:08:45 pi4? 15:09:09 Does that include the genet driver? 15:09:12 so a mmc fix for the rev 1.2 rpi4 HW and a general HDMI fix which affects all 15:09:33 jlinton: no, we have the genet driver though, what's wrong with it 15:09:48 and we have the upstream support for the rev in the rpi4 soc 15:09:51 Well the acpi bindings landed in 5.7 15:10:14 jlinton: if you have the explicit u/s commit I can pull it back 15:11:12 I can get them, while its a small change, its not tiny. 15:11:38 I will send them to you on fedora-arm and you can decide. 15:12:48 jlinton: I can see them, there's around half a dozen from you dated Feb 24th? Is it all self contained in drivers/net/ethernet/broadcom/genet/ or does it go to phy too> 15:14:31 No, its all in genet, except for the first, which is in the mdiobus/phy.h 15:15:00 Should be 6 patches 15:16:20 jlinton: I'll work with you after this to make sure I have them all and that it's a clean apply 15:17:27 ok, any other kernel business? 15:18:13 #topic 3) ==== Bootloader Status ==== 15:18:34 we have U-Boot 2020.04 RC5 15:18:43 the release was due this week but it's slipped a week 15:18:44 #info uboot-tools-2020.04-0.7.rc5.fc32 15:18:44 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1490824 15:19:06 #info Please test and report any issues to the list or #fedora-arm. 15:19:22 so please test as we'll either ship with rc5 or get a FE early next week to get GA in, I don't expected the later to be much different to this one 15:20:04 #info grub2-2.04-12.fc32 15:20:12 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1488126 15:22:26 looks like that grub also hasnt been in a compose that I've tested, yet 15:23:10 #topic 4) ==== Fedora 32 Final ==== 15:24:04 we had a bit of a change in the schedule, the final freeze was moved to Thursday, April 9th (I believe, or is it Friday?) 15:24:52 Thurs 15:25:13 #info Fedora 32 Final Freeze - 2020-04-09 15:25:25 no change in the target release date 15:25:29 #info F32 Final release(target) - 2020-04-21 15:25:38 #info Latest nominated nightly 15:25:39 #link https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test 15:25:47 #info Fedora 32 Final Blockers 15:25:48 #link https://qa.fedoraproject.org/blockerbugs/milestone/32/final/buglist 15:26:11 nothing specific to arm/aarch64 15:27:13 Anything else for F32? 15:27:24 Any issues not reported? 15:29:49 #topic 5) == Open Floor == 15:29:57 Anything else for today? 15:30:10 Draging up pac, discussion from last, week. Are we going to want a systemwide change request? 15:30:25 (so if nothing else it shows up in the changelog?) 15:35:37 Maybe that is a discussion for another place. 15:38:21 jlinton, I think it will require a change request for f33, but not clear on the scope. Do things need to be rebuilt? 15:38:43 Pretty much everything should be, as it would be a global compiler flag switch 15:39:17 I've spent a bit of time looking at rpm vs mock to see where the most appropriate place for the flags tweak is. 15:39:49 Since its platform specific. 15:40:56 right, for sure will need a change then. I've not submitted one that requires a rebuild, but recall some bits about it in the request documentation 15:41:40 lets move it to #fedora-arm, pbrobinson might have some more details when he returns 15:41:52 ba 15:42:23 jlinton: yes, we'll want a system wide change 15:42:44 jlinton: I can work with you on that to ensure we get it right 15:43:17 jlinton: are we going to do BTI as well or just PAC? 15:43:44 Thats the question. Break everything once, or twice? 15:44:40 I've only been testing it with -mbranch-protection=standard 15:45:31 that's for PAC? What about -msign-return-address as I think that uses the PAC HW feature too doesn't it? 15:45:45 basically I got that from here I think https://lwn.net/Articles/718888/ 15:46:18 The branch-protection flag is newer and turns on msign-return-address 15:47:24 Well, depending on setting. "standard" enables everything including BTI iirc 15:48:38 jlinton: OK, we can discuss offline 15:50:26 sounds good. 15:50:33 #endmeeting