From: Siddharth Heroor <heroor@ti.com>
To: "Maupin, Chase" <chase.maupin@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [PATCH] recipes-kernel: Add GLSDK specific kernel tree for omap-a15
Date: Thu, 27 Jun 2013 19:57:46 +0530 [thread overview]
Message-ID: <51CC4BE2.6080602@ti.com> (raw)
In-Reply-To: <7D46E86EC0A8354091174257B2FED1015961B7AF@DLEE11.ent.ti.com>
On 6/27/2013 5:44 PM, Maupin, Chase wrote:
>> -----Original Message-----
>> From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-
>> bounces@yoctoproject.org] On Behalf Of Heroor, Siddharth
>> Sent: Thursday, June 27, 2013 5:13 AM
>> To: meta-ti@yoctoproject.org
>> Subject: [meta-ti] [PATCH] recipes-kernel: Add GLSDK specific
>> kernel tree for omap-a15
>>
>> * Machine compatible with only omap-a15 devices.
>> * The TI Staging tree will not be used to maintain K3.8. Instead,
>> this new tree is set up as a production tree. Pending features
>> for 3.8 will be implemented on this tree.
>> - Backported features from linux mainline
>> - Backported bug-fixes from linux mainline and linux-stable.
>> - Features implemented by the GLSDK team which maybe product
>> specific.
>> This is the tree on which GLSDK kernel releases will be made.
>> * This recipe is based off the Core SDK 2013.04.02 released kernel
>> recipe - recipes-kernel/linux/linux-ti-staging_3.8.bb
>>
>
> Can you try using --find-copies-harder when making this patch or I think Denys likes -m. That will help to minimize the actual patch difference in cases like this where you are based on an existing recipe.
>
>> Signed-off-by: Siddharth Heroor <heroor@ti.com>
>> cc: Mrinmayee Hingolikar <mrinmayee@ti.com>
>> ---
>> recipes-kernel/linux/linux-ti-glsdk/defconfig | 1 +
>> recipes-kernel/linux/linux-ti-glsdk_3.8.bb | 30
>> +++++++++++++++++++++++++
>> 2 files changed, 31 insertions(+), 0 deletions(-)
>> create mode 100644 recipes-kernel/linux/linux-ti-glsdk/defconfig
>> create mode 100644 recipes-kernel/linux/linux-ti-glsdk_3.8.bb
>>
>> diff --git a/recipes-kernel/linux/linux-ti-glsdk/defconfig
>> b/recipes-kernel/linux/linux-ti-glsdk/defconfig
>> new file mode 100644
>> index 0000000..926b35a
>> --- /dev/null
>> +++ b/recipes-kernel/linux/linux-ti-glsdk/defconfig
>> @@ -0,0 +1 @@
>> +use-kernel-config=omap2plus_defconfig
>> diff --git a/recipes-kernel/linux/linux-ti-glsdk_3.8.bb b/recipes-
>> kernel/linux/linux-ti-glsdk_3.8.bb
>> new file mode 100644
>> index 0000000..8d66f84
>> --- /dev/null
>> +++ b/recipes-kernel/linux/linux-ti-glsdk_3.8.bb
>> @@ -0,0 +1,30 @@
>> +SECTION = "kernel"
>> +DESCRIPTION = "Linux kernel for TI devices supported by the GLSDK
>> product"
>> +LICENSE = "GPLv2"
>> +LIC_FILES_CHKSUM =
>> "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
>> +KERNEL_IMAGETYPE = "uImage"
>> +
>> +inherit kernel
>> +
>> +require recipes-kernel/linux/linux-dtb.inc
>> +require recipes-kernel/linux/setup-defconfig.inc
>> +
>> +KERNEL_DEVICETREE_omap5-evm = "arch/arm/boot/dts/omap5-sevm.dts
>> arch/arm/boot/dts/omap5-uevm.dts"
>> +KERNEL_DEVICETREE_dra7xx-evm = "arch/arm/boot/dts/dra7-evm.dts"
>> +
>> +COMPATIBLE_MACHINE = "omap-a15"
>
> I think you might want to set a DEFAULT_PREFERRENCE = -1 here. Since you are going to use your branding config to select this kernel vs. the linux-ti-staging kernel this should be no issue. That way there isn't a confusion about with basic meta-ti what kernel is being picked up.
>
Agreed. I'll fix that.
>> +
>> +S = "${WORKDIR}/git"
>> +
>> +BRANCH = "master"
>> +
>> +# This commit corresponds to ti2013.04.02 release tag
>
> Sorry to nit-pick here, but any reason to re-use the tag name from the linux-ti-staging tree? The reason I ask is back to it being confusing if I have two trees with the same tag name (including version) it becomes kind of confusing. Especially since this tree is part of the same git.ti.com project as the other one. Thoughts?
Agreed. I'll just cleanup the comment. Since we haven't frozen our
commits yet, I would expect changes to this recipe till we that.
>
>> +SRCREV = "f3cb62a800ae37f17a3382b10d155ee02dbc83fc"
>> +PV = "3.8.13"
>> +
>> +# Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause
>> a rebuild
>> +MACHINE_KERNEL_PR_append = "f+gitr${SRCPV}"
>
> Go ahead and reset your append here to a+ gitr${SRCPV}. No need to start from f.
Right. Will reset to a+.
>
> Thanks for the submission. Overall looks pretty good, just a few things to fix up.
>
>> +
>> +SRC_URI = "git://git.ti.com/ti-linux-kernel/ti-linux-3-8-y-
>> kernel.git;protocol=git;branch=${BRANCH} \
>> + file://defconfig \
>> + "
>> --
>> 1.7.0.4
>>
>> _______________________________________________
>> meta-ti mailing list
>> meta-ti@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-ti
next prev parent reply other threads:[~2013-06-27 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 10:13 [PATCH] recipes-kernel: Add GLSDK specific kernel tree for omap-a15 Siddharth Heroor
2013-06-27 12:14 ` Maupin, Chase
2013-06-27 13:34 ` Siddharth Heroor
2013-06-27 14:23 ` Denys Dmytriyenko
2013-06-27 14:31 ` Siddharth Heroor
2013-06-27 14:27 ` Siddharth Heroor [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-27 13:49 Siddharth Heroor
2013-06-27 13:52 ` Cooper Jr., Franklin
2013-06-27 14:16 ` Maupin, Chase
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=51CC4BE2.6080602@ti.com \
--to=heroor@ti.com \
--cc=chase.maupin@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.