Re: [RFC PATCH] fpga: Introduce new fpga subsystem

[Michal Simek]

On 09/19/2013 12:08 PM, Pavel Machek wrote:
> Hi!
> 
>> The firmware approach is interesting.  It might be less flexible
>> compared with my original code (see link to git below) that this is
> 
> On the other hand... that's the interface world wants, right? To most
> users, fpga bitstream is just a firmware.

It is one nice way how to get data from one place to another and
it is easy to handle. Using different methods is also possible.

>> Is there some way a per-device userspace helper can be added that can
>> handle adding the headers?  Such that different fpga types get different
>> helpers?
> 
> https://www.kernel.org/doc/Documentation/firmware_class/README
> 
>  4), userspace:
>      - hotplug: cat appropriate_firmware_image > \
>        		    			       /sys/class/firmware/xxx/data
> 
> I assume udev's firmware.sh could be modified to add headers.
> 
> But... if same bitstream is expected to work across multiple FPGAs (is
> it?) maybe kernel should hide that difference and provide headers
> itself.

There could be a configuration where you want to load one bitstream
to more fpgas with the same type. I can imagine this system and use cases.

Thanks,
Michal


-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform

Attachment: signature.asc
Description: OpenPGP digital signature