[Buildroot] Board defconfigs lacking maintainers

[Buildroot] Board defconfigs lacking maintainers

[Thomas Petazzoni]

Hello,

A significant number of our defconfigs don't have anyone in charge of
them according to the DEVELOPERS file.

If you are interested in one of the below defconfigs, could you please
send an update to the DEVELOPERS file to add yourself? Defconfigs not
associated to any developer are likely to be dropped at some point in
the future, since they will most likely fail to build due to toolchain
updates, and nobody will be there to fix those issues.

Here is the complete list of defconfigs that aren't associated to
anybody in the DEVELOPERS file:

 - arcturus_ucp1020_defconfig
 - arm_foundationv8_defconfig
 - arm_juno_defconfig
 - beagleboardx15_defconfig
 - beaglebone_defconfig
 - beaglebone_qt5_defconfig
 - chromebook_snow_defconfig
 - ci20_defconfig
 - ci40_defconfig
 - cubieboard2_defconfig
 - firefly_rk3288_defconfig
 - firefly_rk3288_demo_defconfig
 - freescale_p1010rdb_pa_defconfig
 - galileo_defconfig
 - gdb_bfin_bf512_defconfig
 - imx23evk_defconfig
 - imx6-sabreauto_defconfig
 - imx7dpico_defconfig
 - minnowboard_max_defconfig
 - minnowboard_max-graphical_defconfig
 - mx25pdk_defconfig
 - mx51evk_defconfig
 - mx53loco_defconfig
 - nanopi_neo_defconfig
 - nexbox_a95x_defconfig
 - odroidc2_defconfig
 - olimex_imx233_olinuxino_defconfig
 - openblocks_a6_defconfig
 - pandaboard_defconfig
 - qemu_aarch64_virt_defconfig
 - qemu_arm_versatile_defconfig
 - qemu_arm_versatile_nommu_defconfig
 - qemu_arm_vexpress_defconfig
 - qemu_m68k_mcf5208_defconfig
 - qemu_m68k_q800_defconfig
 - qemu_microblazebe_mmu_defconfig
 - qemu_microblazeel_mmu_defconfig
 - qemu_mips32r2el_malta_defconfig
 - qemu_mips32r2_malta_defconfig
 - qemu_mips32r6el_malta_defconfig
 - qemu_mips32r6_malta_defconfig
 - qemu_mips64el_malta_defconfig
 - qemu_mips64_malta_defconfig
 - qemu_mips64r6el_malta_defconfig
 - qemu_mips64r6_malta_defconfig
 - qemu_nios2_10m50_defconfig
 - qemu_or1k_defconfig
 - qemu_ppc64_pseries_defconfig
 - qemu_ppc_g3beige_defconfig
 - qemu_ppc_mpc8544ds_defconfig
 - qemu_ppc_virtex_ml507_defconfig
 - qemu_sh4eb_r2d_defconfig
 - qemu_sh4_r2d_defconfig
 - qemu_sparc64_sun4u_defconfig
 - qemu_sparc_ss10_defconfig
 - qemu_x86_64_defconfig
 - qemu_x86_defconfig
 - qemu_xtensa_lx60_defconfig
 - qemu_xtensa_lx60_nommu_defconfig
 - raspberrypi0_defconfig
 - raspberrypi2_defconfig
 - raspberrypi3_64_defconfig
 - raspberrypi3_qt5we_defconfig
 - raspberrypi_defconfig
 - riotboard_defconfig
 - roseapplepi_defconfig
 - s6lx9_microboard_defconfig
 - sheevaplug_defconfig
 - snps_aarch64_vdk_defconfig
 - snps_arc700_axs101_defconfig
 - snps_archs38_axs103_defconfig
 - snps_archs38_haps_defconfig
 - snps_archs38_vdk_defconfig
 - stm32f429_disco_defconfig
 - stm32f469_disco_defconfig
 - telit_evk_pro3_defconfig
 - toradex_apalis_imx6_defconfig
 - ts4800_defconfig
 - ts5x00_defconfig
 - ts7680_defconfig
 - warpboard_defconfig
 - zynq_microzed_defconfig
 - zynq_zc706_defconfig
 - zynq_zed_defconfig
 - zynq_zybo_defconfig

Thanks for your participation!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com

[Buildroot] Board defconfigs lacking maintainers

[daggs]

Greetings Thomas,

