From: Ivan Sergio Borgonovo <mail@webthatworks.it>
To: "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 19:40:41 +0200 [thread overview]
Message-ID: <5627CE19.5040305@webthatworks.it> (raw)
In-Reply-To: <CAP9ODKq1vXWnEt5H0YZpseO8A0q=gVvLsQ=zktm83_tnVOCOCw@mail.gmail.com>
On 10/21/2015 06:53 PM, Otavio Salvador wrote:
> So first thing I would do is to move for U-Boot mainline (or here, u-boot-fslc).
[snip]
> I would take linux-fslc 4.1 branch or linux mainline (4.3-rcX).
Sorry for trying hard to be as much as I can a freeloader ;) but which
one is going to be the one that once I finish my work I'll see supported
by others?
Or maybe to suggest a different opportunity:
which one do you think has more chances to be adopted by the
manufacturer once I'll knock at their door and say "look what a nice
work I've done for free, you'll get much love if you take care of it"?
I'm not sure I'm going to succeed, but why shouldn't I try?
>> Crossing fingers I may not have to learn how uboot works right now.
> It is a nice software and worth learning it ;-)
I've a long list of things I'd like to learn earlier and currently with
a higher return than uboot.
First I'll have to re-read how to hack a kernel in yocto ;)
--
Ivan Sergio Borgonovo
http://www.webthatworks.it
next prev parent reply other threads:[~2015-10-21 17:39 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
2015-10-21 16:53 ` Otavio Salvador
2015-10-21 17:40 ` Ivan Sergio Borgonovo [this message]
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=5627CE19.5040305@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.