PPC to PowerPC Migration

[John Linn]

Hi Andrew,

We have a git server with the kernel running on the ML405 (V4) and ML507
(V5) Xilinx boards with arch/powerpc at git://git.xilinx.com.

The default configuration, using ml507_defconfig or ml405_defconfig,
uses a static device tree located in the arch/powerpc/boot/dts
directory.

>make ARCH=powerpc zImage
>make ARCH=powerpc zImage.initrd (for a ramdisk image, after putting
ramdisk image in arch/powerpc/boot directory)

zImage file is located in arch/powerpc/boot directory.

On the http://git.xilinx.com site, there's some tar files with a bit
stream to match the default kernel configuration.

Maybe this is not what you're looking for, but thought I'd offer. Others
have used this to get their own boards running with Linux.

Look at Documentation/powerpc/booting-without-of.txt for some device
tree information.

Thanks,
John Linn
Linux Development & Strategy

Xilinx is looking for more embedded Linux developers.

-----Original Message-----
From: linuxppc-embedded-bounces+john.linn=xilinx.com at ozlabs.org
[mailto:linuxppc-embedded-bounces+john.linn=xilinx.com at ozlabs.org] On
Behalf Of Andy Schmidt
Sent: Tuesday, June 10, 2008 11:49 AM
To: linuxppc-embedded at ozlabs.org
Subject: PPC to PowerPC Migration

I am wondering if anyone has seen any good documentation for migrating
from the arch/ppc to arch/powerpc.  Specifically, I am working with a
Xilinx board so I am more accustom to the xparamters.h vs. device
trees.  I am very willing to build a (or multiple) tutorials to help
others in my situation, I just need some initial help getting started.
 If anyone can point me in the right direction, I will be sure to keep
the group (or those interested) updated on the documentation.

Thank you,
Andrew
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded at ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded


This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.