arch/powerpc, Xilinx, and mainline kernel support

[Stephen Neuendorffer]

Grant, could you post explicit instructions about how to build the
simpleImage?  I tried it too and couldn't get the makefile rules to
match my dts.

Mike, Supporting mpmc2 for memory access only is pretty straightforward,
but supporting the temac/sdma connections is more problematic,
particularly since we have no plans to update the plb_temac driver for
ARCH=powerpc.

Steve

> -----Original Message-----
> From: Koss, Mike (Mission Systems) [mailto:mike.koss at ngc.com]
> Sent: Friday, May 23, 2008 8:09 AM
> To: Stephen Neuendorffer; Grant Likely
> Cc: linuxppc-embedded at ozlabs.org
> Subject: RE: arch/powerpc, Xilinx, and mainline kernel support
> 
> So yesterday, we got a chance to checkout Linus' main (2.26.26-rc3)
and
> it appears to not have all the necessary updates to build for the
> Generic Xilinx Virtex either.
> 
> For now, I've decided to work from the Xilinx git-tree.
> 
> We also gave the EDK bsp->dts generator a spin, and I have a comment
on
> it: documentation. It would be nice to have some kind of simple README
> that explains what it is and what it supports. The current README
talks
> about using the old python script. I fired up the bsp against my EDK
9.1
> MPMC(2) based system and it bombed out when it reached the MPMC2
> definition. So I dug through the tcl and found it that it was only
> supporting the MPMC3.
> 
> I'm still working on my EDK 9.2 MPMC3 system, so I can't check to see
if
> that works or not, yet.
> 
> -- Mike
> 
> -----Original Message-----
> From: Stephen Neuendorffer [mailto:stephen.neuendorffer at xilinx.com]
> Sent: Friday, May 16, 2008 6:34 PM
> To: Grant Likely; Koss, Mike (Mission Systems)
> Cc: linuxppc-embedded at ozlabs.org
> Subject: RE: arch/powerpc, Xilinx, and mainline kernel support
> 
> 
> 
> > -----Original Message-----
> > From: linuxppc-embedded-bounces+stephen=neuendorffer.name at ozlabs.org
> [mailto:linuxppc-embedded-
> > bounces+stephen=neuendorffer.name at ozlabs.org] On Behalf Of Grant
> Likely
> > Sent: Friday, May 16, 2008 3:27 PM
> > To: Koss, Mike (Mission Systems)
> > Cc: linuxppc-embedded at ozlabs.org
> > Subject: Re: arch/powerpc, Xilinx, and mainline kernel support
> >
> > On Fri, May 16, 2008 at 4:06 PM, Koss, Mike (Mission Systems)
> > <mike.koss at ngc.com> wrote:
> > > Is there any reason why the mainline 2.6.25.3 (and from what I
could
> see .4)
> > > is missing the files to build for the Xilinx Virtex platform?
> > >
> > > Or in other words, I tried to build from 2.6.25.3 for the Xilinx
> Virtex
> > > under arch/powerpc (because arch/ppc actually crashes when once
apps
> start
> > > to run) and it failed when trying to actually create the zImage. I
> hopped
> > > over to Xilinx's git server and noticed a bunch of missing entries
> in the
> > > boot/Makefile and source code to actually support the complete
image
> build
> > > for a Xilinx Virtex PPC405.
> > >
> > > When is the Xilinx Virtex support going to be mainline official? I
> need to
> > > be able to grab a stable kernel and work from there rather than
> using the
> > > latest -rc that Xilinx is hosting on their git server.
> >
> > Working on it.  Biggest problem is getting the device drivers in
> > shape.  However, other than Ethernet support, current arch/powerpc
> > (head of Linus' tree, not 2.6.25) should work for building virtex
> > kernels.
> 
> Mike,
> 
> What is your objection to using what is in the git tree, because it is
> based on 24-rc8 and not 25, or something more fundamental?
> 
> Steve
> 
> 
> 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.
> 
> 


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.