20:00:30 #startmeeting Fedora ARM status meeting 20:00:30 Meeting started Wed Sep 3 20:00:30 2014 UTC. The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:30 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:00:30 #chair pwhalen jonmasters bconoboy pbrobinson dgilmore dmarlin hrw jsmith 20:00:30 Current chairs: bconoboy dgilmore dmarlin hrw jonmasters jsmith pbrobinson pwhalen 20:00:40 afternoon all 20:00:44 .fas pwhalen 20:00:45 pwhalen: pwhalen 'Paul Whalen' 20:00:52 .hellomynameis jsmith 20:00:55 jsmith: jsmith 'Jared Smith' 20:01:05 * masta is here 20:01:24 * pbrobinson is here 20:02:45 doesnt look like we had any action items last time, so lets get started.. 20:02:52 #topic 1) Kernel Status Update 20:03:24 hola 20:04:00 pbrobinson, anything interesting worth mentioning here? 20:05:01 * pbrobinson is back 20:05:19 kernel 3.16 is the one we'll have for alpha 20:05:40 tegra K1 should be OK, and I'm working on some others 20:05:49 as for testing, not seeing any kernel breakage.. I did test Hans patches for the banana pi, both for uboot and kernel.. working well, Peter is looking at adding it to our kernel 20:05:54 would like feedback all round across all devices 20:06:33 I suspect we'll be moving to 3.17 post alpha but not 100% sure yet 20:06:56 wandboard quad boots, usb works, ethernet works, display works but no edid read (can be enforced with dms_kernel_helper.edid_firmware argument). did not checked sound of wifi 20:07:15 s/of wifi/or wifi 20:07:50 #info F21 Alpha to ship with 3.16 - Please test all devices and report issues 20:07:52 hrw: display works just fine here on wandboard quad 20:07:59 I believe wifi, if sdio attached, likely will have problems 20:08:25 dgilmore: I got xga resolution == no edid read 20:08:47 may dig for other hdmi cable if needed 20:08:49 hrw: that is a local issue, but one that should be fixed 20:08:57 hrw, I saw the same. I believe you were talking to someone about it? 20:09:24 pwhalen: got one patch to test from robclark. same effect 20:09:40 ah, ok 20:10:12 hrw: http://paste.fedoraproject.org/130793/77496414 is what i get from edid-decode /sys/class/drm/card0/card0-HDMI-A-1/edid 20:10:28 anything else kernel related? 20:10:43 no, I don't think so 20:10:57 we'll quickly talk about aarch64, then move on to all f21 alpha 20:11:03 #topic 2) Aarch64 Status update 20:11:17 mass rebuilt for both f21/22 is ongoing 20:11:28 kernel I believe is in reasonable state 20:11:35 it's all moving forward 20:11:42 major blocker at the moment is java 20:11:58 BZ? 20:12:03 aarch64 repos were broken today 20:12:04 openjdk-8? 20:12:14 #info Aarch64 mass rebuild for f21/22 in progress. Major blocker is Java 20:12:18 1130179 20:12:36 #info Java BZ: 1130179 20:12:42 3.17-rc0/fedora booted fine on mustang 20:12:48 #link https://bugzilla.redhat.com/show_bug.cgi?id=1130179 20:12:51 it's being dealt with by the maintainers so it's moving 20:13:38 dgilmore: here edid is full of 00 20:13:41 excellent, thanks.. anything else? 20:14:12 do we have composes going? 20:14:17 hrw: dgilmore: can you discuss that on the arm channel please 20:14:23 sure 20:14:47 bconoboy: it's moving forward, I believe dgilmore has a few bugs to deal with now TC5 is out 20:15:25 #topic 3a) F21 Alpha - Test Day (Sept 18th) 20:15:37 #link https://fedoraproject.org/wiki/Test_Day:2014-09-18_ARM 20:16:31 oh cool, test day! 20:16:44 * masta marks his calendar 20:16:44 I've created a wiki page, needs some work including the actual tests to be performed. first test day is to determine a baseline support 20:17:19 as you can see, f21 should work on quite a few boards.. 20:18:00 this is the overview of the core ideas for board support in F-21 http://nullr0ute.com/2014/08/fedora-21-and-arm-device-support/ 20:18:57 #info Overview of board support in F21 - http://nullr0ute.com/2014/08/fedora-21-and-arm-device-support/ 20:19:31 That list looks good 20:19:32 interested in feeedback, tests you think we should look at.. either here, on the list.. 20:19:33 I have bbw, pandaboard ea1 on which I can run tests. 20:21:17 I'm trying to get A15 boards (arndale & omap5 uevm) working, but I'll probably give up on them, and focus on any boards I happen to own from the primary list. 20:21:55 If we get Tegra k1 working, then that is a good A15 story. 20:22:06 masta, its working 20:22:31 dgilmore: what's the state of uboot rebase? 20:22:47 pbrobinson: its coming along, there is a lot thats changed upstream 20:23:25 do you think it'll land, even if it's just rawhide as a first cut, this week? 20:24:08 since we've changed topics.. 20:24:10 #topic 3b) F21 Alpha - ARM Status 20:24:21 he goal 20:24:25 pbrobinson: that is the goal 20:25:41 in other status, the selinux-policy bz for intial-setup is now resolved - https://bugzilla.redhat.com/show_bug.cgi?id=1112387 20:25:58 that was an open arm specific blocker for f21 20:26:10 eoo! 20:26:14 woo! even 20:26:25 network installations seem to be broken-ish.. 20:27:05 pwhalen: borken-ish ? 20:27:06 a little confused with all the different repositories, looks like we have multiple pxe images, repos .. 20:27:32 pwhalen: that is expected 20:27:37 I was able to do a network install using the workstation repo, but server blew up on storage 20:27:39 onbe install tree per product 20:27:46 ugh 20:27:53 pwhalen: that is expected one install tree per product 20:28:04 right, got ya, and figured as much.. 20:28:08 pwhalen: server is broken in general right now 20:28:12 its not arm specific 20:28:28 though the storage code is the same 20:28:34 so there is some other issue there 20:28:40 i did see that, but didnt hit the same reported bug 20:30:39 there is a lot of changes in flight here still 20:30:48 again not at all arm related 20:31:04 agreed.. when will the next TC be? 20:31:19 bconoboy: have you heard how torez is doing on XFS support? I know the Server WG would like to use it everywhere 20:31:30 pwhalen: as soon as we have enough to make it 20:31:55 ok, so not determined. thanks 20:32:57 pwhalen: its done by the blocker bugs process 20:33:07 its not something I just decide to do 20:33:15 dgilmore: I understand she's working on it when she has time but haven't had an update in a couple weeks 20:33:30 dgilmore: why not ask her? 20:33:45 bconoboy: okay. not heard from her in ages. i will check with her 20:33:58 bconoboy: I asked you since you were here and shes not :) 20:34:23 :-) 20:35:06 alright.. any other f21 related issues to discuss? 20:35:30 test test test 20:35:33 file bugs 20:35:39 what he says... 20:36:00 right.. 20:36:01 ask questions on #fedora-arm if you're not sure 20:36:05 #link https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_TC5_Install 20:36:18 #link https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_TC5_Base 20:36:31 #link https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_TC5_Desktop 20:36:41 #link https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_TC5_Server 20:37:01 #info please add results to the wiki, file bugs on issues encountered 20:37:34 Hmm, someone pinged me. 20:37:55 Guess it was from the previous meeting in here. 20:38:14 :) 20:38:17 #topic 4) Open Floor 20:39:05 Can we start having this meeting more often? 20:39:15 and earlier? 20:39:20 more than once a fortnight? 20:39:41 has it only been 2 weeks? Seems longer. 20:40:13 I thought we've chosen to move it to a fortnightly cadence 20:40:21 I thought it was monthly 20:40:25 I had to miss change from 1/month to 1/fortnight 20:40:50 I'm sure someone said it was moving to fortnightly 20:40:55 anyway 20:40:56 pbrobinson: I thought we decided to move it to every 2 weeks but never did 20:41:12 +1 fortnightly 20:41:29 so I'm not completely on a different planet :) 20:41:54 no, you're right.. it was to be every two weeks. 20:42:05 so that's decided... 20:42:09 what time? 20:42:10 sold. 20:42:51 maybe take that to the list? 20:42:58 I'm flexible.. sounds like others want it changed 20:43:15 we have prior, hard to do on the list.. 20:43:24 pwhalen: set up a whenisgood? 20:44:00 dgilmore, sure. 20:44:07 earlier than 9pm would be nice, I think it's 10pm for hrw 20:44:19 but after bit of thinking 2200 is fine 20:44:39 if I need to put my daughter to sleep then I miss 2100 one 20:45:41 working with US based team messed my work time anyway ;D (not first time) 20:46:00 Okay, just start with biweekly? 20:46:35 yeah fortnightly is a good start, progress! 20:46:40 +1 20:47:02 that'll put the next meeting the day before test day which sounds good 20:47:32 agreed, anything else? 20:47:42 email for whenisgood will come shortly 20:47:50 fortnightly it is 20:48:02 bconoboy: learn the right lingo :P 20:48:38 dgilmore: I will forget fortnight word during night 20:48:50 #agreed fedora-arm meeting moving to forthnightly cadence 20:49:08 is it some kind of old british-celt-norman word? 20:49:33 hrw: In the US we only hear fortnight when watching period costume dramas 20:49:45 wikipedia says: The word derives from the Old English: fēowertyne niht, meaning "fourteen nights". 20:50:35 I try to keep my english closer to british than american but not so close to remember fortnight ;D 20:50:50 hrw: ill remind you daily :P 20:51:19 last call.. 20:51:30 hrw: dealing with dgilmore and I will keep you up to speed in proper english ;-) 20:51:53 pwhalen: test test test, then file bugs 20:51:57 that is all 20:52:34 pbrobinson: I had worked with UK based company for 18 months - it did lot to unamerican my english. 20:52:36 there are millifortnight units 20:53:00 20 minutes 20:53:03 there is one simple reason for me to forget it: there is no Polish word for it 20:53:18 3... 20:53:23 #info Please add your preference for our meeting time: http://whenisgood.net/39kpwq8 20:53:28 2... 20:53:34 uno 20:53:42 #undo 20:53:42 Removing item from minutes: INFO by pwhalen at 20:53:23 : Please add your preference for our meeting time: http://whenisgood.net/39kpwq8 20:53:43 sorry 20:53:55 times were off 20:54:22 will send to the list 20:54:35 #endmeeting