PPC 405GPr support in linux 2.4.32
Marcelo Tosatti wrote: Folks, The v2.4 patch acceptance policy has been shifting gradually from accept new features to critical fixes only, and at this point in time the goal is to have a minimal amount of modifications as possible. There should be no need for major patch reworking with reference to new v2.4 releases. Willy Tarreau created a repository of useful v2.4 patches for this sort of situations. Stephen, Eugene, I think the 405GPr patches are good candidates. http://w.ods.org/linux/kernel/2.4/lkup/hardware.html This (and things like it) needs to be *much* better advertised. I had no idea it existed, or where I would look for such a thing. It does no one any good if no one thinks to look for it;-) If course the next major question is how does one submit patches to this system? -- Steve WilliamsThe woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep.
PPC 405GPr support in linux 2.4.32
On Thu, Apr 27, 2006 at 11:32:45AM -0700, Stephen Williams wrote: Eugene Surovegin wrote: There are bigger problems with 4xx support in 2.4 mainline than just missing some chips support. Some parts which are already in 2.4 (e.g. ethernet driver) are of non-production quality. I can imagine Marcelo agreeing to commit 405GPr/405EP support as this change shouldn't break anything, but this will not make 2.4 support really useful for real world deployments. I think we are stuck with maintaining our own 2.4 trees with backports from 2.6. This is what I do myself of all our products (and yeah, diff between stock 2.4.32 and my internal version has already grown quite big to be acceptable for 2.4 inclusion). Of course we are going to have to keep our own per-board trees. but the blatantly common stuff, like the core 405gpr support and certain drivers, might as well go in if the gatekeeper can be convinced. You and I both probably have huge drivers for custom devices hanging off our PPCs, with various hacks to squeeze extra performance out. These make our transition to 2.6 difficult, and surely we are not alone. So 2.4 is going to be around for a while longer for us, so we might as well make an effort to keep the house in some sort of order. It serves no one to keep these fixes a secret:-) In any case, if the patches I sent are rejected, then that's that. We'll see. Folks, The v2.4 patch acceptance policy has been shifting gradually from accept new features to critical fixes only, and at this point in time the goal is to have a minimal amount of modifications as possible. There should be no need for major patch reworking with reference to new v2.4 releases. Willy Tarreau created a repository of useful v2.4 patches for this sort of situations. Stephen, Eugene, I think the 405GPr patches are good candidates. http://w.ods.org/linux/kernel/2.4/lkup/hardware.html Of course that it would be incredibly better for everyone to be happy with v2.6. I see a lot of embedded users complaining about v2.6. Cyclades (my former employer) has been using v2.6 in production environments with 48MHz MPC855T PPC's with no problems at all (actually, it is faster in certain key situations). This boxes have 128MB, which is can be considered large, but still, no major problems have been seen in _several_ different v2.6 versions.
PPC 405GPr support in linux 2.4.32
Stephen Williams wrote: ... seems completely missing in the linux-2.3.32 tree from kernel.org. This used to be in the linuxppc-2.4 BK tree that no longer exists, so what happened to the ppc405GPr support?! The attached patch adds the ibm405gpr support files from various places and adds the core support to Linux 2.4. Although this diff was done relative Marcelo's git tree, it actually touches no C files, only a few config and make files (Plus it adds the gpr support c/h files) so it should apply to any recent 2.4 kernel tree. I'm almost ready with a patch that does a similar thing with the SystemACE driver. -- Steve WilliamsThe woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep. -- next part -- An embedded and charset-unspecified text was scrubbed... Name: 0001-Core-ppc405GPr-support.txt Url: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060427/89f6fb0b/attachment.txt
PPC 405GPr support in linux 2.4.32
On Wed, Apr 26, 2006 at 04:57:21PM -0700, Stephen Williams wrote: Is there a git tree for main line 2.4 maintenance (against which I could maintain patches) git://git.kernel.org/pub/scm/linux/kernel/git/marcelo/linux-2.4.git -- Eugene
PPC 405GPr support in linux 2.4.32
On Wed, Apr 26, 2006 at 04:35:40PM -0700, Matt Porter wrote: linuxppc-2.4 tree to linux-2.4. Oh, and Marcelo didn't want to take new stuff into linux-2.4 at that time either. There's still rsync://source.mvista.com/linuxppc-2.4 available with the 405gpr/sycamore support. There are bigger problems with 4xx support in 2.4 mainline than just missing some chips support. Some parts which are already in 2.4 (e.g. ethernet driver) are of non-production quality. I can imagine Marcelo agreeing to commit 405GPr/405EP support as this change shouldn't break anything, but this will not make 2.4 support really useful for real world deployments. I think we are stuck with maintaining our own 2.4 trees with backports from 2.6. This is what I do myself of all our products (and yeah, diff between stock 2.4.32 and my internal version has already grown quite big to be acceptable for 2.4 inclusion). -- Eugene
PPC 405GPr support in linux 2.4.32
Eugene Surovegin wrote: There are bigger problems with 4xx support in 2.4 mainline than just missing some chips support. Some parts which are already in 2.4 (e.g. ethernet driver) are of non-production quality. I can imagine Marcelo agreeing to commit 405GPr/405EP support as this change shouldn't break anything, but this will not make 2.4 support really useful for real world deployments. I think we are stuck with maintaining our own 2.4 trees with backports from 2.6. This is what I do myself of all our products (and yeah, diff between stock 2.4.32 and my internal version has already grown quite big to be acceptable for 2.4 inclusion). Of course we are going to have to keep our own per-board trees. but the blatantly common stuff, like the core 405gpr support and certain drivers, might as well go in if the gatekeeper can be convinced. You and I both probably have huge drivers for custom devices hanging off our PPCs, with various hacks to squeeze extra performance out. These make our transition to 2.6 difficult, and surely we are not alone. So 2.4 is going to be around for a while longer for us, so we might as well make an effort to keep the house in some sort of order. It serves no one to keep these fixes a secret:-) In any case, if the patches I sent are rejected, then that's that. We'll see. -- Steve WilliamsThe woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep.
PPC 405GPr support in linux 2.4.32
On Thu, Apr 27, 2006 at 11:32:45AM -0700, Stephen Williams wrote: Eugene Surovegin wrote: There are bigger problems with 4xx support in 2.4 mainline than just missing some chips support. Some parts which are already in 2.4 (e.g. ethernet driver) are of non-production quality. I can imagine Marcelo agreeing to commit 405GPr/405EP support as this change shouldn't break anything, but this will not make 2.4 support really useful for real world deployments. I think we are stuck with maintaining our own 2.4 trees with backports from 2.6. This is what I do myself of all our products (and yeah, diff between stock 2.4.32 and my internal version has already grown quite big to be acceptable for 2.4 inclusion). Of course we are going to have to keep our own per-board trees. but the blatantly common stuff, like the core 405gpr support and certain drivers, might as well go in if the gatekeeper can be convinced. You and I both probably have huge drivers for custom devices hanging off our PPCs, with various hacks to squeeze extra performance out. These make our transition to 2.6 difficult, and surely we are not alone. Well, personally, I don't migrate to 2.6 not because I have many custom drivers in my tree (if they are properly written, migration is relatively easy), but because 2.6 in my opinion isn't production ready, at least for architectures I work with. 2.6 is slower, bigger, is constantly being broken by huge amount of changes, etc. I spent enough time making 2.4 work on our hardware given limitations and requirements put on performance, resources etc. I just don't have time to go through this cycle again. And I'm not talking about PPC stuff, I mean mostly generic stuff - filesystems, scheduling, networking, etc. So 2.4 is going to be around for a while longer for us, so we might as well make an effort to keep the house in some sort of order. It serves no one to keep these fixes a secret:-) They aren't secret, but I can understand the simple fact that 2.4 is closed for a new stuff, we might not like that (although I do, just look at the mess stable 2.6 is :). There is a point in every piece of software life-cycle when you have to stop adding features. 2.4 is already at this point, and we should accept that. -- Eugene
PPC 405GPr support in linux 2.4.32
... seems completely missing in the linux-2.3.32 tree from kernel.org. This used to be in the linuxppc-2.4 BK tree that no longer exists, so what happened to the ppc405GPr support?! -- Steve WilliamsThe woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep.
PPC 405GPr support in linux 2.4.32
Stephen Williams wrote: ... seems completely missing in the linux-2.3.32 tree from kernel.org. This used to be in the linuxppc-2.4 BK tree that no longer exists, so what happened to the ppc405GPr support?! I guess nobody sent patches upstream and development shifted to 2.6 kernel. 405Gpr is not alone. 405EP and a number of other CPU support that was present never got its way up kernel.org sources.
PPC 405GPr support in linux 2.4.32
On Wed, Apr 26, 2006 at 04:19:23PM -0700, Stephen Williams wrote: ... seems completely missing in the linux-2.3.32 tree from kernel.org. This used to be in the linuxppc-2.4 BK tree that no longer exists, so what happened to the ppc405GPr support?! There's some stuff that never got submitted upstream to kernel.org during 2.4 due partially to 2.5 appearing. All upstream devel moved to 2.5/2.6 and no effort was made to merge stuff from the linuxppc-2.4 tree to linux-2.4. Oh, and Marcelo didn't want to take new stuff into linux-2.4 at that time either. There's still rsync://source.mvista.com/linuxppc-2.4 available with the 405gpr/sycamore support. -Matt
PPC 405GPr support in linux 2.4.32
Matt Porter wrote: On Wed, Apr 26, 2006 at 04:19:23PM -0700, Stephen Williams wrote: ... seems completely missing in the linux-2.3.32 tree from kernel.org. This used to be in the linuxppc-2.4 BK tree that no longer exists, so what happened to the ppc405GPr support?! There's some stuff that never got submitted upstream to kernel.org during 2.4 due partially to 2.5 appearing. All upstream devel moved to 2.5/2.6 and no effort was made to merge stuff from the linuxppc-2.4 tree to linux-2.4. Oh, and Marcelo didn't want to take new stuff into linux-2.4 at that time either. There's still rsync://source.mvista.com/linuxppc-2.4 available with the 405gpr/sycamore support. Well then I guess for 405GPr support and the SystemACE drivers I'm on my own. Is there a git tree for main line 2.4 maintenance (against which I could maintain patches) or am I on my own there too? It should be easy enough to rescue the gpr support form the bk working dir that I have (or the mvista repository as you point out) and make up patches. -- Steve WilliamsThe woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep.
