IRC logs for #automotive for Monday, 2016-02-29

*** AlisonChaiken has quit IRC00:22
*** AlisonChaiken has joined #automotive01:17
*** AlisonChaiken has quit IRC02:34
*** sanjeev has quit IRC03:29
*** AlisonChaiken has joined #automotive04:08
*** swiss_ is now known as swiss04:48
*** gmacario1 has quit IRC06:22
*** gmacario has joined #automotive06:56
*** driftingblues has joined #automotive07:30
*** driftingblues has quit IRC07:31
*** driftingblues has joined #automotive07:33
*** driftingblues has joined #automotive07:35
*** nuohan has quit IRC07:41
*** fredcadete has joined #automotive07:47
*** toscalix has joined #automotive07:49
*** ctbruce has joined #automotive08:27
*** gmacario has quit IRC08:35
*** leon-anavi has joined #automotive08:37
*** Tarnyko has joined #automotive08:48
*** gmacario has joined #automotive09:01
Tarnykomorning everybody09:04
*** jobol has joined #automotive09:06
leon-anavimorning :)09:13
*** jonathanmaw has joined #automotive09:37
*** CTtpollard has joined #automotive10:03
*** jbocklage has joined #automotive10:08
*** gunnarx has joined #automotive11:31
*** gunnarx has joined #automotive11:31
*** gunnarx has quit IRC11:49
*** rjek_ is now known as rjek12:19
*** sukesh has joined #automotive12:21
*** Aleks1917 has joined #automotive12:41
*** driftingblues has quit IRC12:52
*** gunnarx has joined #automotive12:56
CTtpollardgunnarx: thanks for sorting out the go.genivi issue13:04
gunnarx CTtpollard: Well, I was only cleaning up my own mess... :)13:21
*** mdurnev has quit IRC13:31
*** riazantsev has joined #automotive14:23
*** ToxicGumbo-work1 has quit IRC14:32
*** ToxicGumbo-work has joined #automotive14:32
*** gmacario has quit IRC14:44
*** waltminer has joined #automotive14:48
*** ctbruce has quit IRC15:06
*** ndec has quit IRC15:16
*** ndec has joined #automotive15:18
*** ndec has joined #automotive15:18
*** gmacario has joined #automotive15:26
*** gunnarx has quit IRC15:31
*** gmacario has quit IRC15:48
*** AlisonChaiken has quit IRC15:52
*** gmacario has joined #automotive15:57
*** gunnarx has joined #automotive16:03
*** gunnarx has joined #automotive16:03
*** pedroalvarez_ is now known as pedroalvarez16:08
*** RzR has quit IRC16:10
*** RzR has joined #automotive16:10
fredcadetejonathanmaw: regarding your message to genivi-projects, I also don't see a better way16:13
*** ctbruce has joined #automotive16:13
jonathanmawfredcadete: thanks. I have the weird apprehension that I'll be expected to maintain weston 1.9.0 in perpetuity, so I thought it best to make it very public why I'm doing it.16:15
fredcadeteis it really necessary to have a GDP version on meta-ivi-9 + weston 1.9 ?16:16
*** waltminer has quit IRC16:16
fredcadetesorry, I haven't been following things for a while16:16
*** jlrmagnus has joined #automotive16:31
jlrmagnusGood morning.16:32
rjekAfternoon, jlrmagnus16:32
jlrmagnusMorning.16:33
rjek:)16:33
jlrmagnusWe had a late Friday brain storming session at the office, trying to figure out how to standardize vehicle signal names.16:33
CTtpollardfredcadete: there's been requests for having 1.9 + extension1.5/1.9 on gdp916:33
jlrmagnusWe didn't get too far before we gave up, went out, and got drunk, but I'd love some input from this channel.16:34
rjekjlrmagnus: Start with letters.  When you run out of them, move onto numbers.  After you run out of numbers, try symbols.16:34
jlrmagnushvac_front_left_123. Got it.16:34
jlrmagnusgunnarx, I spoke to Anders L about this, and he thought it was a good idea to get together around this.16:35
rjekI often use sort -R /usr/share/dict/words | head -116:35
rjek:)16:35
jlrmagnusI was thinking tree structure, like SNMP MIB, with a number of top level nodes such as body, drive_train, hvac, lighting, etc.16:35
gunnarxAren't vehicle signals standardized by AUTOSAR?16:35
gunnarx(playing 50% devil's advocate here...)16:36
jlrmagnusHaven't seen it since JLR are not members.16:36
rjekOr head -4 to generate an XKCD-style password, such as this joy: "cannibalistic shootable paralipomenon secessionists".16:36
*** mvick has joined #automotive16:36
gunnarxAh, bummer for you16:36
jlrmagnusWe are working on it.16:36
jlrmagnusIn any case, the database has to be freely available, and very lightweight in its extension process.16:36
*** Aleks1917 has quit IRC16:36
jlrmagnusgunnarx, Any way of opening that up?16:37
gunnarxrjek, nice password algorithm16:37
gunnarxAUTOSAR?  I wouldn't hold my breath under water :)16:37
jlrmagnusNeither would I, hence this discussion.16:37
CTtpollardgmacario: I've responded to your jira ticket :)16:37
*** waltminer has joined #automotive16:37
* gunnarx enjoys butchering english idioms16:38
jlrmagnusOpen Connect Foundation (IOC / Iotitivy) apparently has something.16:38
gunnarxjlrmagnus, let's for arguments sake say JLR doesn't have an AUTOSAR based standard, surely you have already named all your signals on the bus at least...16:39
jlrmagnusYes. And we will use that as a starting point.16:39
gunnarxbasically I'm wondering if mapping them to other names makes any sense16:39
jlrmagnusWe are going through our CANdb and scrubbing signals.16:39
gunnarxwell that will make it tricky for anyone else I'd suspect...16:39
jlrmagnusOnce we've scrubbed the signal, we will populate a namespace tree with them.16:40
jlrmagnusThat tree will be opened up.16:40
jlrmagnusBut I'd still like nominal concensus on the basic structure, which is not encoded in the current signalling.16:41
jlrmagnusI.e. What are the top level nodes, and how do we encode seating positions, etc.16:41
jlrmagnusWe need this in the RVI expert group since the signal names will be a part of the WebAPI for data harvesting and vehicle control.16:42
gunnarxNot a bad idea to work on although consensus might be a bit hard.  You would probably in part be presenting an AUTOSAR-alternative standard16:44
gunnarx"How do we encode seating positions", some of those things already in the existing vehicle signal interfaces?16:44
gunnarxprevious GENIVI work I mean16:45
jlrmagnusIn our interfaces, yes, but we don't do three seat rows, for example.16:45
fredcadeteeither AUTOSAR members make their spec available to open standards, or they can't expect the open standards to be AUTOSAR-like16:45
jlrmagnusfredcadete : Agree.16:45
gunnarxfredcadete, I'm not disagreeing with you16:45
jlrmagnusThe only previous standard I've seen is W3C automotive group.16:45
gunnarxbut you need also to consider OEM adoption of the "standards" that are created16:45
fredcadeteand that's all my butting in for today, have a nice evening16:45
jlrmagnusThat standard, after a cursory read, seems mostly focused on LBS.16:46
gunnarxjlrmagnus, you should know GENIVI had a lot of input into that16:46
*** riazantsev has quit IRC16:46
gunnarxand also worked with Automotive Message Broker maintainer.   As far as I know they are all pretty similar by now.16:46
jlrmagnusYes. And I am trying to figure out who, inside GENIVI< we want to talk to.16:46
jlrmagnusI agree on AMB, but its, and W3C's signal set is far too limited and, to be frank, a bit random.16:47
gunnarxAMB is both an implementation and a kind of attempt at interface definition at the same time.16:47
jlrmagnusCorrect. We want to break that up.16:47
gunnarxI'm sure everyone would welcome some continued work there16:47
jlrmagnusYep. And since JLR now has a clear need for that, I am starting to explore how to move forward.16:48
gunnarxMy reference to AUTOSAR was more about the names on CAN, FlexRay etc. and the scope being "all signals on the bus".  It's possible the subset that is exposed upward is more limited - thus not too far from W3C / AMB work?16:48
jlrmagnusI believe we actually need to make as much data as possible available (in a secure manner) to on and off board components.16:49
gunnarxI stand behind you.  Off the top of my head the previous proposals we have made is to use Franca in the IVI space and translate to/from other spaces16:49
gunnarxWeb APIs need to be translated into WebIDL16:49
jlrmagnusAgree.16:49
*** fredcadete has quit IRC16:50
gunnarxIONAS is for translating against AUTOSAR although you may not care.  and so on16:50
jlrmagnusBut I believe we need to start at the bottom, defining the namespace structure.16:50
* paulsherwood cheers jlrmagnus and gunnarx on from the sidelines16:50
jlrmagnusI'll do the usual thing: Sit down with a few JLR colleagues, come up with a proposal, and let the SAT team shred it to pieces.16:50
jlrmagnusAt least we will have something concrete to discuss at that point.16:51
gunnarxHappy to participate in the shredding ;)16:51
jlrmagnusBTW: Ericsson's Magnus Olson, RVI-EG's new system arhitect, has a lot of experience interfacing OMA, W3C, etc.16:51
jlrmagnusHe will drive the standardization process on the expert group's behalf.16:52
jlrmagnusHello paulsherwood .16:52
gunnarxsounds good to me16:52
jlrmagnusI'll put together a simple JSON structure (or similar) and publish it on github.16:53
jlrmagnusSpeaking of: Did we ever figure out who had admin rights to github.com/genivi?16:53
jlrmagnusFor RVI migration.16:53
gunnarxno, and I didn't care16:53
gunnarxwait, what?16:53
jlrmagnusToo late. Your non-careness ha been officially recorded.16:53
gunnarxI didn't think we said RVI should migrate there, did I miss some decision?16:53
jlrmagnusYou missed the discussion - decision is yet to be made.16:54
jlrmagnusThe proposal from JLR is that we use github.com/genivi as our daily work area, and use auto pushers to keep git.projects.genivi.org as an up-to-date master.16:54
gunnarxIs this a problem issue for you still, where to put stuff?  I've been downplaying this as a non-issue at the moment...16:55
jlrmagnusI never get any real feedback from Philippe or jeremiah|AFK  on this.16:55
gunnarxand what do you want to achieve by doing that?16:55
gunnarxlet me ask this way, who has commit access to that github account?16:55
gunnarx^^ who would you give commit access16:55
jlrmagnusI'd rather get RVI out of a JLR-owned repo into a GENIVI-hosted one to show that this is a GENIVI repo.16:55
jlrmagnusTo the genibi github account?16:55
gunnarxyes16:55
paulsherwoodjlrmagnus: hi :)16:55
jlrmagnusThe same people who has admin rights to git.projects.genivi.org?16:56
paulsherwood+1 for github.com/genivi16:56
gunnarxyes...16:56
jlrmagnusHear hear.16:56
gunnarxand... so I'm asking what is the github account used for16:56
jlrmagnusLet's have a look, shall we?16:57
jlrmagnusSDL16:57
jlrmagnusAnd SDL only.16:57
gunnarxNo... please understand16:57
gunnarxwhat *would you use it for*?  (that you cannot use git.projects.genivi.org for).  It's all git...16:57
gunnarxDo you have a workflow in mind that involves github.com/genivi for anything else than "keeping code around" (which is then auto-pushed to another git anyhow).16:58
jlrmagnusWe presented a git branch / release document a while back, which we would use as a guideline.16:59
gunnarxAs I'm sure you can see, I don't "get it", and since I wasn't part of the original discussion I don't know if we have an issue here.  As I said, I had assumed this is not a blocker for you.16:59
jlrmagnusIt's more of a piece that we need to get right to make this a genivi-owned project.17:00
jlrmagnusThe reason for moving to github is primarily to attract more community developers to our projects.17:00
jlrmagnusGithub provides a low barrier of entry that everybody knows.17:00
jlrmagnusWe could do the same thing from PDXostc, but that repo is clearly a JLR-owned thing.17:01
paulsherwoodjlrmagnus: not everyone... there are still some clearcase users left in the world ;)17:01
gunnarxwell owned is not the most important perhaps17:01
gunnarxbut what then does git.projects.genivi.org not give you?17:01
gunnarxTo get to the point:  I may be thick, but the only thing I can see github gives anyone is a "one click fork", instead of a few shell commands.17:01
gunnarxAh, that's another aspect though17:02
paulsherwoodgunnarx: you're not thick, but i don't think you're correct on this17:02
jlrmagnusPull requests, and a brilliant UI.17:02
gunnarxFair enough, as far as I know this will be discussed further next week.   I understand your input then is that GENIVI should use github in order to attract community developers.   Fair enough.17:02
jlrmagnusBut the bottom line is that if we want to attract more, non-GENIVI RVI developers, we need to roll out the welcome mat.17:03
jlrmagnusAnd github has the best rug of them all.17:03
gunnarxbrilliant is arguable.  But I'm not saying the current git.projects is what we should keep forever17:03
gunnarxjlrmagnus, I have picked up that point, no need to hammer it home.  Didn't know that was your driving point as opposed to technical17:04
jlrmagnusOk. I'll rest my case.17:05
* paulsherwood smiles, for once17:05
gunnarxSo backtracking a bit I'm still not seeing this as a blocker.  Community welcome rug is not preventing you from getting started.   The strategic discussion is already on agendas so don't worry.17:05
gunnarxYou could start with PDXostc + genivi git basically17:06
jlrmagnusyes.17:06
jlrmagnuswe shall do that17:06
jlrmagnuson the phone17:07
*** AlisonChaiken has joined #automotive17:07
gunnarxjlrmagnus, https://at.projects.genivi.org/jira/browse/TOOL-52 was opened, and closed again.   TOOL-9 and TOOL-14 are related.  It's a bit messy.17:15
gunnarxAnyway if you are partial to pull-request workflow, feel free to give that input in Tools forums (JIRA & Email might be more useful than IRC).  That type of input is exactly what was solicited.17:15
gunnarxBack in the day.... people managed without any stinkin'  "hubs"  :)   Poke the recipient about something, they do a git fetch, and diffs locally with whatever tool they prefer and everyone is happy?  :-)17:21
*** ctbruce has quit IRC17:21
*** BB has joined #automotive17:30
*** BB has quit IRC17:34
*** toscalix has quit IRC17:36
gunnarxpaulsherwood: If you're wondering I was just trying to get to the bottom of jlrmagnus' concern which I assumed was workflow/technical.  In Tool-52 I had already last week noted most of the mentioned aspects, including features other than one-click-fork, the large ecosystem of other tools around Github, _and_ the community aspect.17:43
jlrmagnusstill on the phone. discussing this very topic.17:44
gunnarxdo something more useful ;)17:45
gunnarxAre the participants in the discussion up to date with Tool-52 and other work at least?17:45
jlrmagnusi would say no...17:45
gunnarxthat's what I expected :-/17:45
jlrmagnusi will bring them up to speed.17:46
gunnarxI'm a little concerned with the efficiency of going around and around in circles on this.  There is a pretty clear Tools team desire to take this towards a conclusion.  There's a BoD meeting next week which I suspect should give input on any strategic matter, and so on.17:47
gunnarxOf course it's your time and I should butt out...17:47
paulsherwoodgunnarx: thanks for mentioining https://at.projects.genivi.org/jira/browse/TOOL-52 - that looks like a very useful discussion17:48
gunnarxOf course if you come up with any new arguments that have not been seen, that's fine.17:48
*** chbae has joined #automotive17:50
*** jonathanmaw has quit IRC17:50
gunnarxpaulsherwood, the content of  TOOL-52 was discussed on last week's Tools meeting.  We said we have until this week's Tools meeting to come up with any more input before the Tools team should give a kind of technical recommendation.  And as I said if there's a community/strategic aspect to all this hopefully the BoD will give an opinion.  So it seems to me a communication issue mostly at this point?17:52
gunnarxDon't really have more to add right now, going afk17:53
paulsherwoodgunnarx: yup, fair enough. i won't drag TOOL-9 up again, TOOL-52 seems reasonably self-contained :)17:53
gunnarxyes, it was a worthy attempt at least ...17:54
paulsherwoodwe can only do our best :)17:55
*** gunnarx has quit IRC18:01
jlrmagnusBack, too late it seems.18:06
*** joone has joined #automotive18:12
*** leon-anavi has quit IRC18:17
*** chbae has quit IRC18:32
*** chbae has joined #automotive18:35
jlrmagnusLooking into tool-5218:36
*** chbae has quit IRC18:40
*** chbae has joined #automotive18:41
*** chbae has quit IRC18:45
*** aeiche has joined #automotive19:32
aeicheGreetings #automotive19:32
aeicheDoes anyone happen to know where the recipe is (in GDP) that builds the LayerControlManager?19:32
radiofreethat's part of wayland-ivi-extension19:37
radiofreeso that recipe will have it19:38
aeicheokay19:40
aeichethanks19:40
aeichehmm19:48
aeicheI'm trying to get the layer-add-surfaces component in GDP19:49
aeicheThe wayland-ivi-extension repo suggests that GDP should get all of the tools on build, but unfortunately I only see three19:55
aeicheEGLWLInputEventExample19:55
aeicheEGLWLMockNavigation19:55
aeicheand LayerManagerControl19:55
radiofreeis layer-add-surfaces part of ivi-extension?19:55
aeicheyeah19:56
radiofreeit doesn't look like it was ever merged19:56
radiofreehttp://lists.genivi.org/pipermail/genivi-ivi-layer-management/2015-July/002913.html19:56
radiofreeah19:57
radiofreeit's in examples http://git.projects.genivi.org/?p=wayland-ivi-extension.git;a=tree;f=ivi-layermanagement-examples;h=91ea5362b3d0ccdecae91d622847684d88c6cb3d;hb=HEAD19:57
aeicheRight19:57
aeichebut so is LayerManagerControl19:57
aeicheso I assumed that it'd make the cut19:57
radiofreei seem to remember the gdp using an old version, do you know what version is in the gdp?19:58
aeicheI don't19:58
aeicheand the command doesn't say...19:59
radiofreeyou need at least 1.4.91, or backport it to whatever version you're using19:59
aeicheIVI extension?20:00
radiofreebackport layer-add-surfaces, it's these patches http://git.projects.genivi.org/?p=wayland-ivi-extension.git;a=history;f=ivi-layermanagement-examples/layer-add-surfaces;hb=5626251f7b7ad69079ceb611e640c565e947efc920:00
*** jobol has quit IRC20:01
radiofreei think there's a newever version of the gdp which should have it in20:01
aeichehmm20:01
aeicheI'm working on the beta right now20:02
aeicheTom's Minnowboard branch20:02
radiofreehttp://lists.genivi.org/pipermail/genivi-projects/2016-February/001550.html suggests there's some branch somewhere with weston 1.9, which would mean they've upgraded ivi-extension as well20:02
aeicheOh right20:02
aeichethat was just this morning...20:03
radiofreei think they're in the process of upgrading the GDP to more mainline components20:03
radiofreeit was all a bit of a mess previously20:03
aeicheIf I were just building with the defaults though, I shouldn't be dealing with 1.9 anyway20:05
aeicheor need it20:05
aeicheOr have I got that wrong, do I need 1.9?20:07
radiofreeof weston?20:07
aeicheyes20:07
radiofreei don't see why you wouldn't want to keep track of upstream weston20:07
aeicheOh20:08
radiofreei'm not an expert here, but wasn't/isn't the gdp using some odd branch of 1.5 with dozens of patches?20:08
aeicheLooking at the receipe, yes20:08
aeicheI think20:08
aeicheI'm also not an expert20:08
radiofreemoving to something totally upstream is always more beneficial in the long run20:08
aeicheI'm just trying to hack my way into running some different QML20:08
aeicheBut I'm also on a short term time-table20:09
radiofreee.g multi-screen support for ivi-shell (part of mainline weston) is improving all the time, that's probably something you'd wnat to keep track of in the long run20:09
radiofreedo you need layer-add-surfaces for that?20:09
aeicheThat's my path of least resistance.20:09
aeicheI figure I can do it a few ways20:09
radiofreeif you run the qml app with the qtwayland platform it should show up in the list of surfaces20:10
radiofreesurface id == pid if i remember correctly20:10
aeicheRight, but that requires writing a C++ app to wrap the QML20:10
radiofreeqml-viewer foo.qml -platform wayland-egl20:11
aeichehmm20:11
radiofreeshould work?20:11
aeichelet me give that shot20:11
aeicheI was building off of the AGL launcher shell script20:11
radiofree`LayerManagerControl get surfaces` should tell you if it has or not :)20:11
aeichethat reminds me20:12
aeiche"failed to get surface context in ilmControl"20:12
aeicheis that bad news? I get it with almost anything in LayerManagerControl20:12
aeiche1 Surface(s):20:13
aeiche- Surface 2 (0x2)20:13
radiofreei don't think it's bad news20:13
radiofreeok... try...20:13
* radiofree holds breath20:13
radiofreeLayerManagerControl create layer 1000 800 60020:13
radiofreeLayerManagerControl set screen 0 render order 100020:13
radiofreeLayerManagerControl set layer 1000 render order 220:14
radiofreeLayerManagerControl set layer 1000 visibity 120:14
radiofreeLayerManagerControl set surface 2 visibility 120:14
radiofreedoes the QML show?20:14
aeicheOkay, give me a second to try this.20:14
aeicheDo I need to stop the gdp-hmi services ?20:15
radiofreeit's entirely possible surface 2 is something from gdp-hmi services, it shouldn't matter20:16
radiofreedid qml-viewer error out then?20:17
radiofreemake sure you `export XDG_RUNTIME_DIR=/wherere/is/correct`20:17
aeichewhat is the correct XDG_RUNTIME_DIR?20:18
radiofreeit's *probably* /run/user/020:18
radiofreehowever i have no idea20:18
radiofreedo ls /run/user/020:18
radiofreeshould be some file called wayland in there20:18
radiofreehowever since LayerManagerControl is working i would assume it's been set correctly20:19
radiofree(try `env` and see if XDG_RUNTIME_DIR is already set)20:19
aeicheyup - /run/user/020:19
aeicheokay20:19
aeichetrying again20:19
radiofreebasically you need to make sure qml-viewer is run in an environment where XDG_RUNTIME_DIR is set, did it give you an error20:20
aeichecan I use qmlscene?20:20
radiofreeyep20:20
aeicheokay20:20
radiofreethen check LayerManagerControl get surfaces20:20
aeicheThe only errors I'm seeing are the "failed to get surface context in ilmControl" when I do anything with LayerManagerControl20:20
radiofreethat shouldn't matter, do you see any more surfaces in the surface list?20:21
radiofreeafter running qmlscene foo -platform wayland-egl20:21
aeicheafter that, or after all the LayerManagerControl commands?20:21
radiofreerun the LM control commands later20:22
radiofreefirst lets make sure the surface is create20:22
aeicheyes20:22
aeicheI have an extra surface20:22
radiofreeok20:22
radiofreeso in those LM commands, replace 2 with the surface id of the newly created one20:22
radiofreeit's probably not "2"20:22
aeicheno20:23
aeiche:)20:23
aeicheHey!20:24
aeicheThere it is20:24
radiofreehurrah!20:24
aeicheThank you!20:24
aeicheIt's even got an ugly window title bar!20:25
radiofreeright, that's an enivronment setting20:25
aeicheokay20:25
radiofreeyou can basically do "export QT_SOMETHING_BAR=foo" to tell it not to do that20:25
aeicheokay20:26
aeicheI'll have to look at that20:26
aeicheAllright20:26
aeichethat was easier than I expected.20:27
aeichethank you so much20:27
aeicheNow I have to go try this with a much more complicated QML app20:27
*** jlrmagnus has quit IRC21:06
*** tguild has joined #automotive21:19
waltminercan one of the iot.BZH guys tell me what the proper capitalization of the company name is?21:39
waltminermaybe IoT.bzh or IOT.bzh21:40
*** aeiche has quit IRC21:45
Tarnykowaltminer: it is IoT.bzh :)21:45
waltminerthanks21:46
*** aeiche has joined #automotive21:50
aeichewaltminer, When all else fails, go CamelCase21:56
waltmineris that like going commando?22:04
aeichein the sense of making it up as you go along, yes22:06
*** riazantsev has joined #automotive22:38
*** waltminer has quit IRC22:55
*** Tarnyko1 has joined #automotive22:59
*** waltminer has joined #automotive23:20
*** riazantsev has quit IRC23:21
*** riazantsev has joined #automotive23:58

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!