All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Sergio Borgonovo <mail@webthatworks.it>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: from where to start to port some patches to a newer kernel
Date: Wed, 21 Oct 2015 00:54:43 +0200	[thread overview]
Message-ID: <5626C633.7040503@webthatworks.it> (raw)

I'm playing with an imx28evk based board.

The manufacturer supports just the old freescale kernel and and I have 
their layer to make it work in Yocto.
They didn't define a new board, they just patched the bsp of imx28evk.

I'd like to get an idea about how hard it could be to port those patches 
to a newer kernel.
Which kernel would you suggest?

What procedure do you suggest to set up a dev environment that will let 
me try start hacking easily?

I was thinking about:
* creating a copy of their layer, getting rid of their kernel patches
* uncomment
   PREFERRED_PROVIDER_virtual/kernel = "linux-fslc"
   and
   PREFERRED_VERSION_linux-fslc = "3.%"
   in local.conf
* build image-core-minimal
* start to add their ported patch back in the copy of their layer.

Hoping that once I start they will join.

thanks

-- 
Ivan Sergio Borgonovo
http://www.webthatworks.it



             reply	other threads:[~2015-10-20 22:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20 22:54 Ivan Sergio Borgonovo [this message]
2015-10-20 23:35 ` from where to start to port some patches to a newer kernel Otavio Salvador
2015-10-21  0:55   ` Ivan Sergio Borgonovo
2015-10-21 16:53     ` Otavio Salvador
2015-10-21 17:40       ` Ivan Sergio Borgonovo
2015-10-21 18:00         ` Otavio Salvador

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=5626C633.7040503@webthatworks.it \
    --to=mail@webthatworks.it \
    --cc=meta-freescale@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.