IRC logs for #automotive for Tuesday, 2015-08-11

*** jlrmagnus has quit IRC00:29
*** bbranch has quit IRC05:03
*** bbranch has joined #automotive05:05
*** bbranch has joined #automotive05:10
*** poxar has quit IRC06:43
*** gunnarx has joined #automotive07:41
*** jonathanmaw has joined #automotive07:51
*** mdunford has joined #automotive08:06
*** jacobo has joined #automotive08:07
*** jeremiah has joined #automotive08:12
*** jeremiah1 has joined #automotive08:14
*** jeremiah_ has joined #automotive08:14
*** KlausUhl has joined #automotive08:20
*** poxar has joined #automotive08:29
*** CTtpollard has quit IRC08:38
*** CTtpollard has joined #automotive08:41
CTtpollardwoop! second build of GDP for porter has booted!09:11
*** gunnarx has quit IRC09:11
paulsherwoodlovely :-)09:12
dzenporter ? as in beer ?09:12
fredcadeteas in lager and koelsch09:12
mdunfordso beer then? :)09:12
fredcadeteyes, that's Renesas's naming scheme for their development boards09:13
* rjek tries to remember the name of the company who named all their dev boards after scotches.09:14
*** wschaller has joined #automotive09:14
rjekPerhaps the fact that alcohol is a common theme is telling.09:15
jeremiah1lol09:15
jeremiah1Interesting hackfest today with the builder folks from GNOME09:16
jeremiah1They're looking into building out GNOME conitinuous and thinking about pulling in Yocto / Baserock09:16
*** jeremiah1 has left #automotive09:18
*** jeremiah_ has left #automotive09:18
rjekjeremiah: Interesting.09:19
paulsherwoodjeremiah: maybe you can help me with this...09:30
paulsherwooddoes the idea of working from a managed/known mirror of upstreams seem clearly a win to you?09:31
jeremiahpaulsherwood: Yes, absolutely.09:38
jeremiahWe've seen in GENIVI that using the build system when it pulls from dead upstreams it causes problems.09:39
jeremiahI can imagine that we're going to see that issue again09:39
jeremiahI also can see the usefulness of a *single* location to pull from for our builds09:39
paulsherwoodjeremiah: ok. but then i see gunnarx's point that to implement this for the GDP for example, we'd end up forking a load of recipes09:40
jeremiahWell, yes.09:40
jeremiahIt is going to be huge.09:40
jeremiahThis is why using maintained packages from a distro is so advantageous.09:41
paulsherwoodwhen i explained this concept to wolfgang denx earlier this year he said 'this is clearly a good idea... you should take it to yocto upstream'09:41
jeremiahDoesn't Yocto do something like this already?09:41
paulsherwoodwell if it does, why are the default recipes pulling from the wild internet?09:42
jeremiahLikely because they don't want to do the work of hosting an archive.09:43
paulsherwoodmaybe there's some magic url-mapper shim i'm not aware of09:43
jeremiahI think, now that I look a bit, its really just a way for one to use Yocto with local sources.09:43
jeremiahSo I don't think it really maps to a proper hosted semi-official mirror.09:43
jeremiahI don't know much about Lorry or the other tools you have but I don't know too many other tools that even attempt to do the kind of mirroring that baserock does09:44
paulsherwoodwell, i believe debian mirrors sources, but as tarballs09:45
paulsherwoodpresumablty the yocto local sources approach deals  bzr, hg, svn etc?09:46
jeremiahTo be honest I don't know about the internals09:46
jeremiahDebian does create source packages09:47
jeremiahAnd it hosts some upstreams in git as well09:47
rjekpaulsherwood: Debian normally mirror the project's release tarballs, along with a seperate tarball containing Debian-specific patches09:47
jeremiahThis allows you to do apt-get source <foo> and get the source of a given package09:47
paulsherwoodrjek: ah, ok09:47
rjekpaulsherwood: If a project doesn't make release tarballs (or Debian decide to ship a pre-release from a project's version control) then they make their own tarball.09:48
rjekBut that's pretty rare09:48
jeremiahBut what is great is that they have a source package FOR EVERY PACKAGE THEY SHIP!09:48
rjek(This also allows people to check the upstream release signature on what Debian mirrors and then patches, if such is provided)09:48
jeremiahWhich means that the 25,000 package strong archive is highly available and maintained for you.09:49
rjekjeremiah: It's amazing how many distributions don't do that09:49
jeremiahrjek: It is.09:49
jeremiahAnd it is part of what makes Debian so valuable09:49
rjekDebian is love.09:49
jeremiahrjek++09:49
jeremiahIt means we can use Debian to create builds of an image and you automatically have the "complete and corresponding" source code09:50
jeremiahSo you comply with the GPL trivially09:50
rjekIndeed.  That's also one of the great things about Baserock's approach09:51
jeremiahSo just stuff Debian sources in your CI and you can ship binaries.09:51
paulsherwoodexactly09:51
jeremiahYes, this is a huge benefit to Baserock's approach09:51
jeremiahHuge.09:51
paulsherwoodjeremiah: so my dilemma is how to help agl, genivi and automotive in general achieve this benefit...09:52
jeremiahpaulsherwood: Politically it may be hard because automotive folks are wedded to their tooling.09:52
paulsherwoodi don't think offering to fork yocto will be very popular09:52
paulsherwoods/yocto/yocto and oe recipes/09:52
jeremiahPractically just setting up a source mirror and enabling builds from Yocto should be fairly easy?09:53
jeremiahpaulsherwood: Perhaps just implementing it and offering it for use would be enough for adoption?09:53
jeremiahOr perhaps you (rightly) want this to be funded?09:53
paulsherwoodjeremiah: i believe that when others have done this, they forked the recipes09:53
jeremiahpaulsherwood: Ah, I see.09:53
jeremiahhmm.09:53
paulsherwoodit's not the funding, it's the question of maintenance09:54
paulsherwoodi don't want to lead automotive into forking anything if i can avoid it09:54
jeremiahShouldn't the maintenance be funded?09:54
jeremiahAgreed09:54
paulsherwoodi think i need a constructive discussion with yocto and/or oe upstream09:54
jeremiahpaulsherwood++09:55
paulsherwood(as amazing as that sounds, given some of the arguments in genivi in recent years)09:55
jeremiahOE might be a good place to approach09:55
jeremiahBut Richard Purdie in Yocto might be interested09:55
paulsherwoodisn't richard active in both places?09:55
jeremiahI imagine, you likely know better than I, I don't really work with him.09:56
jeremiahBut he's a Linux Foundation fellow so he would likely be open minded.09:56
paulsherwoodack09:56
jeremiahAs I mentioned, GNOME builder is going try to incorporate Yocto and/or Baserock, a source code mirror might fit well in such a project and potentially might yield shared maintenance.09:58
jeremiahBUt I think its early days still there.09:59
paulsherwoodjeremiah: ack, thanks for the headsup09:59
* CTtpollard would like the various guides on the gdp wiki to have links to prebuilt images10:06
paulsherwoodhere's a thought... could we do that and then just get folks to 'drop in' the binaries themselves?10:07
CTtpollardbut there's the obvious licensing complexity, especially with the renesas boards10:07
paulsherwood(eg for renesas)10:07
paulsherwoodthere would be no licensing complexity if the binaries were not present in the images?10:07
CTtpollardI would not think so no10:08
CTtpollardbut that's still adding to the complexity for a user who just wants to spin it up and may not have the knowledge / urge to start doing that10:08
CTtpollardyou would however not need to wait on build time, which is a start10:09
paulsherwoodCTtpollard: instructions for that would be simpler than the currnet process10:09
CTtpollards/simpler/shorter10:11
paulsherwoodboth :)10:11
*** jeremiah has quit IRC10:14
*** jeremiah_ has joined #automotive10:17
*** gunnarx has joined #automotive10:22
CTtpollardwhat about non-renesas images?10:25
*** jeremiah_ has quit IRC10:28
*** gunnarx has quit IRC10:42
*** gunnarx has joined #automotive11:03
CTtpollardwould it be acceptable to provide a renesas build without gfx acceleration, if it's still functional11:04
fredcadetemaybe I am late to the conversation about the mirroring11:08
fredcadetebut yocto has some stuff to avoid pulling from the internet every time you rebuild11:09
fredcadeteI have tested it, mostly to make sure that what you deliver to a customer can have its source tracked and the build reproduced11:10
fredcadeteeven years later11:10
*** wschaller has quit IRC11:10
paulsherwoodfredcadete: iiuc that's a 'local mirror'? ie sits on the developer/integrator's own machine?11:11
fredcadetepaulsherwood: not necessarily, it can be put in a server in the basement for example11:12
fredcadetebasically it's a bbclass and a set of variables that you can use to make your download directory a repository for all the sources11:13
fredcadetelet me see if I can find the docs11:13
paulsherwoodfredcadete: ok, i must do more reading on this.11:13
fredcadetepaulsherwood: https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_create_my_own_source_download_mirror_.3F11:13
paulsherwoodfredcadete: thanks!11:13
fredcadetepaulsherwood: it's enough for saving bandwidth and reproduceability; but it's not what you want if you also want to heavily customize the packages in a repo11:15
fredcadetepaulsherwood: no problem11:15
paulsherwoodfredcadete: the use-case i'm mainly interested in is ciat on an ongoing basis for genivi and agl11:16
paulsherwood(and other projects too)11:17
paulsherwoodthe mirror will likely be used for licence compliance, traceability, reproducibility as well as driving the builds11:19
fredcadetepaulsherwood: I'm afraid I don't have any good suggestion for that... in our internal usage of yocto we haven't yet found a very efficient way of doing ciat11:19
fredcadetepaulsherwood: the trouble has mostly been how resource usage scales with several branches11:20
paulsherwoodfredcadete: ack. i wonder if others have similar experiences11:20
fredcadetepaulsherwood: we don't have a clean way of building a topic branch without rebuilding practically the whole system11:21
fredcadeteso we do it with care11:21
paulsherwoodouch11:23
fredcadeteit may or may not be a problem depending on your available computing resources11:25
fredcadeteand the response time you want from the ciat11:25
paulsherwoodunderstood11:29
*** KlausUhl has quit IRC12:03
*** wschaller has joined #automotive12:22
gunnarxCTtpollard: Recently built minnowboard successfully as well as koelsch (not deployed and tested either of those builds though).12:43
gunnarxAccording to branches koelsch and minnowboard at: https://github.com/gunnarx/gdp-submodules/12:43
gunnarxFor koelsch we had the necessary graphics drivers. For porter, they are downloadable with click-through license. Have no porter branch there yet but maybe soon.12:45
CTtpollardgunnarx: I'm currently having a poke are you submodule repo :P12:46
CTtpollards/:p/:)12:46
gunnarxstill not a parseable sentence, but that's ok :)12:47
CTtpollardyep sorry my head was in two conversations there12:47
paulsherwoodgunnarx: this is irc, we have to make do :-)12:47
*** emaj has joined #automotive12:54
CTtpollardI think the use of the submodules suits what we need13:00
gunnarxOh, Pollard, now I made the connection...13:05
gunnarxYou have commit permission to meta-genivi-demo then, right?13:06
CTtpollardgunnarx yes13:06
gunnarxSo currently our project has forked I think 2 layers, let me know if you think I can point m-g-d towards GENIVI git again.13:07
CTtpollarddoing a recursive clone of a specific board branch through the use of submodules is imo a really clean way to do it13:08
gunnarxthanks, I think so too :)13:08
paulsherwoodgit subtrees (cough)13:08
gunnarxwhat?13:09
paulsherwoodsorry, there's an alternative to submodules, subtrees.... better in some respects iiuc13:09
* paulsherwood is on a call, half on irc13:09
paulsherwoodbut your submodules soln works, so i'm not pushing13:10
paulsherwoodjust mentioning it in passing ;)13:12
gunnarxOK, I'll check.  Submodules are indeed a little quirky.13:12
paulsherwoodhttp://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-subtree/13:15
gunnarxYes, found all that.13:15
paulsherwood:-)13:16
gunnarxI'm no fan of repo though for sure.13:16
gunnarxI should upload my unrepo program to github.  Converts a project to submodules (if I remember, it's been a while) :)13:16
CTtpollardgunnarx: the head of m-g-d builds and deploys fine to porter and qemu for me, so I'd be happy for you to point to genivi git instead of the github fork13:16
gunnarxOK good, we'll put that on a short term list...  Next is meta-ivi...13:20
*** KlausUhl has joined #automotive13:21
gunnarx"Since there’s no way to have two versions of a submodule checked out at once, it simply doesn’t try, effectively treating the entire submodule like a single binary file"13:22
gunnarx"(If you’ve ever tried to have two people working on a binary file that’s tracked in Git, you’ll have an idea of how much of a pain it is to resolve such conflicts.)"13:22
*** jeremiah has joined #automotive13:23
gunnarxNonsense, IMHO.  You need to do some supposedly unnecessary steps but you still have git supporting you when merging inside of the submodule, which is not the case for binaries.13:23
gunnarxOther than that, yes I agree all the things mentioned are indeed the problems you realize after using submodules for a while.13:24
emajj #amb14:08
*** gunnarx has quit IRC14:28
CTtpollardI've posted my thoughts about it to the projects mailing list14:36
*** felipealmeida has quit IRC15:00
*** felipealmeida has joined #automotive15:08
*** KlausUhl has left #automotive15:09
*** wschaller_ has joined #automotive15:13
CTtpollardI've tested using kvm-qemu as described here, linked from the bottom of http://wiki.projects.genivi.org/index.php/Hardware_Setup_and_Software_Installation/qemux86-6415:14
CTtpollardI think it definitely should be added to the main part of the guide, I've found that the instructions for it are already there, but hidden 'until prebuild binaries are available'15:15
CTtpollardthere is a section hidden like this for actually providing the download urls which is understandable, but I'm not sure if the kvm method also needs to be hidden for that reason?15:16
*** wschaller has quit IRC15:17
*** gunnarx has joined #automotive15:23
*** bbranch has left #automotive15:24
*** gunnarx has quit IRC15:34
*** jlrmagnus has joined #automotive15:55
*** jonathanmaw has quit IRC16:29
*** jeremiah has quit IRC16:31
*** jeremiah has joined #automotive16:33
*** jeremiah has quit IRC16:35
*** bbranch has joined #automotive16:36
*** jeremiah has joined #automotive16:37
*** mdunford has quit IRC16:48
*** wschaller_ has quit IRC16:54
*** tester1234 has joined #automotive17:29
*** jacobo has quit IRC18:29
*** myself has joined #automotive18:46
*** joone has quit IRC19:04
*** joone has joined #automotive19:07
*** jeremiah has quit IRC19:22
*** emaj has quit IRC20:38
jlrmagnusCAN Firewall presentation complete21:13
jlrmagnushttps://github.com/PDXostc/canfw/blob/master/doc/DRD_CANFW.xlsx?raw=true21:13
jlrmagnusWrong  file.21:13
jlrmagnusOne sec21:13
jlrmagnushttps://github.com/PDXostc/canfw/blob/master/doc/CAN%20Firewall.pdf21:15
jlrmagnusHardware has been sent off for production.21:16
jlrmagnusI'll add the specs.21:16
JEEB'grats21:41
myselfnot sure about the crypto math but the canb.us hardware should be able to do the rest today.21:42
rjekjlrmagnus: I noticed that RVI's build system checks stuff out at build time, and some deps are at HEAD rather than a specific hash.  My Baserock and Debian love means this makes me sad.  Can this be easily fixed?21:44
rjekOr do I have the wrong end of the stick?21:46
jlrmagnusPlease note that all directories under deps are actually a part of the rvi_core repo.21:52
jlrmagnusThe reason for this is the stupidity of GBS/OBS where the sandboxed machine does not have network access to pull deps.21:54
rjekISTR that when issuing make, things got git cloned21:54
jlrmagnus Can you dump output to pastebin?21:55
rjekWould git submodules make more sense?21:55
rjekI'm in a pub atm, not at my laptop :-)21:55
jlrmagnusPossibly. This, however, is a part of rebar, erlangs build system.21:56
rjekYeah, it was rebar21:56
jlrmagnusSeparate repos do make sense, as is, but we need to clean up the GBS build21:56
rjekthe rebar config file fills me with fear atm21:56
rjekEsp. because HEAD imports are not only very variable, they are man in rhe middleable21:57
rjekOBS makes me sad too :-)21:58
jlrmagnusWhich branch are you working on?22:19
jlrmagnusI can lock it down to specific commits fairly easily.22:19
*** jlrmagnus has left #automotive23:54

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