> Sent: Monday, March 05, 2018 at 12:15 AM
> From: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
> To: "buildroot at uclibc.org" <buildroot@uclibc.org>
> Subject: [Buildroot] Board defconfigs lacking maintainers
>
> Hello,
> 
> A significant number of our defconfigs don't have anyone in charge of
> them according to the DEVELOPERS file.
> 
> If you are interested in one of the below defconfigs, could you please
> send an update to the DEVELOPERS file to add yourself? Defconfigs not
> associated to any developer are likely to be dropped at some point in
> the future, since they will most likely fail to build due to toolchain
> updates, and nobody will be there to fix those issues.
> 
> Here is the complete list of defconfigs that aren't associated to
> anybody in the DEVELOPERS file:
> 
>  - arcturus_ucp1020_defconfig
>  - arm_foundationv8_defconfig
>  - arm_juno_defconfig
>  - beagleboardx15_defconfig
>  - beaglebone_defconfig
>  - beaglebone_qt5_defconfig
>  - chromebook_snow_defconfig
>  - ci20_defconfig
>  - ci40_defconfig
>  - cubieboard2_defconfig
>  - firefly_rk3288_defconfig
>  - firefly_rk3288_demo_defconfig
>  - freescale_p1010rdb_pa_defconfig
>  - galileo_defconfig
>  - gdb_bfin_bf512_defconfig
>  - imx23evk_defconfig
>  - imx6-sabreauto_defconfig
>  - imx7dpico_defconfig
>  - minnowboard_max_defconfig
>  - minnowboard_max-graphical_defconfig
>  - mx25pdk_defconfig
>  - mx51evk_defconfig
>  - mx53loco_defconfig
>  - nanopi_neo_defconfig
>  - nexbox_a95x_defconfig
>  - odroidc2_defconfig
>  - olimex_imx233_olinuxino_defconfig
>  - openblocks_a6_defconfig
>  - pandaboard_defconfig
>  - qemu_aarch64_virt_defconfig
>  - qemu_arm_versatile_defconfig
>  - qemu_arm_versatile_nommu_defconfig
>  - qemu_arm_vexpress_defconfig
>  - qemu_m68k_mcf5208_defconfig
>  - qemu_m68k_q800_defconfig
>  - qemu_microblazebe_mmu_defconfig
>  - qemu_microblazeel_mmu_defconfig
>  - qemu_mips32r2el_malta_defconfig
>  - qemu_mips32r2_malta_defconfig
>  - qemu_mips32r6el_malta_defconfig
>  - qemu_mips32r6_malta_defconfig
>  - qemu_mips64el_malta_defconfig
>  - qemu_mips64_malta_defconfig
>  - qemu_mips64r6el_malta_defconfig
>  - qemu_mips64r6_malta_defconfig
>  - qemu_nios2_10m50_defconfig
>  - qemu_or1k_defconfig
>  - qemu_ppc64_pseries_defconfig
>  - qemu_ppc_g3beige_defconfig
>  - qemu_ppc_mpc8544ds_defconfig
>  - qemu_ppc_virtex_ml507_defconfig
>  - qemu_sh4eb_r2d_defconfig
>  - qemu_sh4_r2d_defconfig
>  - qemu_sparc64_sun4u_defconfig
>  - qemu_sparc_ss10_defconfig
>  - qemu_x86_64_defconfig
>  - qemu_x86_defconfig
>  - qemu_xtensa_lx60_defconfig
>  - qemu_xtensa_lx60_nommu_defconfig
>  - raspberrypi0_defconfig
>  - raspberrypi2_defconfig
>  - raspberrypi3_64_defconfig
>  - raspberrypi3_qt5we_defconfig
>  - raspberrypi_defconfig
>  - riotboard_defconfig
>  - roseapplepi_defconfig
>  - s6lx9_microboard_defconfig
>  - sheevaplug_defconfig
>  - snps_aarch64_vdk_defconfig
>  - snps_arc700_axs101_defconfig
>  - snps_archs38_axs103_defconfig
>  - snps_archs38_haps_defconfig
>  - snps_archs38_vdk_defconfig
>  - stm32f429_disco_defconfig
>  - stm32f469_disco_defconfig
>  - telit_evk_pro3_defconfig
>  - toradex_apalis_imx6_defconfig
>  - ts4800_defconfig
>  - ts5x00_defconfig
>  - ts7680_defconfig
>  - warpboard_defconfig
>  - zynq_microzed_defconfig
>  - zynq_zc706_defconfig
>  - zynq_zed_defconfig
>  - zynq_zybo_defconfig
> 
> Thanks for your participation!
> 
> Thomas

I was under the impression I'm maintaining the odroidc2 board, did to got changed?
the config didn't got updated lately because I'm focusing on the mainline support (see patches pending).
regardless, I'll make a pass on the vendor's repo to see if there are any updates.

