From: anisse at astier.eu <anisse@astier.eu>
To: buildroot@busybox.net
Subject: [Buildroot] Tesla is using Buildroot
Date: Fri, 11 May 2018 23:55:08 +0200 [thread overview]
Message-ID: <20180511215508.GA28572@jaya> (raw)
In-Reply-To: <20180511172314.28ba9f80@windsurf.home>
Hi,
On Fri, May 11, 2018 at 05:23:14PM +0200, Thomas Petazzoni wrote:
> Hello,
>
> I met a few engineers from Tesla at the Embedded Linux Conference in
> March, who told me they are using Buildroot. Now that their tree is
> publicly available online, I can share this information.
>
> Their Buildroot tree is at:
>
> https://github.com/teslamotors/buildroot
>
> Unfortunately, it looks a bit ugly in terms of commit history: just
> a few huge comments that mix tons of changes together. I was told the
> autopilot configurations are there for now, but infotainment
> configurations should be added in the near future.
>
> It's of course very nice to see Buildroot being used on board of those
> vehicles!
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
> Embedded Linux and Kernel engineering
> https://bootlin.com
I've had a quick look at what's inside. Here is what I found:
- it seems based on buildroot 2016.05, with backports from more recent
versions; but at its core it's still a 2016.05
- there are a few packages tesla-{findutils, grep, bash, gzip, which, rsync}
that are here with old versions to work around GPLv3
- there's a tesla-verity package which seems to be a custom init that
checks the validity of the verity metadata and interacts with
firmware to check soc lock status before calling dmsetup.
- there are a few packages that look like backports: python-dateutil,
nanomsg, python-pytz, python-jsonschema
- tesla-binutils is a "real" host binutils (non-cross)
- there's tesla-libsystemd stub that builds a libsystemd with stubbed
functions
- it has its own parallel building infrastructure, using the loglinear
tool, first introduced in google fiber's buildroot implementation
https://gfiber.googlesource.com/buildroot/
- many packages are patched to modify behaviour, customize build
options: business as usual
- probably many things I've missed
I've added Olof in cc.
Regards,
Anisse
next prev parent reply other threads:[~2018-05-11 21:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 15:23 [Buildroot] Tesla is using Buildroot Thomas Petazzoni
2018-05-11 21:55 ` anisse at astier.eu [this message]
2018-05-12 1:22 ` ratbert90
2018-05-12 1:42 ` Carlos Santos
2018-05-12 13:27 ` Adrian Perez de Castro
2018-05-12 16:34 ` Adam Duskett
2018-05-12 17:06 ` Joseph Kogut
2018-05-12 17:51 ` Olof Johansson
2018-05-14 18:00 ` Trent Piepho
2018-05-15 20:18 ` Arnout Vandecappelle
2018-05-19 11:08 ` Angelo Compagnucci
2018-05-22 7:51 ` Andreas Naumann
2018-05-22 17:40 ` Trent Piepho
2018-05-12 18:16 ` Olof Johansson
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=20180511215508.GA28572@jaya \
--to=anisse@astier.eu \
--cc=buildroot@busybox.net \
/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