From: David Lechner <david@lechnology.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] configs/lego_ev3_defconfig: enable brickd by default
Date: Fri, 22 Feb 2019 19:04:54 -0600 [thread overview]
Message-ID: <20190223010454.7335-2-david@lechnology.com> (raw)
In-Reply-To: <20190223010454.7335-1-david@lechnology.com>
This enables the brickd package by default on LEGO MINDSTORM EV3. This
program is important because it shuts down the system on low battery.
Without this, rechargeable batteries could be damaged.
Signed-off-by: David Lechner <david@lechnology.com>
---
configs/lego_ev3_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/configs/lego_ev3_defconfig b/configs/lego_ev3_defconfig
index cf2809059e..b4a1000036 100644
--- a/configs/lego_ev3_defconfig
+++ b/configs/lego_ev3_defconfig
@@ -8,6 +8,7 @@ BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
# system
BR2_TARGET_GENERIC_GETTY=y
BR2_TARGET_GENERIC_GETTY_PORT="ttyS1"
+BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y
BR2_ROOTFS_POST_IMAGE_SCRIPT="board/lego/ev3/post-image.sh"
# Linux headers same as kernel, a 4.19 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_19=y
@@ -27,6 +28,7 @@ BR2_LINUX_KERNEL_INTREE_DTS_NAME="da850-lego-ev3"
BR2_PACKAGE_BUSYBOX_CONFIG_FRAGMENT_FILES="board/lego/ev3/busybox.fragment"
BR2_PACKAGE_BLUEZ5_UTILS=y
BR2_PACKAGE_BLUEZ5_UTILS_CLIENT=y
+BR2_PACKAGE_BRICKD=y
BR2_PACKAGE_LINUX_FIRMWARE=y
BR2_PACKAGE_LINUX_FIRMWARE_TI_CC2560=y
--
2.17.1
next prev parent reply other threads:[~2019-02-23 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 1:04 [Buildroot] [PATCH 1/2] package/brickd: new package David Lechner
2019-02-23 1:04 ` David Lechner [this message]
2019-03-26 21:26 ` [Buildroot] [PATCH 2/2] configs/lego_ev3_defconfig: enable brickd by default Thomas Petazzoni
2019-03-26 21:26 ` [Buildroot] [PATCH 1/2] package/brickd: new package 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=20190223010454.7335-2-david@lechnology.com \
--to=david@lechnology.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