On Thu, 19 Nov 2015, Moritz Fischer wrote:
> Hi Alan,
>
> while trying to implement something that works for Zynq along these lines
> I stumbled upon some minor stuff.
>
> On Tue, Nov 3, 2015 at 9:11 AM, wrote:
>
> > + * Return: 0 on success, negative error code otherwise.
> > + */
> > +int
On Thu, 19 Nov 2015, Moritz Fischer wrote:
> Hi Alan,
>
> while trying to implement something that works for Zynq along these lines
> I stumbled upon some minor stuff.
>
> On Tue, Nov 3, 2015 at 9:11 AM, wrote:
>
> > + * Return: 0 on success, negative error code
Hi Alan,
while trying to implement something that works for Zynq along these lines
I stumbled upon some minor stuff.
On Tue, Nov 3, 2015 at 9:11 AM, wrote:
> + * Return: 0 on success, negative error code otherwise.
> + */
> +int fpga_bridge_register(struct device *dev, const char *name,
> +
Hi Alan,
while trying to implement something that works for Zynq along these lines
I stumbled upon some minor stuff.
On Tue, Nov 3, 2015 at 9:11 AM, wrote:
> + * Return: 0 on success, negative error code otherwise.
> + */
> +int fpga_bridge_register(struct device
From: Alan Tull
This framework adds API functions for enabling/
disabling FPGA bridges under kernel control.
This allows the Linux kernel to disable FPGA bridges
during FPGA reprogramming and to enable FPGA bridges
when FPGA reprogramming is done. This framework is
be manufacturer-agnostic,
From: Alan Tull
This framework adds API functions for enabling/
disabling FPGA bridges under kernel control.
This allows the Linux kernel to disable FPGA bridges
during FPGA reprogramming and to enable FPGA bridges
when FPGA reprogramming is done. This framework is
6 matches
Mail list logo