On Mon, Jul 10, 2017 at 12:36 PM, Moritz Fischer
wrote:
>> +struct fpga_image_info *fpga_image_info_alloc(struct device *dev)
>> +{
>> + struct fpga_image_info *info;
>> +
>> + info = devm_kzalloc(dev, sizeof(*info), GFP_KERNEL);
>> + if (!info)
>> + return ERR_PTR
On Mon, Jul 10, 2017 at 12:36 PM, Moritz Fischer
wrote:
Hi Moritz,
Thanks for looking at this stuff.
>>
>> +struct fpga_image_info *fpga_image_info_alloc(struct device *dev)
>> +{
>> + struct fpga_image_info *info;
>> +
>> + info = devm_kzalloc(dev, sizeof(*info), GFP_KERNEL);
>> +
Hi Alan,
On Thu, Jul 6, 2017 at 11:47 AM, Alan Tull wrote:
> fpga-mgr has three methods for programming FPGAs, depending on
> whether the image is in a scatter gather list, a contiguous
> buffer, or a firmware file. This makes it difficult to write
> upper layers as the caller has to assume wheth
fpga-mgr has three methods for programming FPGAs, depending on
whether the image is in a scatter gather list, a contiguous
buffer, or a firmware file. This makes it difficult to write
upper layers as the caller has to assume whether the FPGA image
is in a sg table, as a single buffer, or a firmware
4 matches
Mail list logo