16:00:15 #startmeeting Fedora ARM and AArch64 Status Meeting 16:00:15 Meeting started Tue Jan 12 16:00:15 2016 UTC. The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:15 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:15 The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting' 16:00:15 #chair pwhalen bconoboy pbrobinson dgilmore hrw jsmith dmarlin 16:00:15 Current chairs: bconoboy dgilmore dmarlin hrw jsmith pbrobinson pwhalen 16:00:27 good morning folks, whos here? 16:00:36 morning pwhalen 16:01:39 good morning dmarlin 16:01:49 * pbrobinson waves 16:03:12 not many here, but i know its late for you pbrobinson, lets get started 16:03:20 #topic 1) ==== Package Status & Issues ==== 16:04:02 i think the #1 still remains a new binutils/systemd rebuild. 16:04:17 looking OK, we have a fixed grep failure today which should catch us up for the already small diff we have 16:04:20 using the rpms hrw built last week i was able to do some rawhide installs 16:04:52 I thought that was landing upstream and we should get it once we're back in sync 16:04:58 #info grep failure fixed today which should catch us up further. 16:05:21 my understand was we just needed a new build for it, sadly doesnt look like hrw is here 16:05:40 pinged 16:05:43 sorry 16:05:54 hola 16:05:57 .helo 16:06:01 .hello 16:06:01 dgilmore: (hello ) -- Alias for "hellomynameis $1". 16:06:03 no worries, just discussing issues.. what do we need for binutils? 16:06:09 .hello ausil 16:06:10 dgilmore: ausil 'Dennis Gilmore' 16:06:13 good morning dgilmore 16:06:26 * masta looks in 16:06:48 hrw, my understanding was just a new build of 2.26, rebuild of systemd? 16:07:00 pwhalen: update to snapshot 16:07:48 2.25 is latest release. we need 2.26 snapshot 16:09:06 ah, i see, sounds like we can only wait? 16:09:43 we can discuss with nickc and try to convince him 16:09:57 for us it is release blocker ;( 16:10:42 right, ok. 16:11:33 #info Binutils still needs build of 2.26 snapshot for aarch64. 16:11:42 anything other issues? 16:11:50 er *any 16:11:56 not from me 16:12:03 not currently 16:12:03 we had issue with grep but it got solved 16:12:26 hrw, right, mention just prior to you joining.. 16:12:27 be aware of gcc6 and golang 1.6 coming soon 16:12:41 #topic 2) ==== Kernel & Uboot Status ==== 16:12:47 pbrobinson: and mass rebuild after them 16:12:50 plus boost/ghc/nodejs4 and frinds 16:13:27 yep, dgilmore and I are in planning for those.... 16:14:10 #info 4.3 headed to stable on f23. Tested on armhfp, aarch64 without issue. Please test your favourite boards! 16:14:40 #info 4.4 final now in rawhide, pending aarch64 build. 16:14:45 pwhalen: sorry network dropped out 16:15:14 dgilmore, no worries 16:15:32 dgilmore: excuses ;-) 16:17:24 pbrobinson: its my story and I am sticking to it 16:17:53 I have been testing 4.4 on tegra, wandboard quad and cubox-i 16:17:57 anyway for kernel just test 16:18:01 #info Current U-Boot: uboot-tools-2016.01-0.4.rc4.fc24 16:18:05 new bits being enabled 16:18:09 #link http://koji.fedoraproject.org/koji/buildinfo?buildID=710222 16:20:18 #topic 3) ==== Rawhide Status ==== 16:21:43 Ive been testing rawhide on aarch64 locally using hrw's rpms for binutils 2.26 and systemd.. didnt hit any other issues, but thats when we have that pending fix. 16:21:56 for armhfp 16:22:11 #link https://fedoraproject.org/wiki/Test_Results:Fedora_24_Rawhide_20160112_Summary?rd=Test_Results:Current_Summary 16:23:45 despite the checks there for arm images, they dont boot to initial-setup in my testing and require a change to the initial-setup symlink in the ks, we no longer need to specify gui or text and just i-s.service 16:24:20 will review than this week 16:25:13 todays minimal image, booted ok in vexpress, kickstart install worked without issue. xfce booted to login on bpi-pro 16:26:02 #info Please update the QA wiki with testing results. 16:26:17 anything else for rawhide? 16:26:47 nope 16:26:56 #topic 4) == Open Floor == 16:27:55 i see a few of you got your chromebooks going thanks to masta's page, awesome, doing that today as well. everything up to date? 16:28:37 pwhalen: There are a few unknowns going on with those instructions, mostly around the size of those silly chromebook kernel partitions 16:29:29 in some cases the instructions are not working for mysterious reasons, yet to be solved. So looking for any/all feed back 16:30:04 masta, ok, will be cautious as i go, thanks.. and so far was smooth sailing 16:30:29 chromebook partitioning is not so complicated 16:30:47 anything else for this week folks? 16:31:00 gpt, big enough kernel partiition (set type, priority), rootfs partition. done 16:31:33 on samsung one it was fine to have 4MB kernel partition with uboot there + rootfs 16:31:40 hrw: apparently 24 MiB is the largest anybody has got to work on chromebook kernel partition 16:31:58 masta: do 4MB one and put chain uboot there? 16:32:04 lets move this to fed-arm, so pbrobinson can go to sleep :) 16:32:06 hrw: too small for initramfs + kernel to go inside FIT image 16:32:14 ok, eof 16:32:30 #endmeeting