From: Ivan Sergio Borgonovo <mail@webthatworks.it>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: from where to start to port some patches to a newer kernel
Date: Wed, 21 Oct 2015 02:55:33 +0200 [thread overview]
Message-ID: <5626E285.9030806@webthatworks.it> (raw)
In-Reply-To: <CAP9ODKoHq+tjXk8P385TwvBFZVa2VnLfBJTtF0rn5XBW8juiFA@mail.gmail.com>
On 21/10/2015 01:35, Otavio Salvador wrote:
> It depends on how:
> - much access you have to information
I've a working yocto layer that use freescale 2.6.35 kernel that
includes some minor changes to init to set up a display. tslib and some
kernel patches.
Most of the patches are related to the attached display.
Others look like backports or pin configuration (none of which seems to
be "boot" related).
No pathces for uboot.
> - is the board already supported by Linux mainline?
Up to my understanding of the patches, the board shouldn't be very
different from the original imx28evk so it probably may be supported and
I may just have to reassign some pins and port the display patches.
> - compare both kernel sources to see the changes done by the manufactor
Ok, going back to re-read my books. Anyway, which kernel would you
suggest considering the board doesn't look that different from the
original imx28evk?
> To be honest, I would start at U-Boot and not the kernel as it is
> easier to hack and also allow for you to learn more about the board
> specifics.
Crossing fingers I may not have to learn how uboot works right now.
thanks
--
Ivan Sergio Borgonovo
http://www.webthatworks.it
next prev parent reply other threads:[~2015-10-21 0:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 22:54 from where to start to port some patches to a newer kernel Ivan Sergio Borgonovo
2015-10-20 23:35 ` Otavio Salvador
2015-10-21 0:55 ` Ivan Sergio Borgonovo [this message]
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=5626E285.9030806@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.