From: "Jean-Samuel Chenard" <jsamch@macs.ece.mcgill.ca>
To: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Xilinx ML310 Linux 2.6 PCI bridge
Date: Mon, 10 Dec 2007 11:33:51 -0500 [thread overview]
Message-ID: <169c03cb0712100833m36842bf7j95aab235f67b5250@mail.gmail.com> (raw)
In-Reply-To: <20071210054659.D373C16006E@mail51-dub.bigfish.com>
On Dec 10, 2007 12:46 AM, Stephen Neuendorffer
<stephen.neuendorffer@xilinx.com> wrote:
> I would strongly recommend not spending a huge amount of time on the ml31=
0.
> The University program board is dirt cheap for universities, very well
> supported under Linux, using either secretlab.ca or git.xilinx.com and yo=
u
> 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.
Hi Stephen,
Thanks for the insight. I was aware of the XUP V2P board and I think
this is a nice initiative to let students use some great technology.
> 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.
That's where things get complicated... In our lab, we get expensive
hardware such as the BEE2 via CMC Microsystems (a Canadian granting
agency). However, getting funds locally to buy other equipment is a
relatively long and administratively complex process...
One of my colleague did not use his ML-310 board so I got a hold of it
(in a day, with little overhead). So far, the ML-310 has helped me
bring up Linux 2.6 and experiment most of what I need to use on the
BEE2. I am only missing the networking. This would make things much
nicer to work via a NFS-exported root file system. However, I'm OK
swapping the CompactFlash card...
I find it strange that Xilinx would not invest in supporting Linux 2.6
for an important feature such as a PCI bridge (not specifically for
the ML-310, but in general) when this can bring many interesting
benefits to an embedded platform. Is this something that is "in
progress" at Xilinx? You seem to imply that most of the difficulty in
getting the PCI core working is in meeting the timing requirements
(not with the SW drivers), so I might be missing driver files when I
generate the BSP code for Linux 2.6.
Regards,
Jean-Samuel
--=20
Integrated Microsystems Laboratory
McGill University, Montr=E9al, QC, CANADA
Web Page: http://chaos.ece.mcgill.ca
next prev parent reply other threads:[~2007-12-10 16:33 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
2007-12-10 16:33 ` Jean-Samuel Chenard [this message]
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=169c03cb0712100833m36842bf7j95aab235f67b5250@mail.gmail.com \
--to=jsamch@macs.ece.mcgill.ca \
--cc=linuxppc-embedded@ozlabs.org \
--cc=stephen.neuendorffer@xilinx.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;
as well as URLs for NNTP newsgroup(s).