*** zoli__ has joined #baserock | 01:38 | |
*** zoli__ has quit IRC | 01:43 | |
radiofree | mustang built complete armv7 devel image (jetson) in [TOTAL] Elapsed time 04:30:07 | 10:13 |
---|---|---|
radiofree | 15-08-28 17:43:10 [18/280/282] [gcc] Elapsed time for build 00:11:31 | 10:14 |
radiofree | seems pretty quick | 10:14 |
rjek | shiny | 10:14 |
radiofree | paulsherwood: regarding build assembly times for http://fpaste.org/260774/78316214/ | 10:21 |
radiofree | it doesn't seem to bear any relation to the timings for glibc | 10:21 |
radiofree | 15-08-28 17:25:06 [14/280/282] [glibc] Starting build | 10:22 |
radiofree | 15-08-28 17:30:03 [14/280/282] [glibc] Elapsed time for assembly 00:24:17 | 10:22 |
radiofree | why isn't it 4minutes 57 seconds? | 10:23 |
rjek | Perhaps it's counting CPU time not wall clock time? | 10:24 |
radiofree | ah so reading pauls answer it is the time glibc + things needed to build glibc... maybe | 10:25 |
*** zoli__ has joined #baserock | 12:04 | |
*** zoli___ has joined #baserock | 12:08 | |
*** zoli__ has quit IRC | 12:09 | |
*** zoli__ has joined #baserock | 12:12 | |
*** zoli___ has quit IRC | 12:15 | |
*** zoli__ has quit IRC | 12:24 | |
*** zoli___ has joined #baserock | 12:24 | |
*** zoli__ has joined #baserock | 12:36 | |
*** zoli___ has quit IRC | 12:36 | |
*** zoli___ has joined #baserock | 12:45 | |
*** zoli__ has quit IRC | 12:47 | |
*** zoli__ has joined #baserock | 12:52 | |
*** zoli___ has quit IRC | 12:52 | |
*** zoli___ has joined #baserock | 13:06 | |
*** zoli__ has quit IRC | 13:09 | |
*** zoli___ has quit IRC | 14:39 | |
*** zoli__ has joined #baserock | 14:42 | |
*** zoli___ has joined #baserock | 14:44 | |
*** zoli__ has quit IRC | 14:44 | |
*** zoli___ has quit IRC | 14:49 | |
paulsherwood | yup | 16:04 |
*** zoli__ has joined #baserock | 17:03 | |
*** zoli__ has quit IRC | 17:54 | |
*** zoli__ has joined #baserock | 18:13 | |
*** zoli__ has quit IRC | 18:14 | |
*** Walkerdine has joined #baserock | 18:32 | |
Walkerdine | Hello! I'm currently trying to figure out how to build my own baserock image with the genivi platform but I'm having trouble finding what I need to do so | 18:33 |
*** zoli__ has joined #baserock | 19:16 | |
*** zoli__ has quit IRC | 19:21 | |
Walkerdine | Am I not able to compile a jetson image from a x86 machine or do I need to set up a jetson to compile for the jetson? | 19:37 |
paulsherwood | Walkerdine: baserock is native only, i'm afraid | 19:58 |
Walkerdine | So I do need a jetson to compile for a jetson? | 19:59 |
paulsherwood | ideally yes | 20:00 |
radiofree | hmm.. maybe if you used ybd, and the cache was populated, you wouldn't need to use a jetson... | 20:01 |
Walkerdine | I was trying to use the chroot method but apparently thats not supported yet | 20:02 |
radiofree | nope, we don't cross compile | 20:02 |
paulsherwood | Walkerdine: are you wanting to work on ketson specifically, or something else? what's your actual target device? | 20:02 |
Walkerdine | My target is the jetson | 20:03 |
paulsherwood | ok | 20:03 |
paulsherwood | do you have one jetson or several? | 20:04 |
Walkerdine | One | 20:04 |
Walkerdine | If I need another I can get one | 20:04 |
radiofree | you can do it all on one | 20:04 |
radiofree | install the devel image on one, build the gdp, deploy to self | 20:04 |
radiofree | if you use the baserock-flash-script mentioned in the wiki you *must* use util-linux fdisk and *NOT* gnu fdisk | 20:05 |
paulsherwood | Walkerdine: it's probably actually faster working on the one, so long as you have plenty of ssd | 20:05 |
radiofree | https://www.kernel.org/pub/linux/utils/util-linux/v2.27/ | 20:05 |
Walkerdine | Yeah I got it flashed with the genivi demo image right now | 20:06 |
radiofree | ah that's good, it's a pitty i didn't make that devel image | 20:06 |
radiofree | then you wouldn't have this problem... | 20:06 |
Walkerdine | Why no support for cross compiling? How was the original image made then | 20:07 |
* radiofree feels there should be a section of the wiki explaining that | 20:08 | |
radiofree | s/of/on | 20:08 |
paulsherwood | +1 | 20:08 |
paulsherwood | the original image was built on a jetson (or maybe several) running baserock | 20:09 |
Walkerdine | I wish I had a hard drive handy so I could do that | 20:09 |
paulsherwood | how much storage on your jetson? | 20:09 |
Walkerdine | The default 16 gb | 20:09 |
paulsherwood | erk | 20:09 |
Walkerdine | Yeah its got a sata connector on it so I'll just grab a hard drive on monday | 20:10 |
paulsherwood | basically we can reduce our complexity and our delta vs upstream by staying native | 20:14 |
paulsherwood | at the cost of needing performant arm hardware for working on arm targets | 20:15 |
Walkerdine | How do I edit the source code | 20:17 |
paulsherwood | for one of the components, or for the overall integration? | 20:18 |
Walkerdine | Both | 20:18 |
Walkerdine | I have a simple goal right now of getting one of the GPIO pins to wiggle | 20:19 |
paulsherwood | radiofree would maybe be better placed to guide you | 20:20 |
paulsherwood | broadly our workflow is to do stuff directly on the board, build there, then boot into a new partition with the built changes | 20:20 |
Walkerdine | Yeah I read through how moprh is used to deploy new builds | 20:22 |
Walkerdine | I made it as far as trying to build on my computer before I realized that there is no cross compiling support | 20:22 |
paulsherwood | right. maybe you you could experiment with the workflow on your computer first, til you get storage for the board? | 20:23 |
Walkerdine | That sounds like a good idea | 20:23 |
Walkerdine | I don't know where the source is though | 20:24 |
paulsherwood | the definitions are pretty well isolated, so it's only really the bsp that's different between the jetson systems and the x86_64 | 20:24 |
paulsherwood | all the source is at git.baserock.org. when you run morph, it clones/fetches what it needs from there | 20:25 |
Walkerdine | So I can just clone the entry that says genivi demo platform? | 20:25 |
paulsherwood | what do you mean by 'entry'? | 20:27 |
Walkerdine | Sorry I'm not sure what the terminology exactly is but there is 20 pages of .git files and I don't know what I'm looking for | 20:28 |
paulsherwood | lol :) | 20:28 |
* paulsherwood takes a note that baserock is not clear enough for new user | 20:29 | |
* paulsherwood goes to work out what links will help Walkerdine best | 20:29 | |
paulsherwood | ok, do you have a laptop with kvm or virtualbox? | 20:31 |
paulsherwood | (and at least 30GB free?) | 20:31 |
paulsherwood | s/laptop/computer/ | 20:31 |
Walkerdine | I do not | 20:32 |
Walkerdine | I am on ubuntu though if that means anything | 20:33 |
paulsherwood | it does. how much free space do you have? | 20:33 |
Walkerdine | more than 30gb | 20:34 |
paulsherwood | ok | 20:34 |
paulsherwood | well the issue is that the default baserock tooling is self-hosting, so needs to be run on a baserock machine rather than ubuntu | 20:35 |
paulsherwood | hence the default instructions for x86 start by getting folks to download a virtual machine | 20:35 |
Walkerdine | Even with the chroot and doing enter-baserock? | 20:37 |
paulsherwood | ah, i'd forgotten about that | 20:37 |
paulsherwood | have you followed those instructions to setup a chroot on your system? | 20:38 |
* paulsherwood confesses he's never used the chroot | 20:38 | |
Walkerdine | Yeah I got as far as trying to build an image for my jetson but thats when I discovered I can't cross compile | 20:38 |
paulsherwood | right | 20:38 |
paulsherwood | did you setup workspace, checkout/branch definitions etc? | 20:39 |
Walkerdine | I'm pretty sure | 20:40 |
Walkerdine | I did the whole morph init geniviwork | 20:41 |
Walkerdine | morph checkout baserock:baserock/definitions baserock/james/genivi-demo-platform-0.1-rebase | 20:41 |
paulsherwood | ok, well from there you could at least try building an x86 version of the gdp? | 20:42 |
paulsherwood | the definitions will be in geniviwork/baserock/baserock/definitions | 20:43 |
paulsherwood | in there you'll find systems/genivi-demo-platform-x86_64-generic.morph | 20:44 |
Walkerdine | I'm sure it will build | 20:49 |
Walkerdine | I just want to make a custom one | 20:49 |
paulsherwood | ok, so to modify something, you edit the definitions files | 20:56 |
paulsherwood | either directly or by using morph edit | 20:57 |
Walkerdine | So there is 6 folders in the definitions folder where are the files I would be editing | 20:58 |
paulsherwood | how do you plan to 'wiggle the gpio'? | 20:59 |
paulsherwood | the files you'll be working with are probably in strata | 21:00 |
Walkerdine | I was hoping there would be a function thats called periodically so I could xor the pin | 21:00 |
paulsherwood | so the overall workflow for changing things is described at http://wiki.baserock.org/devel-with/#index9h2 | 21:02 |
* paulsherwood has to hit the sack now | 21:03 | |
Walkerdine | Okay Thank you for all the help! | 21:04 |
Walkerdine | I would have been stuck trying to figure out how to build an image from my computer forever | 21:04 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!