ARCH=ppc or ARCH=powerpc
Hello,
I'm new to Linux PowerPC platform, and I'm wondering what ARCH we should use to build the kernel. There seems to be 'ppc' and 'powerpc'. What's the difference between the two ?
Thank you !
Benjamin
ppc = 32bit.
powerpc= 64bit.
Correct me if I am wrong.
I am not sure why community didn't adopt the name ppc and ppc64 just like ia-32 and ia64.
Parav
Benjamin Delagoutte <[email protected]> wrote:
Hello,
I'm new to Linux PowerPC platform, and I'm wondering what ARCH we should use to build the kernel. There seems to be 'ppc' and 'powerpc'. What's the difference between the two ?
Thank you !
Benjamin
_______________________________________________
Linuxppc-embedded mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
---------------------------------
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail.
Quoted 3 lines · Parav Pandit
ppc = 32bit.
powerpc= 64bit.
Correct me if I am wrong.
Yes, you're wrong. Some 32 bit boards are also under arch/powerpc now.
Quoted 3 lines
I am not sure why community didn't adopt the name ppc and ppc64 just like ia-32 and ia64.
They did originally.
The new direction is to have everything under arch/powerpc, both 32 and 64 bit. The reason arch/ppc still exists is because some 32 bit platforms have not been fully migrated to the requirements to be merged into arch/powerpc. Namely, the code has to boot from an OpenFirmware like flattened device tree. The PPC 4xx family of processors, as an example, does not do this yet though there is work going on to adapt it.
Eventually, arch/ppc will go away and all of PowerPC will be under arch/powerpc. That's the goal anyway.
josh
Quoted 11 lines · Josh Boyer
Quoted 3 lines · Parav Pandit
ppc = 32bit.
powerpc= 64bit.
Correct me if I am wrong.Yes, you're wrong. Some 32 bit boards are also under
arch/powerpcnow.Quoted 3 lines
I am not sure why community didn't adopt the name ppc and ppc64 just like ia-32 and ia64.
Quoted 8 lines
They did originally.
The new direction is to have everything under
arch/powerpc, both 32 and 64 bit. The reasonarch/ppcstill exists is because some 32 bit platforms have not been fully migrated to the requirements to be merged intoarch/powerpc. Namely, the code has to boot from an OpenFirmware like flattened device tree. The PPC 4xx family of processors, as an example, does not do this yet though there is work going on to adapt it.
I'm currently working on a PPC 405 based developement card. Does it mean I have to work using the arch/ppc tree ?
What about the includes ? Do I have to use only include/asm-ppc or are include/asm-powerpc necessary as well ?
Quoted 8 lines
Eventually,
arch/ppcwill go away and all of PowerPC will be underarch/powerpc. That's the goal anyway.josh
_______________________________________________
Linuxppc-embedded mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Quoted 3 lines · Benjamin Delagoutte
I'm currently working on a PPC 405 based developement card. Does it mean I have to work using the
arch/ppctree ?
For now, yes. Set ARCH=ppc when you compile the kernel.
Quoted 2 lines
What about the includes ? Do I have to use only
include/asm-ppcor areinclude/asm-powerpcnecessary as well ?
I believe there are some hacks in the makefiles to pull common asm files from include/asm-powerpc when needed. Basically, you should be able to just do:
#include <asm/foo.h>
and it should work. If you're adding new .h files, I suppose asm-ppc is the place to add them for now. That's just my opinion though :)
josh
Quoted 4 lines · Josh Boyer
Quoted 2 lines · Benjamin Delagoutte
What about the includes ? Do I have to use only
include/asm-ppcor areinclude/asm-powerpcnecessary as well ?
Quoted 8 lines
I believe there are some hacks in the makefiles to pull common asm files from
include/asm-powerpcwhen needed. Basically, you should be able to just do:#include <
asm/foo.h>and it should work. If you're adding new .h files, I suppose asm-ppc is the place to add them for now. That's just my opinion though :)
That's what I would recommend too. If this is for an out-of-tree custom port then there's no real concern anyway.
-Matt
Quoted 21 lines · Benjamin Delagoutte
Quoted 11 lines · Josh Boyer
Quoted 3 lines · Parav Pandit
ppc = 32bit.
powerpc= 64bit.
Correct me if I am wrong.Yes, you're wrong. Some 32 bit boards are also under
arch/powerpcnow.Quoted 3 lines
I am not sure why community didn't adopt the name ppc and ppc64 just like ia-32 and ia64.
Quoted 8 lines
They did originally.
The new direction is to have everything under
arch/powerpc, both 32 and 64 bit. The reasonarch/ppcstill exists is because some 32 bit platforms have not been fully migrated to the requirements to be merged intoarch/powerpc. Namely, the code has to boot from an OpenFirmware like flattened device tree. The PPC 4xx family of processors, as an example, does not do this yet though there is work going on to adapt it.
Quoted 2 lines
I'm currently working on a PPC 405 based developement card. Does it mean I have to work using the
arch/ppctree ?
PPC405 is only supported in the arch/ppc tree currenty. Unless you want to contribute to the effort to move to arch/powerpc, you'll have to work with arch/ppc/
Quoted 2 lines
What about the includes ? Do I have to use only
include/asm-ppcor areinclude/asm-powerpcnecessary as well ?
When you do an arch/ppc build it automagically includes shared includes from asm-powerpc as necessary. There's nothing to worry about there.
The goal is to have the new 4xx arch/powerpc support not break 4xx arch/ppc support. So as boards are merged and verified working, we'll remove the equivalent support from arch/ppc...
Some boards/chips may just die if no maintainer step up to port them over...but all the important stuff should get an interested party once we get the initial 4xx support in arch/powerpc working.
-Matt
Hi Matt,
Quoted 7 lines
The goal is to have the new 4xx
arch/powerpcsupport not break 4xxarch/ppcsupport. So as boards are merged and verified working, we'll remove the equivalent support fromarch/ppc...Some boards/chips may just die if no maintainer step up to port them over...but all the important stuff should get an interested party once we get the initial 4xx support in
arch/powerpcworking.
When can we expect this done? I have a 440 based SoC project ongoing and am thinking when I should start moving to arch/powerpc.
THanks,
-Shawn.
Quoted 6 lines · Shawn Jin
Hi Matt,
Quoted 4 lines
The goal is to have the new 4xx
arch/powerpcsupport not break 4xxarch/ppcsupport. So as boards are merged and verified working, we'll remove the equivalent support fromarch/ppc...
Quoted 6 lines
Quoted 3 lines
Some boards/chips may just die if no maintainer step up to port them over...but all the important stuff should get an interested party once we get the initial 4xx support in
arch/powerpcworking.When can we expect this done? I have a 440 based SoC project ongoing and am thinking when I should start moving to
arch/powerpc.
There is no set date or kernel release where this will be done. In other words "when it gets done, it gets done". :)
josh
Quoted 11 lines · Josh Boyer
Quoted 10 lines · Shawn Jin
Hi Matt,
Quoted 7 lines
The goal is to have the new 4xx
arch/powerpcsupport not break 4xxarch/ppcsupport. So as boards are merged and verified working, we'll remove the equivalent support fromarch/ppc...Some boards/chips may just die if no maintainer step up to port them over...but all the important stuff should get an interested party once we get the initial 4xx support in
arch/powerpcworking.
Quoted 5 lines
Quoted 2 lines
When can we expect this done? I have a 440 based SoC project ongoing and am thinking when I should start moving to
arch/powerpc.There is no set date or kernel release where this will be done. In other words "when it gets done, it gets done". :)
There is some push for putting a date one year from now as when arch/ppc will go away.
- k
Thanks for correcting my understanding.
We would also move our code to powerpc from ppc next release onwards.
Parav
Josh Boyer <[email protected]> wrote:
Quoted 3 lines · Parav Pandit
ppc = 32bit.
powerpc= 64bit.
Correct me if I am wrong.
Yes, you're wrong. Some 32 bit boards are also under arch/powerpc now.
Quoted 3 lines
I am not sure why community didn't adopt the name ppc and ppc64 just like ia-32 and ia64.
They did originally.
The new direction is to have everything under arch/powerpc, both 32 and 64 bit. The reason arch/ppc still exists is because some 32 bit platforms have not been fully migrated to the requirements to be merged into arch/powerpc. Namely, the code has to boot from an OpenFirmware like flattened device tree. The PPC 4xx family of processors, as an example, does not do this yet though there is work going on to adapt it.
Eventually, arch/ppc will go away and all of PowerPC will be under arch/powerpc. That's the goal anyway.
josh
---------------------------------
Stay in the know. Pulse on the new Yahoo.com. Check it out.