From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Board defconfigs lacking maintainers
Date: Mon, 5 Mar 2018 13:37:13 +0100 [thread overview]
Message-ID: <20180305133713.0232b1b3@windsurf.home> (raw)
In-Reply-To: <20180305120722.GD7096@momiji>
Hello Adrian,
On Mon, 5 Mar 2018 12:07:22 +0000, Adrian Perez de Castro wrote:
> > - ci20_defconfig
>
> One if my work colleagues has a ci20 around which I *think* he has been using
> mostly with Buildroot as the base system. I'll get to him and see whether it
> may be possible for one of us to adopt this one.
Great! This defconfig was initially contributed by Vicente Olivert
Riera, but he has left Imagination Technologies, so he is no longer
working on Buildroot or MIPS.
> > - odroidc2_defconfig
>
> We have at the office a couple of Odroid C2 which I think may not be in use,
> but I do not have physical access to them (I work remotely), but I might be
> able to do something about them. I'll ask around as well.
Dagg is already working on this defconfig, is actively using the
board, and already replied that he is willing to be in the DEVELOPERS
file for this board.
> > - raspberrypi0_defconfig
> > - raspberrypi2_defconfig
> > - raspberrypi3_64_defconfig
> > - raspberrypi3_qt5we_defconfig
> > - raspberrypi_defconfig
>
> I tend use the Raspberry Pi 2/3 defconfigs whenever I bump the WebKitGTK+
> package (and recently libepoxy), and they are very popular boards. It would
> be a pity to lose those. I can help out with them, but I bet there are people
> with better knowledge about the hardware details who should be listes as
> maintainers ;-)
Yeah, I'm sure the RPi defconfigs will find one or several adopters.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-03-05 12:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 22:15 [Buildroot] Board defconfigs lacking maintainers Thomas Petazzoni
2018-03-05 7:50 ` daggs
2018-03-05 8:31 ` Thomas Petazzoni
2018-03-05 12:07 ` Adrian Perez de Castro
2018-03-05 12:37 ` Thomas Petazzoni [this message]
2018-03-07 13:41 ` Ezequiel Garcia
2018-03-07 14:04 ` Peter Korsgaard
2018-03-07 14:04 ` Thomas Petazzoni
2018-03-07 14:30 ` Ezequiel Garcia
2018-03-05 14:35 ` Luca Ceresoli
2018-03-05 14:59 ` 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=20180305133713.0232b1b3@windsurf.home \
--to=thomas.petazzoni@bootlin.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