From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Systemd update
Date: Mon, 16 Jul 2012 11:41:55 +0200 [thread overview]
Message-ID: <20120716114155.3b5f715f@skate> (raw)
In-Reply-To: <CA+wH294OCgYwtavEVYFUaDv1zpPPcXxEc8nDr4K_fkh2ydo9gw@mail.gmail.com>
Le Mon, 16 Jul 2012 10:32:43 +0100,
Alex Bradbury <asb@asbradbury.org> a ?crit :
> I'm interested in buildroot + the Raspberry Pi also (I'm currently
> responsible for the official Debian wheezy based images). You might
> want to have a look at
> https://github.com/nezticle/RaspberryPi-BuildRoot and feel free to
> contact me off-list if you're having problems building and booting a
> kernel (or drop by #raspberrypi-dev on Freenode).
Do you think it would be possible to submit the necessary patches to
the official Buildroot, instead of maintaining a fork? It will also
make it easier for you to maintain the support for Rasberry Pi if it is
in the mainline Buildroot version.
I am definitely interested in seeing more board/SoC-specific support in
Buildroot.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-16 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 16:08 [Buildroot] Systemd update Dmitry Golubovsky
2012-07-15 14:19 ` Diego Iastrubni
2012-07-15 17:27 ` Dmitry Golubovsky
[not found] ` <CADiAo4KwLhtG-ZpaBBSRQAeDBjKW9XCxAm00ZHUKw2NF97dEMg@mail.gmail.com>
2012-07-16 6:03 ` Diego Iastrubni
2012-07-16 9:19 ` Dmitry Golubovsky
2012-07-16 9:32 ` Alex Bradbury
2012-07-16 9:41 ` Thomas Petazzoni [this message]
2012-07-16 9:54 ` Alex Bradbury
2012-07-16 9:09 ` Maxime Ripard
2012-07-16 9:15 ` Dmitry Golubovsky
2012-07-16 9:16 ` Thomas Petazzoni
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=20120716114155.3b5f715f@skate \
--to=thomas.petazzoni@free-electrons.com \
--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