Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] linux: add ev3dev extension
Date: Tue, 1 Nov 2016 16:09:57 +0100	[thread overview]
Message-ID: <20161101160957.3db26646@free-electrons.com> (raw)
In-Reply-To: <1477870346-4941-4-git-send-email-david@lechnology.com>

Hello,

On Sun, 30 Oct 2016 18:32:25 -0500, David Lechner wrote:
> This adds an ev3dev extension that provides linux kernel drivers for LEGO
> MINDSTORMS EV3 from the ev3dev project.
> 
> Signed-off-by: David Lechner <david@lechnology.com>

This all looks mostly good, I only have a few minor comments.

The first one is about the naming: ev3dev is really the name of the
overall project/organization, so I think the package should rather be
named ev3dev-lego-linux or ev3dev-lego-linux-drivers or
ev3dev-linux-drivers or something like this. Of course, this applies to
both the package itself and the corresponding Linux extension.


> diff --git a/linux/linux-ext-ev3dev.mk b/linux/linux-ext-ev3dev.mk
> new file mode 100644
> index 0000000..23e4c8d
> --- /dev/null
> +++ b/linux/linux-ext-ev3dev.mk
> @@ -0,0 +1,13 @@
> +################################################################################
> +# Linux ev3dev extensions
> +#
> +# Patch the linux kernel with ev3dev extension
> +################################################################################
> +
> +LINUX_EXTENSIONS += ev3dev
> +
> +define EV3DEV_PREPARE_KERNEL
> +	dest=drivers/lego ; \
> +	mkdir -p $(LINUX_DIR)/$${dest}; \
> +	cp -dpfr $(EV3DEV_DIR)/* $(LINUX_DIR)/$${dest}/

I'm not sure using a variable for $${dest} is really useful since there
are only two instances, but if you really want to do so, please use a
make variable. Maybe:

EV3DEV_LINUX_DRIVER_DIR = $(LINUX_DIR)/drivers/lego/

define EV3DEV_PREPARE_KERNEL
	mkdir -p $(EV3DEV_LINUX_DRIVER_DIR)
	cp -dpfr $(EV3DEV_DIR)/* $(EV3DEV_LINUX_DRIVER_DIR)
endef

or something along those lines.


> +config BR2_PACKAGE_EV3DEV
> +	bool
> +	depends on BR2_LINUX_KERNEL
> +	help
> +	  Linux drivers for LEGO MINDSTORMS EV3
> +
> +	  This is only the download helper for the kernel patch.

kernel extension

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-11-01 15:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-30 23:32 [Buildroot] [PATCH 0/4] LEGO MINDSTORMS EV3 Updates David Lechner
2016-10-30 23:32 ` [Buildroot] [PATCH 1/4] configs/lego_ev3: add U-Boot support David Lechner
2016-11-01 15:02   ` Thomas Petazzoni
2016-10-30 23:32 ` [Buildroot] [PATCH 2/4] board/lego/ev3: Create images using genimage David Lechner
2016-10-31  4:19   ` Baruch Siach
2016-10-31 15:57     ` David Lechner
2016-11-01 15:04   ` Thomas Petazzoni
2016-11-01 18:54   ` [Buildroot] <DKIM> " Vincent Stehlé
2016-10-30 23:32 ` [Buildroot] [PATCH 3/4] linux: add ev3dev extension David Lechner
2016-11-01 15:09   ` Thomas Petazzoni [this message]
2016-10-30 23:32 ` [Buildroot] [PATCH 4/4] board/lego/ev3: Use ev3dev linux ext for ev3dev drivers David Lechner
2016-11-01 15:10   ` 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=20161101160957.3db26646@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox