All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] spidev_test: new package
Date: Fri, 24 Oct 2014 17:01:00 +0300	[thread overview]
Message-ID: <20141024140100.GA2220@tarshish> (raw)
In-Reply-To: <1414155897-2687-1-git-send-email-gustavo@zacarias.com.ar>

Hi Gustavo,

On Fri, Oct 24, 2014 at 10:04:57AM -0300, Gustavo Zacarias wrote:
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
>  package/Config.in                  |  1 +
>  package/spidev_test/Config.in      | 11 +++++++++++
>  package/spidev_test/spidev_test.mk | 30 ++++++++++++++++++++++++++++++
>  3 files changed, 42 insertions(+)
>  create mode 100644 package/spidev_test/Config.in
>  create mode 100644 package/spidev_test/spidev_test.mk
> 
> diff --git a/package/Config.in b/package/Config.in
> index b0d8a80..a5d4dc9 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -85,6 +85,7 @@ endif
>  	source "package/ramsmp/Config.in"
>  	source "package/ramspeed/Config.in"
>  	source "package/rt-tests/Config.in"
> +	source "package/spidev_test/Config.in"
>  	source "package/strace/Config.in"
>  	source "package/stress/Config.in"
>  	source "package/sysprof/Config.in"
> diff --git a/package/spidev_test/Config.in b/package/spidev_test/Config.in
> new file mode 100644
> index 0000000..0fca030
> --- /dev/null
> +++ b/package/spidev_test/Config.in
> @@ -0,0 +1,11 @@
> +config BR2_PACKAGE_SPIDEV_TEST
> +	bool "spidev_test"
> +	help
> +	  SPI testing utility (using spidev driver).
> +
> +	  This package builds and installs the userspace 'spidev_test'
> +	  command. It is up to the user to ensure that the kernel
> +	  configuration has all suitable options enabled to allow a
> +	  proper operation of 'spidev_test'.
> +
> +	  https://www.kernel.org/doc/Documentation/spi/spidev_test.c
> diff --git a/package/spidev_test/spidev_test.mk b/package/spidev_test/spidev_test.mk
> new file mode 100644
> index 0000000..5662eb1
> --- /dev/null
> +++ b/package/spidev_test/spidev_test.mk
> @@ -0,0 +1,30 @@
> +################################################################################
> +#
> +# spidev_test
> +#
> +################################################################################
> +
> +# Newest version requires SPI_TX_QUAD/SPI_RX_QUAD to build

I'd add that SPI_TX_QUAD is also an ABI change to make the next line clearer.

> +# Pretty safe assumption that toolchain headers are <= runtime kernel version

This assumption should@least be documented in the help text, IMO.

> +ifeq ($(BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_15),y)
> +SPIDEV_TEST_VERSION = c2e78c34ef0bf4fa860b5fffc99c769d6ddaf52d
> +else
> +SPIDEV_TEST_VERSION = 925d16a209b40a3e7202a4f867991fb608834d36

Why not use kernel version tags, v3.14 and v3.15?

> +endif
> +SPIDEV_TEST_SITE = http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/Documentation/spi
> +SPIDEV_TEST_SOURCE = spidev_test.c?id=$(SPIDEV_TEST_VERSION)
> +
> +# Downloaded file is C source
> +SPIDEV_TEST_EXTRACT_CMDS =
> +
> +define SPIDEV_TEST_BUILD_CMDS
> +	$(TARGET_MAKE_ENV) $(TARGET_CC) $(TARGET_CFLAGS) -x c \
> +		-o $(@D)/spidev_test $(BR2_DL_DIR)/$(SPIDEV_TEST_SOURCE)
> +endef
> +
> +define SPIDEV_TEST_INSTALL_TARGET_CMDS
> +	$(INSTALL) -D -m 755 $(@D)/spidev_test \
> +		$(TARGET_DIR)/usr/sbin/spidev_test
> +endef
> +
> +$(eval $(generic-package))

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2014-10-24 14:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 13:04 [Buildroot] [PATCHv2] spidev_test: new package Gustavo Zacarias
2014-10-24 14:01 ` Baruch Siach [this message]
2014-10-24 16:36   ` Gustavo Zacarias

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=20141024140100.GA2220@tarshish \
    --to=baruch@tkos.co.il \
    --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.