21:01:22 #startmeeting Fedora ARM status meeting 21:01:22 Meeting started Wed Jan 8 21:01:22 2014 UTC. The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:01:22 Useful Commands: #action #agreed #halp #info #idea #link #topic. 21:01:22 #chair pwhalen jonmasters bconoboy ctyler pbrobinson dgilmore dmarlin jdisnard handsome_pirate msalter ahs3 agreene jcapik ddd 21:01:23 Current chairs: agreene ahs3 bconoboy ctyler ddd dgilmore dmarlin handsome_pirate jcapik jdisnard jonmasters msalter pbrobinson pwhalen 21:01:32 Happy New Year! 21:01:36 .fas pwhalen 21:01:36 pwhalen: pwhalen 'Paul Whalen' 21:01:37 .fas dmarlin 21:01:42 dmarlin: dmarlin 'David A. Marlin' 21:01:42 .fas blc@ 21:01:45 bconoboy: blc '' 21:01:50 woot new year \o/ 21:01:56 * masta is here 21:01:59 .fas ahs3 21:01:59 ahs3: ahs3 'Al Stone' 21:02:58 hi 21:03:00 #topic 1a) Aarch64 - Status Update 21:03:02 .fas juszkiewicz 21:03:03 hrw: hrw 'Marcin Juszkiewicz' 21:03:24 things are building... not particularly automated but we're getting there now 21:03:28 .fas agreene 21:03:28 agreene: tag4fedora 'Tim Greene' - agreene 'Andrew Greene' 21:03:32 Ahoy, me hearties 21:03:38 .fas jdulaney 21:03:39 handsome_pirate: jdulaney 'John Dulaney' 21:03:56 pbrobinson: what're you big pain points on aarch64? 21:03:59 R 21:04:03 it's a bit early to start reporting problem packages as otherwise I'll be reporting a lot 21:04:25 yes R, ghc and a bunch of other languages 21:04:30 pbrobinson: can you survive without mariadb for some time? 21:04:35 nope 21:04:37 #info koji builds are running now- pbrobinson driving builds 21:05:05 hrw: it's a core dependency that half the world links to from ldap to logging platforms 21:05:08 soon I'm going to be joining pbrobinson in the effort to build 21:05:12 pbrobinson: tests need to be checked as some of them fail 21:05:36 DEBUG: Completed: Failed 3/2149 tests, 99.86% were successful. 21:05:36 DEBUG: Failing test(s): main.gis-precise perfschema.func_file_io perfschema.func_mutex 21:06:13 I have mariadb in my 'need to fix' queue 21:06:22 yep and we have a number of other packages that are similar that I've temporarily disabled tests for 21:06:28 pbrobinson: I point you to https://ghc.haskell.org/trac/ghc/ticket/7942 for ghc 21:06:32 but ultimately they need to be fixed 21:06:38 pbrobinson: Looks like there is some movement there 21:07:00 pbrobinson: sqlite, ruby? 21:07:04 #info Numerous bugs being worked through- mariadb is pressing 21:08:02 hrw: I've been working with the maintainers on ruby, sqlite should be fixed in the next release and it's currently got the same status of the non x86 platforms 21:08:25 yay! 21:08:30 .fas jcapik 21:08:31 jcapik: jcapik 'Jaromír Cápík' 21:08:40 there's a bunch of other things that I'm slowly working through and unbundling various circular dependencies 21:08:42 ruby failed in one test iirc 21:08:47 I'll add that we're going to be putting in a few more builders in near term, so we should have plenty of build power as chunks get unlocked 21:08:53 hrw: it's currently failing on mainline too 21:08:54 #info More builders being added this month 21:09:08 handsome_pirate: good to see them updating the ticket 21:09:39 so at the moment the status can be currently summed up as moving forward but it's some what rough around the edges and a number of issues which are being chased etc 21:09:47 can we disable those tests for mariadb? 21:09:57 bconoboy: so my own builds will have more power as I hack on fedora builder machine (or rather fedora build is on same as I was first there) 21:09:58 we're hoping to kick off the nightly rawhide composes RSN 21:10:44 so what's being done and how will start to be more public and hopefully synced out to the secondary mirrors 21:10:51 who is in charge of setting up nightly composes? 21:10:57 dgilmore? masta? 21:11:05 dgilmore and myself 21:11:06 pwhalen: we could put the test in a conditional block, in the aarch64 case have '|true' on the end of the line 21:11:16 It's mostly ready to go 21:11:29 I just need to clean up a few bits to actually make them almost useful 21:11:59 as it's a bit fugly in places 21:12:35 but that's about it at the moment 21:12:51 anything else aarch64, problem packages seem covered .. 21:12:58 nope 21:12:59 yeah it would copy most of the existing setup for armv7 for rawhide nightly, i would imagine 21:13:09 I'll send out things to the list as they become more useful 21:13:16 thanks pbrobinson 21:13:27 #topic 2a) F21 - Hardware Support Goals 21:13:33 I will send qt5 patches to bugzilla soon. 21:13:53 not usable for rawhide/aarch64 now as there is huge set of bdeps not there yet 21:14:11 well HW support is really not worth discussing IMO until we know what is going to land for 3.14 21:14:39 the plan is basically what we have for F-20 21:14:43 what's landing in 3.13? 21:14:54 nothing much over what we have in 3.12 21:15:00 improved i.mx 21:15:07 still no exynos-mp? 21:15:18 improved am33xx 21:15:19 hrw: nope, not even in 3.14 21:15:25 lpae is fixed on exynos5 21:15:26 samsung... 21:15:30 in 3.13 21:15:31 I've heard rumours of not before 3.16 21:15:35 utilite mmc in 3.13? 21:15:53 handsome_pirate: there is no MP support for any samsung platform 21:16:07 pbrobinson: I know 21:16:17 handsome_pirate: and it won't supported in fedora until then so it's a complete mute point 21:16:22 pbrobinson: lpae was broken, though, now it's fixed 21:16:42 handsome_pirate: still completely irrelevant for this discussion 21:17:16 the improvements in 3.13 are primarily improvements on what we have already 21:17:44 so before 3.14-rc1 nothing new 21:17:48 3.14 is looking like it will add allwinner support 21:17:56 workable allwinner support 21:18:07 I suspect more i.mx6 boards to turn up, but not too confident about the DTB's going upstream... so more of the same likely 21:18:27 the ZYNQ stuff might be working but I've not had anyone test it. jcm said he would as he has HW but I've not heard 21:18:39 F20 beaglebone black/white were console and questionable, where are with with 3.12/3.13 on those? 21:19:06 it's possible, but not guaranteed, that there will be .imx6 HDMI support for 3.14 21:19:35 3.12 on BBB is really good, or will be when 3.12.7 lands 21:20:03 3.13 for BBB I believe we'll be mostly upstream, there'll be a few minor patches 21:20:11 video? 21:20:31 basic modesetting is in place already in 3.12, as is usb 21:20:38 #info 3.13 kernel feature set is similar to 3.12, no new hardware specifically tested yet 21:20:45 3.12.7 will make the ethernet stable 21:20:49 cpu freq for BBB? 21:20:55 #info Note to BBB users: 3.12 kernel will make BBB video work 21:21:02 #undo 21:21:02 Removing item from minutes: 21:21:05 handsome_pirate: not in 3.12 21:21:07 #info Note to BBB users: 3.12 kernel will make BBB video work on F20 release 21:21:17 handsome_pirate: but I don't see that as critical 21:21:32 #info 3.12.7 will be the one to go with 21:21:35 pbrobinson: No, but it makes life better 21:21:58 dgilmore: any special uboot plans in F21? 21:22:21 handsome_pirate: it needs a generic cpufreq driver which doesn't have all the bits upstream and hence it's not critical 21:23:07 (greg k-h is right, it's past time that arm silicon vendors start landing support *before* they ship) 21:23:08 there might be basic support for the rockchips in 3.13 21:23:42 ctyler: and can I have a unicorn from the easter bunny please....? 21:24:16 * bconoboy adds unicorn to pbrobinson shopping list 21:24:23 it's not unreasonable. If you're booting a sim, you should be upstreaming. 21:24:36 can't be solved here guys 21:24:38 I've seen him posting about distro env configs, and creating fedora logs in the u-boot frame buffer 21:24:52 ctyler: I never said it wasn't reasonable but ultimately we need to live in the hear and now and work with what we have...... 21:24:56 s/logs/logos/ 21:25:05 My wish list for F21 is images that can be written and booted without weird post-write fixups. 21:25:19 +1 bconoboy 21:25:20 And to stop doing separate vfat images 21:25:33 my wish list is to have 64-bit hardware. GETONIT 21:25:43 jwb: more hardware is coming this week 21:25:45 jwb: we do in koji 21:25:48 +1 jwb 21:26:06 jwb: and the last gcc build on it built 30 mins faster than x86_64 21:26:17 impressive 21:26:23 excellent. then i extend my wish list to stop supporting 32-bit 21:26:23 +1 bconoboy and jwb, but the unicorns are flying fast and furious today 21:26:24 ;) 21:26:44 we'll eventually use aarch64 hosts for armv7hl builders 21:26:45 I want aarch64 desktop on my desk in 1H2014 21:27:00 so you'll see that nice speed on armv7hl builds. 21:27:08 can we please keep the meeting on track.... I would like to have dinner before 10pm 21:27:19 anything else for f21 wishlist? 21:27:21 bconoboy: the day we do it will be end of armv7 hw in build farm 21:27:28 bconoboy: ponies? 21:27:34 pwhalen: let's go :-) 21:27:34 #topic 2b) F21 - Installation Images 21:27:49 hrw: I have two horses... don't need ponies 21:27:50 pbrobinson: and I'd like to go to bed before midnight 21:28:19 pwhalen: what's the topic about? 21:28:29 I was about to ask the same 21:28:33 I made a net install image for the wandboard for f20, do we want to do more of that type of thing for f21? 21:28:56 why do we need board specific install images? 21:28:59 er, blc you requested it 21:29:04 er 21:29:04 pwhalen: i want to have pungi/lorax make installer images 21:29:06 pwhalen: Oh, this :-) 21:29:13 sorry, i had a question on HW support still 21:29:15 we dont.. just an example 21:29:19 Right, so I think the question is how far can we take anaconda installation on boards in F21 21:29:25 jwb: sure 21:29:32 Like can we abandon disk images and just use anaconda 21:29:44 have you all seen hans' allwinner proposal on the kernel list? 21:29:49 bconoboy: I doubt we can 21:29:55 jwb: no- pointer? 21:30:04 jwb: I'm aware of it, I've not read it all and I need to reply to properly clarify 21:30:09 bconoboy: but i want to move more towards installing not using precanned images 21:30:18 dgilmore: y, me too 21:30:21 jwb: I'll try and get to it tomorrow for you 21:30:24 dgilmore, +1 21:30:26 jwb: ive seen his proposal 21:30:32 bconoboy, https://lists.fedoraproject.org/pipermail/kernel/2013-December/004752.html 21:30:42 pbrobinson, your name is on the Change page... 21:30:43 jwb: ive not looked to see where we stand u-boot wise 21:30:52 I dont think there is upstream u-boot support 21:31:00 jwb: is the allwinner stuff even likely to go upstream, Hans wanted to carry patches... I was wondering if they are ACKed and those kind of nice things? 21:31:01 jwb: correct, the discussion I had with him was that it had to be upstream 21:31:20 masta, according to Hans, most of it will land in 3.14 21:31:20 jwb: i think its a win, there is a lot of cheap decent allwinner hardware out tehre 21:31:21 jwb: so I'm not sure what or why or how he's deviating from that 21:31:55 pbrobinson: that he wants to get it in fedora as its headed upstream 21:31:59 dgilmore: the support should mostly be there in 2014.01 and better by 2014.004 21:32:00 test early and often 21:32:04 ok, so my question is basically if you as a SIG are comfortable with that because nobody other than Hans chimed in on the thread. maybe you guys should discuss and reply on the thread? 21:32:26 jwb: that's what I was planning but I've just not had the time 21:32:33 ok. still a couple weeks out anyway 21:32:36 jwb: for me it got lost in holiday breakness 21:32:48 #link Hans' proposed kernel patch plan needs attention https://lists.fedoraproject.org/pipermail/kernel/2013-December/004752.html 21:32:49 jwb: I'll respond to his thread =) 21:33:07 jwb: from reading some of the upstream landing bits today while on a conf call I think most of it should be landing to give us usb/serial/sata/mmc/ethernet plus deps 21:33:51 screen and other bits likely not 21:34:58 and a20 is easiest to get virtualization platform with kind-of fedora support 21:35:18 hrw, yeah. that's why i was more open to it 21:35:18 pwhalen: next? 21:35:32 apparently the virt people are all using it or something 21:35:46 thats all... 21:35:47 #topic 4) Open Floor 21:35:49 jwb: I do not know other platform with such good support 21:36:00 I do have a quick topic 21:36:04 jwb: yes 21:36:29 Tomorrow, there will be a meeting to discuss QA tooldevelopment: 21:36:30 https://lists.fedoraproject.org/pipermail/qa-devel/2014-January/000599.html 21:37:20 what is the relevance or what do we need to discuss 21:37:23 One thing that would be cool would be for people to start thinking about tasks that they'd like to run against builds coming out of Koji 21:37:38 pbrobinson: Mostly, this is a heads up 21:37:55 Since ARM is primary, taskotron will have to take arm into account 21:37:57 handsome_pirate: first one which came to my mind: Are resulting packages installable 21:37:59 I don't see we should be any different to any other primary arch 21:38:01 handsome_pirate: i have a huge list of things, nothing to do with arm 21:38:08 hrw: Working on that already 21:38:17 handsome_pirate: i really dont think there is much arm specific 21:38:28 dgilmore: It was largely an fyi 21:38:38 there's a whole bunch of useful things but none should be arm specific 21:38:39 handsome_pirate: I feel too many packages built into not installable state. but thats mostly on aarch64 21:38:55 hrw: Like I said, working on that 21:39:06 handsome_pirate: great 21:39:13 any other topics? 21:39:20 ABI checks, rpmdiff checks. there is a ton that can be done 21:39:29 Indeed 21:39:31 soname bumps 21:39:39 right 21:39:52 going once... 21:40:08 pwhalen: we didnt really finish the installer question 21:40:25 dgilmore: have anything to add? 21:40:28 we didnt.. we can go back 21:40:43 I dont see disk images going away, they are kinda analogus to livecds 21:41:07 the way they work is a pain- you can't write and use them which is what end users are expecting. 21:41:09 but we should maybe work closer with the spin owners to take them over 21:41:33 bconoboy: in what way? 21:41:45 dgilmore: adding uboot bits 21:41:56 bconoboy: we need to work on tooling for that 21:42:08 bconoboy: so i guess the question is 21:42:18 dgilmore: agree, but not clear on what the end result is that you'd support getting us to :-) 21:42:34 most distros make only a minimal image and make images precanned for a bunch of hardware 21:42:35 How are we getting read of fat partition? 21:42:41 Doesn't BBB require that? 21:43:01 I think we should get rid of the images without a fat partition. 21:43:01 we make generic images that need some tweaking but get to offer many different types of images 21:43:12 handsome_pirate: bbb has no requirement for fat 21:43:39 bconoboy: i think we should get rid of teh images with a fat partition 21:43:42 dgilmore: omap3/am in-cpu bootloader does not know !vfat iirc 21:43:49 we could provide 2 images- One OS image, One (tiny) board specific image- end users download both, write the first, then the second, to the same block device. 21:44:05 hrw: u-boot on the bbb is on fat on internal storage 21:44:23 you dont need vfat on microsd 21:44:27 ultimately the major reason for the vfat images is for the devices people may wish to use which either a) don't ship with a sane uboot b) we don't ship and build a uboot 21:44:31 and MLO can be read raw 21:44:31 dgilmore: ok. but bbw has only microsd 21:44:42 dgilmore: removing vfat will artificially keep fedora out of future boards which require it 21:44:44 teach the MLO ext and you dont need fat 21:44:58 bconoboy: if future boards require it they are broken 21:45:11 hrw: its fixable 21:45:17 +1 dgilmore 21:45:17 ok 21:45:21 * hrw off 21:45:36 22:44 21:45:40 dgilmore: uh, calling things broken because they're not how we want them isn't entirely accurate 21:45:47 bconoboy: hans is planning on extending his script to support writing out auto configs like on his remix 21:45:59 bconoboy: sure it is, anaconda cant do vfat 21:46:13 bconoboy: +1 21:46:27 bconoboy: so if it doesnt work like a regular linux system anaconda cant install it 21:46:37 and we cant support it 21:46:39 if we do disk image pairs we can separate the partitions/fs decision on a per-board basis 21:47:12 One minimal image, one xfce image, etc 21:47:27 then one trimslice image (ext4), one bbb image (vfat), etc 21:47:31 bconoboy: to get ahead we need to pick one thing and go with it, we dont have the tools or manpower to do anything else 21:47:59 bconoboy: not sure what your getting at there 21:48:15 dgilmore: a different way of handling the issue that lets people write disk images and boot without mounting and copying files. 21:48:34 I think there needs to be a proposal sent to the list and it discussed there.... we're just going around in circle here 21:48:41 +1 21:48:43 bconoboy: i can not picture what you are trying to describe 21:48:50 dgilmore: I'll mail the list 21:48:57 bconoboy: perfect 21:49:21 ok, anything else left or can pbrobinson eat dinner ? 21:49:32 lets wrap it up 21:49:57 #endmeeting