New: [Config file] New device: Odroid-U2/U3

https://bugs.busybox.net/show_bug.cgi?id=9256

Bug ID: 9256
Summary: [Config file] New device: Odroid-U2/U3
Product: buildroot
Version: 2016.08
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: qlb1234 at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---

Hi. Here's a config file for Hardkernel's Odroid-U2 and Odroid-U3. They're software compatible.

Name suggestion: odroidu2_defconfig

# Target
BR2_arm=y
BR2_cortex_a9=y
BR2_ARM_ENABLE_NEON=y
BR2_ARM_ENABLE_VFP=y
BR2_ARM_FPU_VFPV3=y

# Toolchain
BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
BR2_BINUTILS_VERSION_2_26_X=y
BR2_GCC_VERSION_6_X=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y

# Kernel
BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_DEFCONFIG="exynos" BR2_LINUX_KERNEL_DTS_SUPPORT=y BR2_LINUX_KERNEL_INTREE_DTS_NAME="exynos4412-odroidu3"

# Bootloader
BR2_TARGET_UBOOT=y
BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
BR2_TARGET_UBOOT_BOARD_DEFCONFIG="odroid"
BR2_TARGET_UBOOT_NEEDS_DTC=y

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=9256

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #1 from Thomas Petazzoni <[email protected]> --- Thanks a lot. Could you instead submit a patch to the Buildroot mailing list? See https://buildroot.org/downloads/manual/manual.html#submitting-patches for some guidelines.

Compared to your proposal, we would need:

- Keep the default toolchain configuration (i.e don't select glibc, binutils
2.26, gcc 6 and C++ support)

- Use a fixed version for the kernel and u-boot, so that the defconfig is
reproducible

- Add a readme.txt in board/ to detail how to use the defconfig.

Thanks!

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=9256

--- Comment #2 from Wesley Chan <[email protected]> --- Dear Thomas,

Thank you for your suggestion. However, I decided I don't want to submit the patch to the mailing list for the following reasons:

1. I was subscribed to the mailing list in before and sent my config file. Not only no one has replied, I got tons of mails discussing all kinds of bugs that I don't care.

2. I don't want to be disrespectful and put a fake e-mail address on the commit history, yet I don't want my real e-mail address on it.

3. I can follow the instructions to create a patch but I have zero experience about the Buildroot project, so I'm afraid I won't be providing a patch with 100% correctness on the format your team demands. I don't want to go back and forth for a tiny enhancement.

I still want to contribute, but not in an engaged way. I think it's the best for me to just leave the config file and readme.txt here. Please tell me if your team still wants it. Thanks.

Regards,

You are receiving this mail because:
You are on the CC list for the bug.