Dagg.

[Buildroot] Board defconfigs lacking maintainers

[Thomas Petazzoni]

Hello,

On Mon, 5 Mar 2018 08:50:30 +0100, daggs wrote:

> I was under the impression I'm maintaining the odroidc2 board, did to got changed?

Well, the DEVELOPERS file doesn't have any entry that links your
name/email to configs/odroidc2_defconfig.

If you want to maintain the board, could you send a patch updating the
DEVELOPERS file accordingly ?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com

[Buildroot] Board defconfigs lacking maintainers

[Adrian Perez de Castro]

Hello everybody,

On Sun, 4 Mar 2018 23:15:47 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
 
> A significant number of our defconfigs don't have anyone in charge of
> them according to the DEVELOPERS file.
> 
> If you are interested in one of the below defconfigs, could you please
> send an update to the DEVELOPERS file to add yourself? Defconfigs not
> associated to any developer are likely to be dropped at some point in
> the future, since they will most likely fail to build due to toolchain
> updates, and nobody will be there to fix those issues.
> 
> Here is the complete list of defconfigs that aren't associated to
> anybody in the DEVELOPERS file:
> 
>  - arcturus_ucp1020_defconfig
>  - arm_foundationv8_defconfig
>  - arm_juno_defconfig
>  - beagleboardx15_defconfig
>  - beaglebone_defconfig
>  - beaglebone_qt5_defconfig
>  - chromebook_snow_defconfig
>  - 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.

>  - ci40_defconfig
>  - cubieboard2_defconfig
>  - firefly_rk3288_defconfig
>  - firefly_rk3288_demo_defconfig
>  - freescale_p1010rdb_pa_defconfig
>  - galileo_defconfig
>  - gdb_bfin_bf512_defconfig
>  - imx23evk_defconfig
>  - imx6-sabreauto_defconfig
>  - imx7dpico_defconfig
>  - minnowboard_max_defconfig
>  - minnowboard_max-graphical_defconfig
>  - mx25pdk_defconfig
>  - mx51evk_defconfig
>  - mx53loco_defconfig
>  - nanopi_neo_defconfig
>  - nexbox_a95x_defconfig
>  - 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.

>  - olimex_imx233_olinuxino_defconfig
>  - openblocks_a6_defconfig
>  - pandaboard_defconfig

I have a Pandaboard in storage, which I will get back by June. After that I
could probably take over this defconfig.

That being said, I do not have much interest in toying with it, so if somebody
else would commit to maintaining Buildroot on the Pandaboard I would happily
consider donating it to someone in the Finland or the EU ? send me an e-mail
off-list if you are interested.

>  - qemu_aarch64_virt_defconfig
>  - qemu_arm_versatile_defconfig
>  - qemu_arm_versatile_nommu_defconfig
>  - qemu_arm_vexpress_defconfig
>  - qemu_m68k_mcf5208_defconfig
>  - qemu_m68k_q800_defconfig
>  - qemu_microblazebe_mmu_defconfig
>  - qemu_microblazeel_mmu_defconfig
>  - qemu_mips32r2el_malta_defconfig
>  - qemu_mips32r2_malta_defconfig
>  - qemu_mips32r6el_malta_defconfig
>  - qemu_mips32r6_malta_defconfig
>  - qemu_mips64el_malta_defconfig
>  - qemu_mips64_malta_defconfig
>  - qemu_mips64r6el_malta_defconfig
>  - qemu_mips64r6_malta_defconfig
>  - qemu_nios2_10m50_defconfig
>  - qemu_or1k_defconfig
>  - qemu_ppc64_pseries_defconfig
>  - qemu_ppc_g3beige_defconfig
>  - qemu_ppc_mpc8544ds_defconfig
>  - qemu_ppc_virtex_ml507_defconfig
>  - qemu_sh4eb_r2d_defconfig
>  - qemu_sh4_r2d_defconfig
>  - qemu_sparc64_sun4u_defconfig
>  - qemu_sparc_ss10_defconfig
>  - qemu_x86_64_defconfig
>  - qemu_x86_defconfig
>  - qemu_xtensa_lx60_defconfig
>  - qemu_xtensa_lx60_nommu_defconfig
>  - 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 ;-)

>  - riotboard_defconfig
>  - roseapplepi_defconfig
>  - s6lx9_microboard_defconfig
>  - sheevaplug_defconfig

The Sheevaplug configuration should also work for the GuruPlug, right? I also
have a GuruPlug in storage which I would be happy to donate if somebody is
interested.

