Hi!
> [resend with fixed email settings]
>
> The idea of the framework is to provide consistent ways of
> programming raw images into FPGA's.
>
> Programming from device tree overlays is supported.
>
> The core (fpga-mgr.c) does not include a userspace interface
> and just exports kernel functions.
>
> This approach separates the core from the interfaces.
>
> Each interface can be enabled or disabled in the defconfig.
> In some production contexts, interfaces that might be used
> during development can be disabled.
>
> The core exports kernel functions to:
> * write the fpga from a buffer or using the firmware layer
> * get fpga status
> * find a particular fpga manager from a device tree phandle
> * register/unregister lower level fpga drivers.
>
> The bus allows us to:
> * program fpga from a device tree overlay using firmware.
> * automatically reload firmware and reprogram fpga during resume.
>
> The sysfs interface:
> * read only, get the name and status of fpga manager.
>
> I have a configfs interface patch which I haven't included,
> adds configfs as a separate file.
Thanks for the patches... is there new version? Is that corresponding
socfpga code?
I'd like to configure fpga with .rbf file on board similar to SocKit.
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
