ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] updating the kernel


From: Stuart Hughes
Subject: Re: [Ltib] updating the kernel
Date: Thu, 23 Jul 2009 09:45:05 +0100
User-agent: Thunderbird 2.0.0.16 (X11/20080707)

Hi B.J.

Are you talking about patches you've made or those Freescale have made?

If you're talking about Freescale patches, you need to talk to them and find out whether those patches have been merged upstream into the vanilla kernel. Its quite possible some/all are already in 2.6.30.

If the modifications are ones you have made then I agree that they should be applied against a recent kernel, or better the latest kernel.org git tree so that you can submit your patches to the kernel mailing list. Your best bet is probably to join the appropriate kernel mailing list and ask their advice.

If you get to a point where you have a vanilla kernel (say 2.6.30) plus a set of (your) patches and you have tested them and would like them added to LTIB I can help with that. Currently Freescale have not merged out the 8377, so it would be helpful if they would do that (avoiding duplication/conflict), maybe you could ask them to send a patch to this list.

Regards, Stuart


B.J. Buchalter wrote:
So, related to, but different from my previous question: I am working with a freescale ltib BSP (for the MPC8377).

The kernel version in that BSP is 2.6.25

There has been a bunch of development in the firewire drivers in the kernel. Merging in the changes to FireWire into the 2.6.25 kernel looks to be non-trivial since there have been substantial changes to the kernel SPIs.

What is involved in bringing up a new version of the kernel within a given BSP or LTIB if there is no direct support for it yet?

Is it worth my time (as a relative newbie) to try to get 2.6.30 building for my board? If so, is there any guide to doing it?

It looks to me like I will need to make changes to the FireWire driver in the kernel, but that seems to be kind of a waste of time if I make the changes on an old version of the kernel, as then there would be no real way to get the changes/fixes into the main line. But it doesn't make sense to be working on the head if I can't get it to build for my target...

Thanks!

B.J. Buchalter
Metric Halo
http://www.mhlabs.com




reply via email to

[Prev in Thread] Current Thread [Next in Thread]