LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>
To: "Koss, Mike (Mission Systems)" <mike.koss@ngc.com>,
	"John Linn" <linnj@xilinx.com>,
	"Grant Likely" <grant.likely@secretlab.ca>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: arch/powerpc, Xilinx, and mainline kernel support
Date: Fri, 23 May 2008 10:15:48 -0700	[thread overview]
Message-ID: <20080523171549.668DB16A806A@mail207-va3.bigfish.com> (raw)
In-Reply-To: <EDAE140DF1B2FC42B5867C22CA0B333FFA5C23@XMBIL132.northgrum.com>


We should run the fdt tests every night and generate a list of IP used
in tests.

> -----Original Message-----
> From: Koss, Mike (Mission Systems) [mailto:mike.koss@ngc.com]
> Sent: Friday, May 23, 2008 10:13 AM
> To: John Linn; Stephen Neuendorffer; Grant Likely
> Cc: linuxppc-embedded@ozlabs.org
> Subject: RE: arch/powerpc, Xilinx, and mainline kernel support
> =

> Yeah, I wasn't saying "hey! We need to support old/deprecated cores!".
> Rather I was stating that it would be nice to know which cores are
> supported currently: SystemACE, MPMC3/4, XPS_LL_TEMAC, SDMA, etc. Just
> so this sort of thing doesn't happen again to the next person who
tries
> it. If I get time this weekend, I may try and extract that information
> from the tcl and post a patch for the README.
> =

> -----Original Message-----
> From: John Linn [mailto:John.Linn@xilinx.com]
> Sent: Friday, May 23, 2008 12:52 PM
> To: Koss, Mike (Mission Systems); Stephen Neuendorffer; Grant Likely
> Cc: linuxppc-embedded@ozlabs.org
> Subject: RE: arch/powerpc, Xilinx, and mainline kernel support
> =

> Hi Mike,
> =

> Thanks for the input, sounds right to me, we'll put it on the list of
> things to do.
> =

> In general we will be testing our work on the current version of the
> Xilinx tools and not maintaining them for all versions of the Xilinx
> tools, but we need a way to spell that out cleanly.
> =

> Thanks,
> John
> =

> -----Original Message-----
> From: linuxppc-embedded-bounces+john.linn=3Dxilinx.com@ozlabs.org
> [mailto:linuxppc-embedded-bounces+john.linn=3Dxilinx.com@ozlabs.org] On
> Behalf Of Koss, Mike (Mission Systems)
> Sent: Friday, May 23, 2008 9:09 AM
> To: Stephen Neuendorffer; Grant Likely
> Cc: linuxppc-embedded@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@xilinx.com]
> Sent: Friday, May 16, 2008 6:34 PM
> To: Grant Likely; Koss, Mike (Mission Systems)
> Cc: linuxppc-embedded@ozlabs.org
> Subject: RE: arch/powerpc, Xilinx, and mainline kernel support
> =

> =

> =

> > -----Original Message-----
> > From: linuxppc-embedded-bounces+stephen=3Dneuendorffer.name@ozlabs.org
> [mailto:linuxppc-embedded-
> > bounces+stephen=3Dneuendorffer.name@ozlabs.org] On Behalf Of Grant
> Likely
> > Sent: Friday, May 16, 2008 3:27 PM
> > To: Koss, Mike (Mission Systems)
> > Cc: linuxppc-embedded@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@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.
> =

> =

> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@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.
> =

> =



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

      reply	other threads:[~2008-05-23 17:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 22:06 arch/powerpc, Xilinx, and mainline kernel support Koss, Mike (Mission Systems)
2008-05-16 22:26 ` Grant Likely
2008-05-16 22:34   ` Stephen Neuendorffer
2008-05-19 13:14     ` Koss, Mike (Mission Systems)
2008-05-23 15:09     ` Koss, Mike (Mission Systems)
2008-05-23 16:13       ` Stephen Neuendorffer
2008-05-23 16:44         ` Grant Likely
2008-05-27 14:31           ` Koss, Mike (Mission Systems)
2008-05-23 16:52       ` John Linn
2008-05-23 17:13         ` Koss, Mike (Mission Systems)
2008-05-23 17:15           ` Stephen Neuendorffer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080523171549.668DB16A806A@mail207-va3.bigfish.com \
    --to=stephen.neuendorffer@xilinx.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linnj@xilinx.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=mike.koss@ngc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox