All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5] br2-ext linux-kernel-extensions support
Date: Sat, 28 Sep 2019 21:51:59 +0200	[thread overview]
Message-ID: <20190928195159.GK7274@scaer> (raw)
In-Reply-To: <20190928174937.408-1-robert.mccabe@rockwellcollins.com>

Robert, All,

On 2019-09-28 12:49 -0500, robert.mccabe at rockwellcollins.com spake thusly:
> From: "McCabe, Robert J" <robert.mccabe@rockwellcollins.com>
> 
> Allows br2-externals to inject custom code into the kernel tree.
> 
> Signed-off-by: McCabe, Robert J <robert.mccabe@rockwellcollins.com>
> ---

Acked-by: Yann E. MORIN <yann.morin.1998@free.fr>

Thanks for staying during the back-n-forth. ;-)

Regards,
Yann E. MORIN.

>  docs/manual/customize-outside-br.txt | 14 ++++++++++++++
>  linux/linux.mk                       | 13 +++++++++----
>  2 files changed, 23 insertions(+), 4 deletions(-)
> 
> diff --git a/docs/manual/customize-outside-br.txt b/docs/manual/customize-outside-br.txt
> index 7d3e2b1714..c3fe3d2b80 100644
> --- a/docs/manual/customize-outside-br.txt
> +++ b/docs/manual/customize-outside-br.txt
> @@ -219,6 +219,12 @@ BR2_ROOTFS_OVERLAY=$(BR2_EXTERNAL_BAR_42_PATH)/board/<boardname>/overlay/
>  BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE=$(BR2_EXTERNAL_BAR_42_PATH)/board/<boardname>/kernel.config
>  ----
> 
> +===== Custom linux-kernel-extensions
> +
> + Custom linux extensions (see xref:linux-kernel-ext[]) can be added by
> + storing them in the `linux/` directory at the root of your
> + br2-external tree.
> +
>  ===== Example layout
> 
>  Here is an example layout using all features of br2-external (the sample
> @@ -315,6 +321,14 @@ illustration, of course):
>    |     |$(eval $(toolchain-external-package))
>    |     `----
>    |
> +  |- linux/Config.ext.in
> +  |     |config BR2_LINUX_KERNEL_EXT_EXAMPLE_DRIVER
> +  |     |    bool "example-external-driver"
> +  |     |    help
> +  |     |      Example external driver
> +  |     |---
> +  |- linux/linux-ext-example-driver.mk
> +  |
>    |- configs/my-board_defconfig
>    |     |BR2_GLOBAL_PATCH_DIR="$(BR2_EXTERNAL_BAR_42_PATH)/patches/"
>    |     |BR2_ROOTFS_OVERLAY="$(BR2_EXTERNAL_BAR_42_PATH)/board/my-board/overlay/"
> diff --git a/linux/linux.mk b/linux/linux.mk
> index 95bde1aba5..32c0621a24 100644
> --- a/linux/linux.mk
> +++ b/linux/linux.mk
> @@ -514,14 +514,19 @@ endef
>  #
>  # Note: our package infrastructure uses the full-path of the last-scanned
>  # Makefile to determine what package we're currently defining, using the
> -# last directory component in the path. As such, including other Makefile,
> -# like below, before we call one of the *-package macro is usally not
> -# working.
> +# last directory component in the path. As such, including other Makefiles,
> +# like below, before we call one of the *-package macros usually doesn't
> +# work.
>  # However, since the files we include here are in the same directory as
>  # the current Makefile, we are OK. But this is a hard requirement: files
> -# included here *must* be in the same directory!
> +# included here *must* either be in this same directory OR within a
> +# another directory with the name "linux" (in the BR2_EXTERNAL case).
>  include $(sort $(wildcard linux/linux-ext-*.mk))
> 
> +#Import linux-kernel-extensions from externals
> +include $(sort $(wildcard $(foreach ext,$(BR2_EXTERNAL_DIRS), \
> +       $(ext)/linux/linux-ext-*.mk)))
> +
>  LINUX_PATCH_DEPENDENCIES += $(foreach ext,$(LINUX_EXTENSIONS),\
>  	$(if $(BR2_LINUX_KERNEL_EXT_$(call UPPERCASE,$(ext))),$(ext)))
> 
> --
> 2.17.1
> 

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2019-09-28 19:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-28 17:49 [Buildroot] [PATCH v5] br2-ext linux-kernel-extensions support robert.mccabe at rockwellcollins.com
2019-09-28 19:51 ` Yann E. MORIN [this message]
2019-09-28 20:13 ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2019-09-27 15:26 robert.mccabe at rockwellcollins.com
2019-09-27 18:05 ` Yann E. MORIN

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=20190928195159.GK7274@scaer \
    --to=yann.morin.1998@free.fr \
    --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.