fedora_arm_and_aarch64_status_meeting
LOGS
15:00:25 <pwhalen> #startmeeting Fedora ARM and AArch64 Status Meeting
15:00:25 <zodbot> Meeting started Tue Jun 18 15:00:25 2019 UTC.
15:00:25 <zodbot> This meeting is logged and archived in a public location.
15:00:25 <zodbot> The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:25 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:25 <zodbot> The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting'
15:00:25 <pwhalen> #chair pwhalen pbrobinson jlinton
15:00:25 <zodbot> Current chairs: jlinton pbrobinson pwhalen
15:00:25 <pwhalen> #topic roll call
15:00:34 <pwhalen> good morning folks, who's here today?
15:01:37 * pbrobinson o/
15:01:47 * nirik is in another meeting, but also wondering if any progress on the armv7 vm thing. ;)
15:01:47 * tdawson is sorta here.
15:02:32 <pbrobinson> nirik: sort of, I was sick the week you were off, pwhalen has been doing further testing, the 3 of us should re-sync
15:03:57 <pwhalen> nirik, minimal progress. Looks like we can move to f30 with updates+4.19 kernels
15:04:57 <pwhalen> ok. lets start
15:05:08 <pwhalen> #topic 1) ==== Userspace Status  ====
15:05:14 <pwhalen> any new user space issues?
15:05:27 <pbrobinson> nothing I'm aware of
15:05:34 <pwhalen> nor I
15:05:40 <pwhalen> #info No new issues reported.
15:05:43 <pbrobinson> the python 3.8 support is on the edge of slipping
15:05:51 <pbrobinson> but that's general, not arch specific
15:05:52 <pwhalen> I saw, sounds like it should
15:06:21 <pwhalen> ok, if nothing else, moving on
15:06:30 <pwhalen> #topic 2) ==== Kernel Status ====
15:06:40 <pwhalen> #info F30: kernel-5.1.11-300.fc30
15:06:40 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1289142
15:07:05 <pbrobinson> so 5.1.11 has a pretty decent CVE fixes in it so I would suggest people upgrade
15:07:28 <pbrobinson> over all I think both 5.1.x and 5.2-rcX are looking reasonable over all now
15:08:50 <pwhalen> #info F31: kernel-5.2.0-0.rc5.git0.1.fc31
15:08:50 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1288824
15:09:17 <pwhalen> rc5 looks ok on the various boards I've tested
15:09:55 <pwhalen> #info Please test and report any issues to the list or #fedora-arm.
15:10:06 <pwhalen> any other kernel news?
15:11:19 <pbrobinson> nothing from me
15:11:23 <pwhalen> #topic 3) ==== Bootloader Status ====
15:11:31 <pwhalen> #info uboot-tools-2019.07-0.1.rc4
15:11:31 <pwhalen> #link https://koji.fedoraproject.org/koji/taskinfo?taskID=35612902
15:11:42 <pwhalen> still building for armhfp
15:12:03 <pwhalen> pbrobinson, anything to highlight ?
15:12:51 <pbrobinson> no, ATM it's just a rebase to the 2019.07 release, we should be shipping F-31 with 2019.10
15:13:14 <pbrobinson> I've been playing with trying to get a bunch of our patches either upstream or dropped
15:13:35 <pbrobinson> and getting it to build with python3 all of which still need some more work
15:14:29 <pwhalen> #info Please test and report any issues to the list or #fedora-arm.
15:15:59 <pwhalen> #topic 4) ==== Fedora 31 ====
15:16:20 <pbrobinson> I need to work on aarch64 features for f31
15:16:47 <pbrobinson> pwhalen: did you reach out to nirik if he would be OK with enabling an aarch64 xfce image?
15:17:04 <pwhalen> #info F31 composes currently failing, last nominated compose was Fedora-Rawhide-20190601.n.0
15:17:18 <pwhalen> ah, no.. nirik^
15:18:00 <pwhalen> nirik, we're looking to add a lightweight desktop, makes sense to align with armhfp.
15:18:24 <nirik> sure. sounds reasonable
15:18:33 <nirik> 4.14 should be out this cycle also
15:19:03 <pbrobinson> nirik: is there an overview somewhere of with 4.14 brings?
15:20:03 <nirik> nothing yet, but https://wiki.xfce.org/releng/4.14/roadmap
15:20:57 <pwhalen> thanks
15:20:58 <nirik> mostly finishing move to gtk3 and various fixes/enhancements
15:21:10 <pbrobinson> cool, thanks
15:22:07 <pwhalen> I've done some testing on the rpi3. And I think the pine64 should also work with display in f31?
15:23:00 <pbrobinson> the pine64 is still up in the air, we might have working acceleration through the open lima driver but that's still TBA, we'll know more with kernel 5.3rc and mesa 19.2rc
15:23:25 <pwhalen> ok, nice to see it progressing
15:24:31 <pwhalen> anything else for f31?
15:24:36 <pbrobinson> it should work unaccerlated on most aarch64 AllWinner devices like it does on the 32 bit ones, things like pinebook are still awaiting the display bridge to land upstream for the panel
15:27:07 <pwhalen> did that soas pr get merged?
15:27:15 <pbrobinson> yup
15:28:16 <pwhalen> #topic 5)  == Open Floor ==
15:29:01 <pwhalen> I'll leave it open for a few minutes
15:30:06 <nirik> so f30 + 4.19 is ok on armv7 vm's?
15:31:49 <pwhalen> nirik, seems to be, I was able to do a number of builds without issue
15:32:51 <nirik> ok.
15:33:02 <nirik> hopefully we can find the real issue soon.
15:34:29 <pwhalen> nirik, yea. the priority was changed to high
15:35:04 <nirik> we do have some new hw in the pipeline, which might solve it... if it's specific to moonshoot
15:35:13 <nirik> but not sure when that will arrive
15:36:06 <pwhalen> right.
15:36:27 <pwhalen> nirik, are all the builders now on f29 ga with 4.19.2?
15:37:11 <pwhalen> 4.19.x in general looks good, however I did hit the implementation fault on 4.19.7 once
15:37:17 <pbrobinson> nirik: pwhalen: yes, I think we need to do mutli prong on this, even with the new HW. I'm back to full health and pwhalen has got it a good way along so we should be able to drive it forward some more this week
15:37:22 <nirik> yes.
15:37:38 <nirik> well, f29 + updates and 4.19.x
15:38:10 <pwhalen> nirik, right. dont think the updates matter.. seemed to with 4.20, but with 4.19 it looks better
15:38:44 <nirik> yeah, so likely it was something that changed in 4.20+ or changed in 4.20 and more in 5.x
15:39:08 <pwhalen> 5.1 fails much faster, within minutes
15:40:08 <nirik> yeah
15:40:18 <pwhalen> ok, anything else for today?
15:41:34 <pbrobinson> not from me
15:42:01 <pwhalen> #endmeeting