From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/3] Add chumby falconwing kernel recipe
Date: Thu, 19 Aug 2010 23:36:29 +0200 [thread overview]
Message-ID: <4C6DA3DD.4080501@eukrea.com> (raw)
In-Reply-To: <B49DA616-CD60-4E6E-A141-C3637BA9EB24@chumby.com>
Hi Sean,
Le 19/08/2010 21:21, Sean Cross a écrit :
> On Aug 19, 2010, at 1:32 AM, Koen Kooi wrote:
>> Can't this me merged into the .26.28 kernel recipe?
>>
> I can do that, but the resulting patch is 28 megabytes. I think
> that's a bit big.
>
> It's Freescale's kernel patch, which supports all of their
> processors, not just the i.MX233. My guess is that nobody's tried to
> get these patches into the kernel upstream.
>
> The resulting patch I get is mostly an additive patch, as I count
> 800,000 added lines in the patch, and 1200 removed lines.
>
maybe using Freecale git server with the right revision will allow you
to only have one smaller patch which adds support of your board :
http://opensource.freescale.com/git?p=imx/linux-2.6-imx.git;a=summary
Eric
next prev parent reply other threads:[~2010-08-19 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 23:03 [PATCH 2/3] Add chumby falconwing kernel recipe Sean Cross
2010-08-19 5:50 ` Khem Raj
2010-08-19 8:32 ` Koen Kooi
2010-08-19 19:21 ` Sean Cross
2010-08-19 21:36 ` Eric Bénard [this message]
2010-08-25 4:55 ` Sean Cross
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=4C6DA3DD.4080501@eukrea.com \
--to=eric@eukrea.com \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox