Re: [yocto] OpenEmbedded developer meeting Sunday before ELC in Portland
What time...a number of us are headed up from SCaLE sunday morning to ELC... its only about 2.5hrs to get there but early will leave a number of us late. T On Mon, Jan 15, 2018 at 3:41 PM, Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > > March 11, 2108, Portland > > I guess, by this date yocto community will experience release 24.7 or > similar... If?! ;-) > > Zoran > ___ > > On Mon, Jan 15, 2018 at 11:30 PM, Philip Balister> wrote: > >> We are setting up an OpenEmbedded developer meeting on the Sunday before >> ELC. More information to follow, I just wanted to make sure everyone had >> the date before making ELC travel arrangements. >> >> March 11, 2108, Portland >> >> Philip >> -- >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto >> > > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] [oe] OEDAM, April 8 in San Diego after ELC
do we have meeting minutes posted someplace? thanks tom On Mon, Apr 11, 2016 at 6:43 PM, Philip Balisterwrote: > On 04/11/2016 09:35 PM, Denys Dmytriyenko wrote: > > On Mon, Apr 11, 2016 at 03:35:21PM -0700, Rudolf J Streif wrote: > >> Hello Everyone: > >> > >> If you attended OEDAM last Friday in San Diego, I very much hope that > you enjoyed being here. > >> > >> The Catamaran Hotel, where we held the meeting, would very much > appreciate your feedback: > >> > >> www.catamaranresort.com/trip > >> > >> I hope you all had a safe trip back home, > > > > And huge thanks to Rudi and Jefro for their help in organizing the event! > > > > And an even bigger thanks to everyone that came to the meeting. You are > the people that make OpenEmbedded great! > > Philip > -- > ___ > Openembedded-core mailing list > openembedded-c...@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Controlling Bitbake Memory usage under Windows/Virtualbox/Ubuntu platform
it starts from the beginning Parses the recipies (again) and picks up where it left off.. On Sun, Mar 6, 2016 at 5:01 PM, Mark Brownwrote: > Again, how is the Bitbake module terminated and then re-run, > picking up its place in the sequence of tasks where it left off ? > > > > -- > Subject: Re: [yocto] Controlling Bitbake Memory usage under > Windows/Virtualbox/Ubuntu platform > From: opensou...@keylevel.com > Date: Sun, 6 Mar 2016 22:38:41 + > CC: yocto@yoctoproject.org > To: mkbrow...@hotmail.com > > > On 6 Mar 2016, at 22:08, Mark Brown wrote: > > > I do not see anything in the Bitbake manual for controlling how much memory > Bitbake should consider itself entitled to consume in the > development platform within which it runs. > > Running it on //Windows 7 64//i7-2620M//Virtualbox//Ubuntu 14 32-bit//, > I told Virtualbox to allow Ubuntu to use 1.5 GBytes, but Windows Task > Manager > indicates the whole Virtualbox/Ubuntu thread is using only 160 MBytes > -- and is generating approximately 1,000 page faults per second. > > > What memory usage does the Ubuntu VM report? > > Perhaps as a result, this Gumstix Overo build has completed only 760 out > of 3792 > total tasks in 21 hours -- at this rate it will complete in 5-6 days. > > > Not used a VM to build in ages, but I used to build an image from scratch > in about 10 hours running on a dual core Macbook Pro. The same build takes > about 1 hour on an 8 thread i7 with 16GB RAM and SSDs for the build work > area, peaking at about 10GB RAM usage with local.conf set to use 16 threads > and 16 parallel makes (BB_NUMBER_THREADS and PARALLEL_MAKE both at 16) - > later Yocto versions set these for you based on the number of cores > available to the build host. > > Another thing to consider - if this is the first build, then you’ll be > downloading a load of stuff from the internet. How fast is your connection? > Subsequent builds will be much quicker as the files required will then be > stored locally. > > How does the user terminate Bitbake at its current stage, increase the > memory it is using, > and then restart in order to speed up this process ? > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > > -- > > Chris Tapp > opensou...@keylevel.com > www.keylevel.com > > > You can tell you're getting older when your car insurance gets real cheap! > > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [oe] Collab Summit + ELC + TSC Meeting
I will be TK On Mon, Mar 14, 2011 at 6:15 PM, Philip Balister phi...@balister.orgwrote: On 03/14/2011 08:44 PM, Jeff Osier-Mixon wrote: There also was a request for more general purpose OEDAM over the weekend, maybe in parallel or before/after TSC meeting: Any thoughts on that? Most of the replies there are from TSC people who are going to be there with the exceptions of yourself and Mike. I'm ok with having a more general meeting if the demand is there and Jefro can arrange it. If there are only a few people, I'd suggest something like meeting after the TSC meeting and finding food/drink together. For those who don't know me, I'm Jefro. :) As Richard says, a small crowd would probably interact better over refreshments. If you are interested in such a gathering, send me a note at je...@jefro.net and let me know when you are available, and I'll see what I can pull together. A quick show of hands, how many OE people can be in San Francisco over the weekend of April 9-10? TSC people, go ahead and chime in for completeness. Philip ___ Openembedded-members mailing list openembedded-memb...@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-members ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto