From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Notes from the U-Boot BOF Meeting in Geneva 2012/07/12
Date: Mon, 23 Jul 2012 14:16:18 -0700 [thread overview]
Message-ID: <20120723211618.GF8985@bill-the-cat> (raw)
In-Reply-To: <20120723062015.E877D200263@gemini.denx.de>
On Mon, Jul 23, 2012 at 08:20:15AM +0200, Wolfgang Denk wrote:
> Dear Marek Vasut,
>
> In message <201207230347.31993.marex@denx.de> you wrote:
> >
> > > Yes, I know. Hmmm, maybe if every 24 hours the auto build infrastructure:
> > > - Runs a MAKEALL on the mainline repo (if any patches have been committed)
> >
> > Certainly ... it takes 16 hours to do so on my dedicated machine though (more
> > now, since I started building sparc too ;-D ). But WD has some pretty badass
> > machines that can do it really quick :-)
>
> Not nearly quick enough for all arches and all boards and and all repos...
>
> > > - All patches applied to sub-repo's (i.e. do a git-pull of each
> > > sub-repo) - If the mainline MAKEALL is clean but the 'patched' MAKEALL is
> > > not, use git bisect to identify the first patch that breaks the build
> >
> > Hm yea ... serverfarm needed here. Badass machines and badass cluster is a
> > difference ;-)
>
> Sponsors needed to pay for such a infrastructure...
>
> > You have c) twice in there (nit :) ). Still, we'd need a pretty badass
> > buildsetup for that, right? But indeed, such an algo sounds nice.
>
> I wish we had unlimited resources...
>
> But then - U-Boot is _much_ smaller than Linux, and they do not do
> anything like that, yet they manage to keep going. What are we doing
> wrong / differently?
I think it boils down to community size. There's a lot of people
building and testing random combinations. There's just not much of that
today for U-Boot.
--
Tom
next prev parent reply other threads:[~2012-07-23 21:16 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 21:30 [U-Boot] Notes from the U-Boot BOF Meeting in Geneva 2012/07/12 Detlev Zundel
2012-07-16 23:11 ` Graeme Russ
2012-07-17 10:37 ` Stefan Roese
2012-07-17 12:10 ` Graeme Russ
2012-07-17 12:15 ` Graeme Russ
2012-07-18 7:21 ` Wolfgang Denk
2012-07-18 23:37 ` Graeme Russ
2012-07-21 14:46 ` Marek Vasut
2012-07-23 1:33 ` Graeme Russ
2012-07-23 1:47 ` Marek Vasut
2012-07-23 2:07 ` Graeme Russ
2012-07-23 2:13 ` Marek Vasut
2012-07-23 7:43 ` Andy Pont
2012-07-23 6:27 ` Wolfgang Denk
2012-07-23 6:20 ` Wolfgang Denk
2012-07-23 21:16 ` Tom Rini [this message]
2012-07-23 22:15 ` Marek Vasut
[not found] ` <500DD2FA.4060800@boundarydevices.com>
2012-07-23 23:06 ` Marek Vasut
2012-07-23 23:37 ` Eric Nelson
2012-07-23 6:16 ` Wolfgang Denk
2012-07-25 19:47 ` Tom Rini
2012-07-27 14:17 ` Marek Vasut
2012-07-20 22:51 ` Tom Rini
2012-07-21 1:27 ` Marek Vasut
2012-07-21 4:28 ` Graeme Russ
2012-07-23 16:49 ` Tom Rini
2012-07-23 16:44 ` Tom Rini
2012-07-23 17:17 ` Marek Vasut
2012-07-23 17:28 ` Tom Rini
2012-07-23 18:11 ` Marek Vasut
2012-07-23 19:09 ` Tom Rini
2012-07-23 22:16 ` Marek Vasut
2012-07-18 7:41 ` Wolfgang Denk
2012-07-20 3:57 ` Mike Frysinger
2012-07-21 14:40 ` Marek Vasut
2012-07-23 20:53 ` Tom Rini
2012-07-23 22:14 ` Marek Vasut
2012-07-20 16:36 ` Kim Phillips
2012-07-20 21:09 ` Marek Vasut
2012-07-20 21:34 ` Graeme Russ
2012-07-20 21:40 ` Scott Wood
2012-07-20 22:04 ` Graeme Russ
2012-07-21 14:41 ` Marek Vasut
2013-02-18 6:55 ` Simon Glass
2013-02-18 9:59 ` Wolfgang Denk
2013-02-18 10:40 ` Graeme Russ
2013-02-18 12:39 ` Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120723211618.GF8985@bill-the-cat \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox