From: Denys Dmytriyenko <denys@ti.com>
To: "Franklin S. Cooper Jr" <fcooper@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH] sitara-linux-ti-staging: Create recipe for Sitara 3.14 kernel tree
Date: Wed, 14 Jan 2015 16:02:13 -0500 [thread overview]
Message-ID: <20150114210213.GM4759@edge> (raw)
In-Reply-To: <1421268209-24159-1-git-send-email-fcooper@ti.com>
Franklin,
Isn't it heavy-handed? How many changes on top do you foresee you'd need? Have
you considered doing those changes (patches or configs) inside the recipe
itself?
--
Denys
On Wed, Jan 14, 2015 at 02:43:29PM -0600, Franklin S. Cooper Jr wrote:
> From: "Franklin S. Cooper Jr" <fcooper@ti.com>
>
> * The Sitara 3.14 Kernel tree is based on the linux-ti-staging_3.14 recipe and
> kernel. However, the tree includes additional patches and configs.
> * This tree is only meant for AM335x and AM437x
>
> Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
> ---
> .../linux/sitara-linux-ti-staging-3.14/defconfig | 1 +
> ...ing_3.14.bb => sitara-linux-ti-staging_3.14.bb} | 23 ++++----------------
> 2 files changed, 5 insertions(+), 19 deletions(-)
> create mode 100644 recipes-kernel/linux/sitara-linux-ti-staging-3.14/defconfig
> copy recipes-kernel/linux/{linux-ti-staging_3.14.bb => sitara-linux-ti-staging_3.14.bb} (58%)
>
> diff --git a/recipes-kernel/linux/sitara-linux-ti-staging-3.14/defconfig b/recipes-kernel/linux/sitara-linux-ti-staging-3.14/defconfig
> new file mode 100644
> index 0000000..98c4069
> --- /dev/null
> +++ b/recipes-kernel/linux/sitara-linux-ti-staging-3.14/defconfig
> @@ -0,0 +1 @@
> +use-kernel-config=singlecore-omap2plus_defconfig
> diff --git a/recipes-kernel/linux/linux-ti-staging_3.14.bb b/recipes-kernel/linux/sitara-linux-ti-staging_3.14.bb
> similarity index 58%
> copy from recipes-kernel/linux/linux-ti-staging_3.14.bb
> copy to recipes-kernel/linux/sitara-linux-ti-staging_3.14.bb
> index d762be8..f9c4641 100644
> --- a/recipes-kernel/linux/linux-ti-staging_3.14.bb
> +++ b/recipes-kernel/linux/sitara-linux-ti-staging_3.14.bb
> @@ -20,46 +20,31 @@ RDEPENDS_kernel-base += "kernel-devicetree"
> RDEPENDS_kernel-base_append_ti33x = " am33x-cm3"
> RDEPENDS_kernel-base_append_ti43x = " am33x-cm3"
>
> -# Add a run-time dependency for the VPE VPDMA firmware to be installed
> -# on the target file system.
> -RDEPENDS_kernel-base_append_dra7xx = " vpe-vpdma-fw"
>
> # Default is to package all dtb files for ti33x devices unless building
> # for the specific beaglebone machine.
> KERNEL_DEVICETREE_ti33x = "am335x-evm.dtb am335x-evmsk.dtb am335x-bone.dtb am335x-boneblack.dtb"
> KERNEL_DEVICETREE_ti43x = "am43x-epos-evm.dtb am43x-epos-evm-hdmi.dtb am437x-gp-evm.dtb am437x-gp-evm-hdmi.dtb am437x-sk-evm.dtb"
> KERNEL_DEVICETREE_beaglebone = "am335x-bone.dtb am335x-boneblack.dtb"
> -KERNEL_DEVICETREE_omap5-evm = "omap5-uevm.dtb"
> -KERNEL_DEVICETREE_dra7xx = "dra7-evm.dtb dra7-evm-lcd7.dtb dra7-evm-lcd10.dtb dra72-evm.dtb dra72-evm-lcd7.dtb dra72-evm-lcd10.dtb am57xx-beagle-x15.dtb"
> -KERNEL_DEVICETREE_am57xx-evm = "am57xx-beagle-x15.dtb"
> -KERNEL_DEVICETREE_omap3 = "omap3-beagle.dtb omap3-beagle-xm.dtb omap3-evm.dtb omap3-evm-37xx.dtb am3517-evm.dtb"
> -KERNEL_DEVICETREE_am3517-evm = "am3517-evm.dtb"
> -KERNEL_DEVICETREE_am37x-evm = "omap3-evm-37xx.dtb"
> -KERNEL_DEVICETREE_beagleboard = "omap3-beagle.dtb omap3-beagle-xm.dtb"
>
> KERNEL_EXTRA_ARGS += "LOADADDR=${UBOOT_ENTRYPOINT}"
>
> -COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|omap3"
> +COMPATIBLE_MACHINE = "ti33x|ti43x"
>
> S = "${WORKDIR}/git"
>
> -BRANCH = "ti-linux-3.14.y"
> +BRANCH = "sitara-ti-linux-3.14.y"
>
> -SRCREV = "7828f3b4cb26fa9c978aa96cc46cca8521957f24"
> +SRCREV = "2d7148a3a95a2811604611f6c66a8826a61b8b12"
> PV = "3.14.26"
>
> # Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause a rebuild
> MACHINE_KERNEL_PR_append = "f+gitr${SRCPV}"
> PR = "${MACHINE_KERNEL_PR}"
>
> -KERNEL_CONFIG_DIR = "${S}/ti_config_fragments"
> -
> -KERNEL_CONFIG_FRAGMENTS_append_ti33x = " ${KERNEL_CONFIG_DIR}/am33xx_only.cfg"
> -KERNEL_CONFIG_FRAGMENTS_append_ti43x = " ${KERNEL_CONFIG_DIR}/am43xx_only.cfg"
> -
> MULTI_CONFIG_BASE_SUFFIX = ""
>
> -KERNEL_GIT_URI = "git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git"
> +KERNEL_GIT_URI = "git://git.ti.com/sitara-linux/sitara-linux.git"
> KERNEL_GIT_PROTOCOL = "git"
> SRC_URI += "${KERNEL_GIT_URI};protocol=${KERNEL_GIT_PROTOCOL};branch=${BRANCH} \
> file://defconfig \
> --
> 1.7.9.5
>
> --
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
next prev parent reply other threads:[~2015-01-14 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 20:43 [PATCH] sitara-linux-ti-staging: Create recipe for Sitara 3.14 kernel tree Franklin S. Cooper Jr
2015-01-14 21:02 ` Denys Dmytriyenko [this message]
2015-01-14 22:11 ` Cooper Jr., Franklin
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=20150114210213.GM4759@edge \
--to=denys@ti.com \
--cc=fcooper@ti.com \
--cc=meta-ti@yoctoproject.org \
/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.