From: David Hawkins <dwh@ovro•caltech.edu>
To: Grant Likely <grant.likely@secretlab•ca>
Cc: Linux PPC <linuxppc-embedded@ozlabs•org>
Subject: Re: pcimsg patch from eons ago
Date: Tue, 29 May 2007 10:40:38 -0700 [thread overview]
Message-ID: <465C6596.4030208@ovro.caltech.edu> (raw)
In-Reply-To: <fa686aa40705282240p936fda6wdd838b8e33977ab3@mail.gmail.com>
Grant Likely wrote:
> Adrian,
>
> Way back in the 2.2 timeframe, you had modified the ARM pcimsg patch
> to port it to PPC and add features.
>
> http://www.cs.helsinki.fi/linux/linux-kernel/2001-07/0572.html
>
> I'd really like to take a look at it. I've been unable to find the
> patch archived anywhere online in my searching. Do you still have a
> copy of it tucked away anywhere?
>
Hey Grant,
TCP/IP over PCI is also something I want to look into.
I'll have about 8 compact PCI crates, with 15 MPC8349E boards
in each that I will boot with U-Boot, and then TFTP a kernel,
and then NFS mounted filesystem on. I'll put ethernet on
the front-panels for the prototype boards, but ideally
I want TCP/IP over PCI for the final system.
The board support package for the Freescale MPC8349E-MDS-PB
has some sort of support for this, but I haven't had a look
at the code yet.
I'm pretty sure Dan Malek had written something similar for
TCP/IP over RapidIO. Take a look in the kernel source,
I forget the name ... I have some notes around here somewhere ...
I'm working on hardware at the moment, so my software
brain cells are lying dormant. Let me know if you want
me to dig up the Freescale stuff and I'll send it to you,
or send you a link to a copy of the ISO. Downloading the
BSP from Freescale's site is a nightmare. I can also
plug the MDS board in as a peripheral and fire up their
TCP/IP over PCI and see what works.
It really shouldn't be too much trouble to get working.
I started by looking at the PLIP code just to see what
that took, and its pretty short. The most work would
be in defining infrastructure to make adding DMA of
data between the host CPU and the peripherals flexible.
Most (all?) x86 hosts don't have DMA, so both write and
read would be handled by the peripheral board. However,
for PPC hosts with DMA, then writes should be handled
by the respective boards ... I'm not sure what the
easiest way to deal with that would be.
Feel free to start a discussion on this :)
Cheers,
Dave
next prev parent reply other threads:[~2007-05-29 17:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 5:40 pcimsg patch from eons ago Grant Likely
2007-05-29 7:09 ` Adrian Cox
2007-05-29 13:37 ` Grant Likely
2007-05-29 17:40 ` David Hawkins [this message]
2007-05-29 18:25 ` Grant Likely
2007-05-30 21:53 ` sys_futex Charles Krinke
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=465C6596.4030208@ovro.caltech.edu \
--to=dwh@ovro$(echo .)caltech.edu \
--cc=grant.likely@secretlab$(echo .)ca \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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