>  - snps_aarch64_vdk_defconfig
>  - snps_arc700_axs101_defconfig
>  - snps_archs38_axs103_defconfig
>  - snps_archs38_haps_defconfig
>  - snps_archs38_vdk_defconfig
>  - stm32f429_disco_defconfig
>  - stm32f469_disco_defconfig
>  - telit_evk_pro3_defconfig
>  - toradex_apalis_imx6_defconfig
>  - ts4800_defconfig
>  - ts5x00_defconfig
>  - ts7680_defconfig
>  - warpboard_defconfig
>  - zynq_microzed_defconfig
>  - zynq_zc706_defconfig
>  - zynq_zed_defconfig
>  - zynq_zybo_defconfig
> 
> Thanks for your participation!

Best regards,


--
 Adri?n ?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180305/09f3c6a7/attachment.asc>

[Buildroot] Board defconfigs lacking maintainers

[Thomas Petazzoni]

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

[Buildroot] Board defconfigs lacking maintainers

[Ezequiel Garcia]

On 5 March 2018 at 09:37, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> 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.
>

Should nobody adopt Ci20, I will. I'm working on it as pet project.
-- 
Ezequiel Garc?a, VanguardiaSur
www.vanguardiasur.com.ar

[Buildroot] Board defconfigs lacking maintainers

[Peter Korsgaard]

>>>>> "Ezequiel" == Ezequiel Garcia <ezequiel@vanguardiasur.com.ar> writes:

Hi,

 >> 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.
 >> 

 > Should nobody adopt Ci20, I will. I'm working on it as pet project.

Great. I also do have a ci20, but haven't really done anything with it.

-- 
Bye, Peter Korsgaard

[Buildroot] Board defconfigs lacking maintainers

[Thomas Petazzoni]

Hello,

On Wed, 7 Mar 2018 10:41:37 -0300, Ezequiel Garcia wrote:

> >> 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.
> >  
> 
> Should nobody adopt Ci20, I will. I'm working on it as pet project.

Please submit a patch to the DEVELOPERS file then :-)

The ci20_defconfig build is currently broken, due to MIPS gcc flags
issues. A patch has been submitted, but we haven't merged it yet.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com

[Buildroot] Board defconfigs lacking maintainers

[Ezequiel Garcia]

On 7 March 2018 at 11:04, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Hello,
>
> On Wed, 7 Mar 2018 10:41:37 -0300, Ezequiel Garcia wrote:
>
>> >> 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.
>> >
>>
>> Should nobody adopt Ci20, I will. I'm working on it as pet project.
>
> Please submit a patch to the DEVELOPERS file then :-)
>

I will.

> The ci20_defconfig build is currently broken, due to MIPS gcc flags
> issues. A patch has been submitted, but we haven't merged it yet.
>

I know. I pinged you ages ago.
-- 
Ezequiel Garc?a, VanguardiaSur
www.vanguardiasur.com.ar

[Buildroot] Board defconfigs lacking maintainers

[Luca Ceresoli]

Hi,

On 04/03/2018 23:15, Thomas Petazzoni wrote:
> Hello,
> 
> A significant number of our defconfigs don't have anyone in charge of
> them according to the DEVELOPERS file.
> 
> If you are interested in one of the below defconfigs, could you please
> send an update to the DEVELOPERS file to add yourself? Defconfigs not
> associated to any developer are likely to be dropped at some point in
> the future, since they will most likely fail to build due to toolchain
> updates, and nobody will be there to fix those issues.

What is required exactly to be considered a board maintainer? Ensure
that it builds, or that it boots? I could take over the zynq boards, but
I have access only to some and only at spots so I cannot always ensure
they all boot.

Bye,
-- 
Luca

[Buildroot] Board defconfigs lacking maintainers

[Thomas Petazzoni]

Hello,

On Mon, 5 Mar 2018 15:35:27 +0100, Luca Ceresoli wrote:

> > If you are interested in one of the below defconfigs, could you please
> > send an update to the DEVELOPERS file to add yourself? Defconfigs not
> > associated to any developer are likely to be dropped at some point in
> > the future, since they will most likely fail to build due to toolchain
> > updates, and nobody will be there to fix those issues.  
> 
> What is required exactly to be considered a board maintainer? Ensure
> that it builds, or that it boots?

We don't have super strict rules. But defconfigs are meant to provide a
ready-to-use initial configuration. So if the configuration is not
ready-to-use because it doesn't boot, it isn't very useful.

So, IMO, we should only have defconfigs that are boot tested by someone.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com