From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3 v4] odroid-scripts: New Package.
Date: Sun, 24 Jul 2016 22:14:55 +0200 [thread overview]
Message-ID: <20160724221455.144fc50d@free-electrons.com> (raw)
In-Reply-To: <20160724163506.20024-1-daggs@gmx.com>
Hello,
On Sun, 24 Jul 2016 19:35:04 +0300, Dagg Stompler wrote:
> Signed-off-by: Dagg Stompler <daggs@gmx.com>
Thanks, I've applied with a few minor changes, see below.
> diff --git a/package/Config.in b/package/Config.in
> index 72c0be3..4529371 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -1690,6 +1690,7 @@ menu "System tools"
> source "package/ncdu/Config.in"
> source "package/numactl/Config.in"
> source "package/nut/Config.in"
> + source "package/odroid-scripts/Config.in"
I've moved to "Hardware handling" instead of "System tools".
> diff --git a/package/odroid-scripts/odroid-scripts.mk b/package/odroid-scripts/odroid-scripts.mk
> new file mode 100644
> index 0000000..34a4501
> --- /dev/null
> +++ b/package/odroid-scripts/odroid-scripts.mk
> @@ -0,0 +1,32 @@
> +################################################################################
> +#
> +# odroid-scripts
> +#
> +################################################################################
> +
> +ODROID_SCRIPTS_VERSION = a252de04562dcf8d8a4918a544b45a9e3d46d2fb
> +ODROID_SCRIPTS_SITE = $(call github,mdrjr,c2_bootini,$(ODROID_SCRIPTS_VERSION))
> +ODROID_SCRIPTS_LICENSE = unclear
> +
> +ifeq ($(BR2_PACKAGE_HAS_UDEV),y)
> + define ODROID_SCRIPTS_INSTALL_UDEV_RULES
We typically do not indent such lines.
> + $(INSTALL) -D -m 0644 $(@D)/10-odroid.rules $(TARGET_DIR)/etc/udev/rules.d/10-odroid.rules
I've split this line.
> + endef
> +endif
> +
> +define ODROID_SCRIPTS_INSTALL_TARGET_CMDS
> + $(INSTALL) -D -m 0755 $(@D)/c2_init.sh $(TARGET_DIR)/usr/sbin/odroidc2_init_fb.sh
> + $(ODROID_SCRIPTS_INSTALL_UDEV_RULES)
> +endef
> +
> +define ODROID_SCRIPTS_INSTALL_INIT_SYSTEMD
> + $(INSTALL) -D -m 0644 $(@D)/amlogic.service $(TARGET_DIR)/usr/lib/systemd/system/odroidc2_fb.service
> + mkdir -p $(TARGET_DIR)/etc/systemd/system/multi-user.target.wants
> + ln -fs ../../../../usr/lib/systemd/system/odroidc2_fb.service $(TARGET_DIR)/etc/systemd/system/multi-user.target.wants/odroidc2_fb.service
Those long lines as well.
> +endef
> +
> +define ODROID_SCRIPTS_INSTALL_INIT_SYSV
> + $(INSTALL) -D -m 0755 package/odroid-scripts/S50odroidc2_fb $(TARGET_DIR)/etc/init.d/S50odroidc2_fb
And this one as well.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-24 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-24 16:35 [Buildroot] [PATCH 1/3 v4] odroid-scripts: New Package Dagg Stompler
2016-07-24 16:35 ` [Buildroot] [PATCH 2/3] odroid: select odroid-scripts for odroidc2 defconfig Dagg Stompler
2016-07-24 20:15 ` Thomas Petazzoni
2016-07-24 16:35 ` [Buildroot] [PATCH 3/3 v5] odroid-mali: New Package Dagg Stompler
2016-07-24 20:35 ` Thomas Petazzoni
2016-07-25 17:59 ` daggs
2016-07-25 18:18 ` Thomas Petazzoni
2016-07-26 15:55 ` daggs
2016-07-24 20:14 ` Thomas Petazzoni [this message]
2016-07-25 17:55 ` [Buildroot] [PATCH 1/3 v4] odroid-scripts: " daggs
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=20160724221455.144fc50d@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.