[lkml]   [2012]   [Dec]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 2/2] New driver: Xillybus generic interface for FPGA (programmable logic)
On 12/01/2012 10:48 PM, Arnd Bergmann wrote:
> I agree that is a concern, but for now, I'm mostly worried about
> the kernel-to-user interface. If we can agree on a driver interface
> that works for Xillybus as well as any of the others we know about,
> we can start using that as the generic kernel FPGA interface.
> Once we get a second FPGA driver, that can use the same user
> interface but talk to the hardware in a different way, and then
> we can reorganise the code to keep the user interface bits in a
> common driver, away from the hardware specific parts.
> If you see anything in the user interface that directly depends on
> the Xillybus IP block, then that would make the approach impossible
> and we should change that to be more generic.

The whole idea about Xillybus was not to invent a new user space
interface. A lot of effort has been put in to make the device files
behave like named pipes. For example, it makes perfect sense to go

$ cat mydata > /dev/xillybus_my_data_sink

knowing that the data will arrive as one would expect to the FPGA.

On my next patch submission, I'll include a documentation file, which
will describe the fine details. But don't expect much on the API side:
All of the configuration is already done on the hardware (FPGA) side,
and the driver merely detects the pipes and their attributes.

All that is left for the user space programmer is to exercise common
UNIX programming practices, and things will work as expected. Or at
least, this is the intention.


 \ /
  Last update: 2012-12-02 14:21    [W:0.174 / U:0.116 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site