Excerpts from christophe lombard's message of 2016-02-16 07:53:54 +1100:
+void cxl_guest_reload_module(struct cxl *adapter)
+{
+struct platform_device *pdev;
+int afu;
+
+for (afu = 0; afu < adapter->slices; afu++)
+cxl_guest_remove_afu(adapter->afu[afu]);
Should we possibly
Excerpts from christophe lombard's message of 2016-02-16 07:53:54 +1100:
> >> +void cxl_guest_reload_module(struct cxl *adapter)
> >> +{
> >> +struct platform_device *pdev;
> >> +int afu;
> >> +
> >> +for (afu = 0; afu < adapter->slices; afu++)
> >> +cxl_guest_remove_afu(adapter
@mpe since this patch introduces a new user API I'd appreciate it if you
could give this a bit extra scrutiny.
Excerpts from Frederic Barrat's message of 2016-02-07 00:29:01 +1100:
+Starts and controls flashing a new FPGA image. Partial
+reconfiguration is not supported (yet), so the ima
@mpe since this patch introduces a new user API I'd appreciate it if you
could give this a bit extra scrutiny.
Excerpts from Frederic Barrat's message of 2016-02-07 00:29:01 +1100:
> +Starts and controls flashing a new FPGA image. Partial
> +reconfiguration is not supported (yet), so the i
From: Christophe Lombard
The new flash.c file contains the logic to flash a new image on the
adapter, through a hcall. It is an iterative process, with chunks of
data of 1M at a time. There are also 2 phases: write and verify. The
flash operation itself is driven from a user-land tool.
Once flas
