From: "Ira W. Snyder" <iws@ovro.caltech.edu>
To: linuxppc-dev@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, "Ira W. Snyder" <iws@ovro.caltech.edu>
Subject: [PATCH RFCv1 0/3] CARMA Board Support
Date: Fri, 3 Sep 2010 15:30:49 -0700 [thread overview]
Message-ID: <1283553052-23576-1-git-send-email-iws@ovro.caltech.edu> (raw)
Hello everyone,
Yesterday I asked where board specific drivers should be located in the
source tree. Several people suggested I just post the drivers for review
right away, and let the reviewers comment on where to put the drivers.
Here they are. I've created a new drivers/fpga/carma/ directory for the
drivers. I expect that this will not be their final resting place.
The CARMA board is essentially an MPC8349EA MDS reference design with a
1GHz ADC and 4 high powered data processing FPGAs connected to the local
bus. It is all packed into a compact PCI form factor. It is used at the
Owens Valley Radio Observatory as the main component in the correlator
system.
For more information, see this webpage, maintained by the board's hardware
engineer: http://www.mmarray.org/~dwh/carma_board/index.html
These drivers are the necessary pieces to get the data processing FPGAs
working and producing data. Despite the fact that the hardware is custom
and we are the only users, I'd still like to get the drivers upstream.
Several people have suggested that this is possible.
Some further patches will be forthcoming. I have a driver for the LED
subsystem and the PPS subsystem. The LED register layout is expected to
change soon, so I won't post the driver until that is finished. The PPS
driver will be posted seperately from this patch series; it is very
generic.
Thanks for any review and comments you can offer!
Ira
Ira W. Snyder (3):
fpga: add basic CARMA board support
fpga: add CARMA DATA-FPGA Access Driver
fpga: add CARMA DATA-FPGA Programmer support
drivers/Kconfig | 2 +
drivers/Makefile | 1 +
drivers/fpga/Kconfig | 1 +
drivers/fpga/Makefile | 1 +
drivers/fpga/carma/Kconfig | 38 +
drivers/fpga/carma/Makefile | 3 +
drivers/fpga/carma/carma-fpga-program.c | 1136 ++++++++++++++++++++++++
drivers/fpga/carma/carma-fpga.c | 1447 +++++++++++++++++++++++++++++++
drivers/fpga/carma/carma.c | 73 ++
drivers/fpga/carma/carma.h | 22 +
10 files changed, 2724 insertions(+), 0 deletions(-)
create mode 100644 drivers/fpga/Kconfig
create mode 100644 drivers/fpga/Makefile
create mode 100644 drivers/fpga/carma/Kconfig
create mode 100644 drivers/fpga/carma/Makefile
create mode 100644 drivers/fpga/carma/carma-fpga-program.c
create mode 100644 drivers/fpga/carma/carma-fpga.c
create mode 100644 drivers/fpga/carma/carma.c
create mode 100644 drivers/fpga/carma/carma.h
next reply other threads:[~2010-09-03 22:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 22:30 Ira W. Snyder [this message]
2010-09-03 22:30 ` [PATCH RFCv1 1/3] fpga: add basic CARMA board support Ira W. Snyder
2010-09-03 22:30 ` [PATCH RFCv1 2/3] fpga: add CARMA DATA-FPGA Access Driver Ira W. Snyder
2010-09-03 22:44 ` Randy Dunlap
2010-09-03 22:30 ` [PATCH RFCv1 3/3] fpga: add CARMA DATA-FPGA Programmer support Ira W. Snyder
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=1283553052-23576-1-git-send-email-iws@ovro.caltech.edu \
--to=iws@ovro.caltech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox