All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Nelson, Sam" <sam.nelson@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [PATCH] linux-keystone: Create recipe for linux-keystone kernel version 3.10
Date: Wed, 29 Jan 2014 18:36:12 -0500	[thread overview]
Message-ID: <20140129233612.GW6814@edge> (raw)
In-Reply-To: <4F9216F96E5DF9428610502835A9F490549E9975@DLEE11.ent.ti.com>

On Wed, Jan 29, 2014 at 06:29:32PM -0500, Nelson, Sam wrote:
> > -----Original Message-----
> > From: Dmytriyenko, Denys
> > Sent: Wednesday, January 29, 2014 4:26 PM
> > To: Nelson, Sam; meta-ti@yoctoproject.org
> > Subject: Re: [meta-ti] [PATCH] linux-keystone: Create recipe for linux-
> > keystone kernel version 3.10
> > 
> > Sam,
> > 
> > Do you need any help with updating this patch? Please let me know if
> > something
> > is not very clear or you just need more time. I don't want to lose momentum
> > :)
> > Thanks.
> > 
> > --
> > Denys
> > 
> > 
> > On Mon, Jan 27, 2014 at 11:35:08PM -0500, Denys Dmytriyenko wrote:
> > > On Mon, Jan 27, 2014 at 11:22:49PM -0500, Sam Nelson wrote:
> > > > - Updated Source URL & version
> > > > - Added device tree file
> > >
> > > Do you need to keep 3.8.4 version around? If not, why not upgrade
> > instead?

> [Sam] You are asking to delete the linux-keystone_3.8.4.bb and the 
> corresponding directory linux-keystone-3.8.4?

If you don't need it anymore. If you do it in a single commit and then git 
format-patch -M (maybe even --find-copies-harder), then it would be recorded 
as an upgrade from 3.8.4 to 3.10.x

BTW, is it really 3.10 and not one of the stable point releases 3.10.x? If 
latter, you also might want to set PV accordingly. As far as I can see, it's 
3.10.10 in git...


> > > Also, I would strongly recommend using linux-ti-kernel_3.12.bb as an
> > example.
> [Sam].
> I could not find a recipe named: linux-ti-kernel_3.12.bb. Appreciate your 
> help. (I can see meta-ti/recipes-kernel/linux-ti-staging_3.12.bb. Is that 
> what you are referring to?)

Yes, indeed. Sorry for the confusion.


> > > > Signed-off-by: Sam Nelson <sam.nelson@ti.com>
> > > > ---
> > > >  recipes-kernel/linux/linux-keystone_3.10.bb |   36
> > +++++++++++++++++++++++++++
> > > >  1 file changed, 36 insertions(+)
> > > >  create mode 100644 recipes-kernel/linux/linux-keystone_3.10.bb
> > > >
> > > > diff --git a/recipes-kernel/linux/linux-keystone_3.10.bb b/recipes-
> > kernel/linux/linux-keystone_3.10.bb
> > > > new file mode 100644
> > > > index 0000000..b37a404
> > > > --- /dev/null
> > > > +++ b/recipes-kernel/linux/linux-keystone_3.10.bb
> > > > @@ -0,0 +1,36 @@
> > > > +SECTION = "kernel"
> > > > +DESCRIPTION = "Linux kernel for TI Keystone devices"
> > > > +LICENSE = "GPLv2"
> > > > +LIC_FILES_CHKSUM =
> > "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
> > > > +
> > > > +COMPATIBLE_MACHINE = "keystone"
> > > > +
> > > > +inherit kernel
> > > > +
> > > > +do_deploy_append() {
> > > > +    cd ${S}
> > > > +}
> > >
> > > I don't remember if this is still needed...
> [Sam] Not sure either why this is needed. I can remove and check.
> > >
> > >
> > > > +require recipes-kernel/linux/linux-dtb.inc
> > > > +require recipes-kernel/linux/setup-defconfig.inc
> > > > +
> > > > +MACHINE_KERNEL_PR_append = "a"
> > > > +
> > > > +CORTEXA8FIXUP = "no"
> > > > +
> > > > +KERNEL_DEVICETREE_keystone-evm = "arch/${ARCH}/boot/dts/k2hk-
> > evm.dts"
> > >
> > > You can use just "k2hk-evm.dtb" instead.
> > >
> [Sam] Ok.
> > >
> > > > +#This commit corresponds to "K2_LINUX_03.10.10_13.12"
> > > > +SRCREV = "335d14b1c2ce23585835243126c6acba89067ecf"
> > > > +
> > > > +BRANCH = "master"
> > > > +
> > > > +# for nightly switch the three lines below
> > >
> > > ^^^ ?
> > >
> [Sam]  Missed to remove this line.
> > >
> > > > +SRC_URI = "git://git.ti.com/keystone-
> > linux/linux.git;protocol=git;branch=${BRANCH}\
> > > > +           file://defconfig\
> > > > +           "
> > > > +
> > > > +S = "${WORKDIR}/git"
> > > > +
> > > > +RDEPENDS_kernel-base = ""
> > > > +
> > > > --
> > > > 1.7.9.5
> > > >
> > > > _______________________________________________
> > > > meta-ti mailing list
> > > > meta-ti@yoctoproject.org
> > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > _______________________________________________
> > > meta-ti mailing list
> > > meta-ti@yoctoproject.org
> > > https://lists.yoctoproject.org/listinfo/meta-ti
> > >


      reply	other threads:[~2014-01-29 23:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28  4:22 [PATCH] linux-keystone: Create recipe for linux-keystone kernel version 3.10 Sam Nelson
2014-01-28  4:35 ` Denys Dmytriyenko
2014-01-29 21:26   ` Denys Dmytriyenko
2014-01-29 23:29     ` Nelson, Sam
2014-01-29 23:36       ` Denys Dmytriyenko [this message]

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=20140129233612.GW6814@edge \
    --to=denys@ti.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=sam.nelson@ti.com \
    /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.