From: Greg Ungerer <gerg@linux-m68k.org>
To: Reid Lindsay <reidlindsay@rallycraft.com>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: linux-m68k@vger.kernel.org
Subject: Re: Issues with vmalloc and ebtables on ColdFire V4e
Date: Sat, 11 Jun 2016 23:14:51 +1000 [thread overview]
Message-ID: <575C0ECB.3050600@linux-m68k.org> (raw)
In-Reply-To: <9b4733d6-fe6d-a27b-aa59-c3285b1fb917@rallycraft.com>
On 11/06/16 21:51, Reid Lindsay wrote:
> On 11/06/2016 7:23 PM, John Paul Adrian Glaubitz wrote:
>> On 06/11/2016 07:54 AM, Reid Lindsay wrote:
>>> The CPU is the 54415 running a 2.6.38 kernel with BSP patches and bug
>>> fixes
>>> provided by Freescale. 64MiB SRAM and 64MiB NAND Flash. The compiler
>>> is GCC
>>> 4.4.1-cs4.4-54.
>> Should those patches be merged in the kernel if they fix bugs?
>>
>> Adrian
> Yes, absolutely. We are considering starting a project to upgrade our
> kernel, and I would be happy to contribute any patches and bug fixes
> which result from this effort.
>
> The Freescale (now NXP) BSP for ColdFire was last updated in Oct 2011,
> and as far as I can tell, there has been no effort to merge patches into
> the mainline kernel. The BSP can be found here:
> http://www.nxp.com/products/software-and-tools/run-time-software/linux-software-and-development-tools/bsps-for-coldfire-architectures:CW_BSP_COLDFIRE.
> In response to bugs we discovered in the DMA and Ethernet drivers,
> Freescale directly provided us with some additional patches on top of
> this BSP. Judging by the website, these patches have not yet been
> released publicly. Some effort will be required to port them to mainline
> (if indeed they are still relevant) given the m68k code has diverged
> somewhat.
The mainline support for v4e is not directly based on Freescales
changes - though it does contain some parts of code they developed.
And mainline doesn't currently support the 54415. (There are some
patches that are close but not quite there yet).
Have you tried asking Freescale?
After all you are using code and patches they supplied.
Regards
Greg
next prev parent reply other threads:[~2016-06-11 13:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 5:54 Issues with vmalloc and ebtables on ColdFire V4e Reid Lindsay
2016-06-11 9:23 ` John Paul Adrian Glaubitz
2016-06-11 11:51 ` Reid Lindsay
2016-06-11 13:14 ` Greg Ungerer [this message]
2016-06-12 2:20 ` Reid Lindsay
2016-06-12 2:44 ` Finn Thain
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=575C0ECB.3050600@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@vger.kernel.org \
--cc=reidlindsay@rallycraft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox