IRC logs for #automotive for Sunday, 2015-07-19

*** rjekalso has quit IRC01:19
*** riazantsev has joined #automotive02:17
*** riazantsev has quit IRC02:21
*** riazantsev has joined #automotive02:35
*** riazantsev has quit IRC03:02
*** riazantsev has joined #automotive03:16
*** AlisonChaiken has joined #automotive06:07
*** fury has quit IRC06:36
*** AlisonChaiken has quit IRC07:15
*** AlisonChaiken has joined #automotive07:18
* paulsherwood was testing a new shout instance09:38
*** kanupatar has joined #automotive10:08
*** waltminer has joined #automotive10:47
*** waltminer has quit IRC11:17
kanupatarhi guys12:40
kanupatarmay I know, how can I get some help on ivi controller. I will share the use case if somebody exists here12:41
paulsherwoodi exist here :)12:42
kanupatarpaulsherwood: hi man12:42
paulsherwoodwhat do you mean by ivi controller, precisely?12:42
kanupatarok, I will explain.12:42
kanupatarI am working for a project where an ARM based board is used. Linux is used as the OS. wayland is used as the display protocol. QT is used for designing the HMI12:44
kanupatarwhen I try to run some QT based openGL applications, I am getting EGLnot found error12:45
kanupataralso, my hardware has some layered display architecture12:46
paulsherwoodhah... so you're state-of-the-art, then :)12:47
paulsherwoodi'm think there are some folks on here who may be able to make suggestions, but not sure how many check this channel on a sunday12:48
JEEBwell first of all you'd have to check what exactly fails12:48
JEEBalso what wayland implementation is being used? weston? if so, which shell? ivi-shell? do you also use the GENIVI layer management stuff?12:49
*** kanupatar has quit IRC12:50
*** kanupatar has joined #automotive13:05
kanupatarpaulsherwood: sorry, bad network connection13:05
paulsherwoodkanupatar: did you see JEEB's comments?13:07
*** kanupatar has quit IRC13:09
JEEBwow13:09
JEEBthat connection13:09
*** kanupatar has joined #automotive13:09
JEEBanyways, here's the logs https://irclogs.baserock.org/automotive/%23automotive.2015-07-19.log.html13:10
kanupatarI again back13:10
JEEBI recommend using a box on a more stable connection if your own connection is very bad. either through ssh+irssi on a box or irccloud or whatever13:11
*** kanupatar has quit IRC13:14
*** kanupatar has joined #automotive13:15
*** kanupatar has left #automotive13:16
*** weston has joined #automotive13:16
westonJEEB: I am using weston and ivi shell must be used as per requirements13:17
JEEBok13:17
westonJEEB: I am bit new to wayland and this display stuff13:18
westonI have configured the ivi-controller.so in weston.ini13:18
JEEBso you're either using that thing adds wl_shell compatibility or one of those Qt patches that adds support for ivi-shell's protocol13:18
JEEBand I guess ivi-controller is the GENIVI layer management stuff13:18
westonJEEB: yes13:19
westonJEEB: qt verses ivi -->not clear13:19
westonany patch in qt is needed/13:20
weston?13:20
westoni built qt arm from source13:20
weston5.3.013:20
JEEBwell, ivi-shell only supports the ivi shell protocol unless you have a patch in there which AFAIK didn't go upstream13:21
JEEBand normal Qt doesn't support ivi shell protocol (although there are WIP patches AFAIK)13:21
westonJEEB: ohh .13:21
westonweston: thanks...I should find the patch for QT then13:22
JEEBor just apply the wl_shell compatibility thing to ivi-shell. I think Tizen IVI had it since it had wl_shell applications running under ivi-shell13:22
westonJEEB: may I know about the patch to be applied to QT lib during build?13:23
JEEBlet me see if I can find it from the genivi layer management mailing list13:24
westonJEEB: thank you13:24
westonpaulsherwood: hi man...thanks for pointing me here. I think i can also contribute here,13:24
westonpaulsherwood: may I know about this channel13:24
JEEBhttps://codereview.qt-project.org/121295/ , https://codereview.qt-project.org/121296/ , https://codereview.qt-project.org/121297/ , https://codereview.qt-project.org/121298/13:25
JEEBdo note that this is most probably for current ivi-shell, so if you're using some older version you'll have "tons of fun"13:26
JEEBI would guess this is against weston 1.8.x's ivi-shell13:26
westonJEEB: I am using Qt 5.3.013:27
JEEBwell then you'll just have to hope that those patches apply :P13:27
westonJEEB: so the thing is , I need to apply some patch to QT for IVI support...is that what I understood...can you confirm13:27
JEEByes, if your ivi-shell doesn't have wl_shell compatibility patches in it13:28
westonQT is having ivi-shell or wl-shell. sorry13:28
weston?13:28
JEEBivi-shell has its own protocol which is different to wl_shell; most wayland applications support wl_shell (and sometimes xdg shell) protcols13:28
JEEBthose patches add ivi-shell protocol support for Qt13:29
westonJEEB: okay.13:29
westonThe first patch tells it is for Qt 5.4.213:30
JEEBthey all are against 5.4.x13:31
westonJEEB: is they compatible with 5.3.0 ?13:31
JEEBI don't know :P13:31
westonJEEB: ohh13:31
* weston hard days ahead!13:32
paulsherwoodwelcome to the world of upstream integration :)13:32
JEEBalso I think this was what was in tizen ivi https://review.tizen.org/git/?p=profile/ivi/weston-ivi-shell.git;a=commit;h=14fe84de8f168a34798f2a300eb03b4043e567b513:32
paulsherwoodit's not so hard. everything's in the open, and git is awesome13:32
paulsherwood:-)13:32
JEEBaddition to ivi-shell that supports basic things in wl_shell13:32
westonwhat is the actual difference between ivi-shell and wl_shell?13:34
JEEBthey have their own protocols13:34
JEEBand ivi-shell was made by tanibata-san and friends at ADIT as far as I can tell13:34
westonADIT?13:35
JEEBwl_shell is one of the original shells in weston, I think?13:35
westonJEEB: yes yes13:35
westonweston-terminal13:35
JEEBanyways, at least ivi-shell is now in mainline weston; so you have one stable tree to develop against13:37
westonpaulsherwood: are you doing some integration?13:37
westonso, do I need to apply the Qt patched? confused13:38
JEEBas I have noted a few times already: if you are using a "vanilla" ivi-shell, yes.13:38
JEEBbecause as far as I know, the wl_shell extensions to it were never merged into upstream weston13:39
JEEB(I can be incorrect)13:39
westonJEEB: really confused13:39
westonso ivi patch and qt patches are needed13:39
weston?13:39
paulsherwoodweston: yes, i do integration and some other things :)13:40
JEEBa) you patch ivi-shell to support basics of wl_shell and enable "normal" wayland applications to show up under ivi-shell13:40
westonpaulsherwood: thanks13:40
JEEBb) you patch Qt to support ivi-shell13:40
JEEBit's one of these "Choose your destiny!" kind of points, I guess :P13:40
westonJEEB: okay. I am using yocto environment13:40
weston1.6.113:41
westonJEEB: understand13:41
westonso I will try a and b tomorrow13:45
westonwill be here in channel13:45
westonwhat about the channel activity?13:45
westonI mean time zones?13:46
paulsherwoodthere are people here from asia, europe, americas13:46
JEEBweston: btw I hope your weston is newer than yocto 1.6 had :P13:46
JEEBbecause if it's that old it means it's from the ages when all of the ivi-shell stuff and such was in rather chaotic situation13:47
JEEBaka "before it was upstream"13:47
JEEB(wayland-ivi-extension is still not in upstream, but ivi-shell itself is at least)13:47
westonJEEB: not sure at the moment. what could be the ideal combination of Qt,ivi and weston?13:48
westonusing Qt 5.3.013:48
westonweston x?13:49
westonivi x?13:49
JEEBdo you have to use wayland-ivi-extension (GENIVI layer management)?13:49
JEEBif yes, you will have to see which is the latest upstream weston version it supports... although it seems like it supports weston 1.8.x just fine13:50
JEEBlooking at http://git.projects.genivi.org/?p=wayland-ivi-extension.git;a=commit;h=2c136ba0ffa3f04d3479a01976ec0dd2b5433c6613:51
JEEBso I would go with ivi-shell from weston 1.8.x13:51
JEEBand wayland-ivi-extension 1.4.x if required13:51
JEEBsince those are the latest releases of those two13:51
JEEBfor Qt unless there's some specific reason I would also go for the latest release, esp. since the ivi-shell folks are pushing a patch there for the IVI shell protocol13:53
*** weston has quit IRC13:53
*** weston has joined #automotive14:13
westonpaulsherwood: JEEB sorry, network issues14:15
westonI will try the suggestions tomorrow and come back14:15
westonJEEB: paulsherwood thank you very much for the weekend support14:23
JEEBnp14:23
westonJEEB: may I know, about you guys..if any issues, leave that question14:24
*** kooltux_ has quit IRC15:17
*** kooltux has quit IRC15:17
*** weston has quit IRC15:48
*** AndChat|614900 has joined #automotive18:54
*** AndChat|614900 has quit IRC19:23
*** AndChat|614900 has joined #automotive19:23
*** AndChat-614900 has joined #automotive19:46
*** AndChat|614900 has quit IRC19:46
*** AndChat|614900 has joined #automotive20:01
*** AndChat-614900 has quit IRC20:01
*** jlrmagnus has joined #automotive20:04
*** fuury has joined #automotive20:45
*** fuury is now known as fury20:46
*** AlisonChaiken has quit IRC21:01
*** AndChat|614900 has quit IRC21:13
*** brlogger has joined #automotive22:17
*** shout-user79 has quit IRC22:17
*** brlogger` has quit IRC22:17
*** rZr has quit IRC22:20
*** RzR has joined #automotive22:25
*** AndChat|614900 has joined #automotive22:55
*** RzR has quit IRC22:58
*** RzR has joined #automotive22:58
*** ZrZ has joined #automotive23:05
*** RzR has quit IRC23:06
*** AndChat|614900 has quit IRC23:50

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