From: Greg KH <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Eli Billauer <eli.billauer@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] New driver: Xillybus generic interface for FPGA (programmable logic)
Date: Wed, 5 Dec 2012 07:48:00 -0800 [thread overview]
Message-ID: <20121205154800.GA4025@kroah.com> (raw)
In-Reply-To: <201212042043.18221.arnd@arndb.de>
On Tue, Dec 04, 2012 at 08:43:18PM +0000, Arnd Bergmann wrote:
> On Tuesday 04 December 2012, Eli Billauer wrote:
> > I'm currently writing some documentation which will cover the API and
> > also help reading the code, I hope. It takes some time...
> >
> > Until it's done, let's look at a usage example: Suppose that the FPGA's
> > application is to receive a high-speed bitstream with time multiplexed
> > data, demultiplex the bitstream into individual channel streams, and
> > send each channel's data to the host. And let's say that there are 64
> > channels in original bitstream. So the FPGA has now 64 independent
> > sources of data.
> >
> > For that purpose, the Xillybus IP core (on the FPGA) is configured to
> > create 64 pipes for FPGA to host communication. The names of these pipes
> > (say, "chan00", "chan01", ...) are also stored in the FPGA.
> >
> > When the driver starts, it queries the FPGA for its Xillybus
> > configuration, and creates 64 device nodes: /dev/xillybus_chan00,
> > /dev/xillybus_chan01, ... /dev/xillybus_chan63.
> >
> > If the user wants to dump the data in channel 43 into a file, it's just:
> >
> > $ cat /dev/xillybus_chan43 > mydump.dat
> >
> > I hope this clarified things a bit.
> >
> > I can't see how the firmware interface would help here.
>
> I think a lot of us (including Greg and me) were confused about
> the purpose of the driver, since you did not include much documentation.
>
> The request_firmware interface would be useful for loading a model
> into the FPGA, but that doesn't seem to be what your driver is
> concerned with. It's also a bit confusing because it doesn't appear
> to be a "bus" in the Linux sense of being something that provides
> an abstract interface between hardware and kernel device drivers.
Yes, that's what I was confused about as well. I'll wait for a new
patch with new documentation, before commenting further.
greg k-h
next prev parent reply other threads:[~2012-12-05 15:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 15:41 [PATCH 1/2] pci_ids: Added FPGA-related entries Eli Billauer
2012-11-28 15:41 ` [PATCH 2/2] New driver: Xillybus generic interface for FPGA (programmable logic) Eli Billauer
2012-11-28 16:57 ` Greg KH
2012-11-30 14:50 ` Eli Billauer
2012-11-30 16:32 ` Greg KH
2012-11-30 16:58 ` Eli Billauer
2012-11-30 17:32 ` Arnd Bergmann
2012-12-02 17:26 ` Eli Billauer
2012-12-04 3:41 ` Greg KH
2012-12-04 10:13 ` Eli Billauer
2012-12-04 20:43 ` Arnd Bergmann
2012-12-04 21:42 ` Eli Billauer
2012-12-04 23:05 ` Arnd Bergmann
2012-12-05 0:03 ` Eli Billauer
2012-12-05 15:48 ` Greg KH [this message]
2012-11-30 17:28 ` Arnd Bergmann
2012-11-30 17:36 ` Greg KH
2012-12-01 3:19 ` Philip Balister
2012-12-01 16:56 ` Greg KH
2012-12-01 16:58 ` Greg KH
2012-12-01 19:30 ` Philip Balister
2012-12-01 20:33 ` Josh Cartwright
2012-12-01 20:48 ` Arnd Bergmann
2012-12-02 12:38 ` Eli Billauer
2012-12-03 20:24 ` John Linn
2012-12-04 19:49 ` Philip Balister
2012-12-04 20:54 ` Arnd Bergmann
2012-12-05 12:34 ` Pavel Machek
2012-11-28 16:50 ` [PATCH 1/2] pci_ids: Added FPGA-related entries Greg KH
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=20121205154800.GA4025@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=eli.billauer@gmail.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome