From: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>
To: "Grant Likely" <grant.likely@secretlab.ca>,
"Jean-Samuel Chenard" <jsamch@macs.ece.mcgill.ca>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Xilinx ML310 Linux 2.6 PCI bridge
Date: Sun, 9 Dec 2007 21:46:57 -0800 [thread overview]
Message-ID: <20071210054659.D373C16006E@mail51-dub.bigfish.com> (raw)
In-Reply-To: fa686aa40712091223x3efb1143kfd81277890fb74ae@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 2337 bytes --]
I would strongly recommend not spending a huge amount of time on the ml310. The University program board is dirt cheap for universities, very well supported under Linux, using either secretlab.ca or git.xilinx.com and you won't spend your time getting PCI to place and route correctly, followed by figuring out how to get Linux to talk to it nicely.
If your lab can afford a bee2, then you should be able to afford one (or better yet, several) xupv2p's to go with it.
http://www.xilinx.com/univ/xupv2p.html
Steve
-----Original Message-----
From: linuxppc-embedded-bounces+stephen=neuendorffer.name@ozlabs.org on behalf of Grant Likely
Sent: Sun 12/9/2007 12:23 PM
To: Jean-Samuel Chenard
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Xilinx ML310 Linux 2.6 PCI bridge
On 12/9/07, Jean-Samuel Chenard <jsamch@macs.ece.mcgill.ca> wrote:
> On Dec 9, 2007 1:18 AM, Grant Likely <grant.likely@secretlab.ca> wrote:
> > On 12/8/07, Jean-Samuel Chenard <jsamch@macs.ece.mcgill.ca> wrote:
> > > Thanks to the valuable information provided by this discussion group and
> > > particularly by Grant Likely from Secret Lab Technologies, I was able to
> > > setup and run Linux 2.6 on my ML-310 development platform.
> >
> > Congratulations. If you had to make any changes to get it to work
> > then please send me your patches.
>
> Thank you for the quick reply.
No problem.
>
> I will directly update Secret Lab's Wiki pages. Those pages are the
> ones that got me going really quickly, so I will add a few of my
> observations directly on your pages so everyone can benefit.
Much appreciated; thank you!
> My real target is the control FPGA on a BEE2 box
> (http://bee2.eecs.berkeley.edu) and on that particular setup, the
> control FPGA is directly connected to an LXT971A Ethernet PHY, so I'll
> use the ethernet MAC from Xilinx.
Cool platform. Yes, you should have much better luck with the EMAC
core. The driver needs some work to be acceptable for mainline, but
it should be functional.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
[-- Attachment #2: Type: text/html, Size: 3247 bytes --]
next prev parent reply other threads:[~2007-12-10 5:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 5:51 Xilinx ML310 Linux 2.6 PCI bridge Jean-Samuel Chenard
2007-12-09 6:18 ` Grant Likely
2007-12-09 17:32 ` Jean-Samuel Chenard
2007-12-09 20:23 ` Grant Likely
2007-12-10 5:46 ` Stephen Neuendorffer [this message]
2007-12-10 16:33 ` Jean-Samuel Chenard
2007-12-10 18:47 ` Stephen Neuendorffer
2007-12-13 16:46 ` Grant Likely
2007-12-10 23:57 ` Rick Moleres
2007-12-11 0:20 ` Grant Likely
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=20071210054659.D373C16006E@mail51-dub.bigfish.com \
--to=stephen.neuendorffer@xilinx.com \
--cc=grant.likely@secretlab.ca \
--cc=jsamch@macs.ece.mcgill.ca \
--cc=linuxppc-embedded@ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.