On 5/23/2017 10:25 AM, Alan Tull wrote:
On Tue, May 23, 2017 at 10:21 AM, Alan Tull wrote:
+
+ mgr->state = FPGA_MGR_STATE_FIRMWARE_REQ;
+ while (length > 0) {
This could be "do { ... } while ((params.fw_size >= FIRMWARE_CHUNK_SZ)
&& (length > 0));" since
On 5/23/2017 10:25 AM, Alan Tull wrote:
On Tue, May 23, 2017 at 10:21 AM, Alan Tull wrote:
+
+ mgr->state = FPGA_MGR_STATE_FIRMWARE_REQ;
+ while (length > 0) {
This could be "do { ... } while ((params.fw_size >= FIRMWARE_CHUNK_SZ)
&& (length > 0));" since that's what it's
On 5/23/2017 10:25 AM, Alan Tull wrote:
On Tue, May 23, 2017 at 10:21 AM, Alan Tull wrote:
+
+ mgr->state = FPGA_MGR_STATE_FIRMWARE_REQ;
+ while (length > 0) {
This could be "do { ... } while ((params.fw_size >= FIRMWARE_CHUNK_SZ)
&& (length > 0));" since
On 5/23/2017 10:25 AM, Alan Tull wrote:
On Tue, May 23, 2017 at 10:21 AM, Alan Tull wrote:
+
+ mgr->state = FPGA_MGR_STATE_FIRMWARE_REQ;
+ while (length > 0) {
This could be "do { ... } while ((params.fw_size >= FIRMWARE_CHUNK_SZ)
&& (length > 0));" since that's what it's
On Tue, May 23, 2017 at 10:21 AM, Alan Tull wrote:
+
+ mgr->state = FPGA_MGR_STATE_FIRMWARE_REQ;
+ while (length > 0) {
>>>
>>> This could be "do { ... } while ((params.fw_size >= FIRMWARE_CHUNK_SZ)
>>> && (length > 0));" since that's what it's really
On Tue, May 23, 2017 at 10:21 AM, Alan Tull wrote:
+
+ mgr->state = FPGA_MGR_STATE_FIRMWARE_REQ;
+ while (length > 0) {
>>>
>>> This could be "do { ... } while ((params.fw_size >= FIRMWARE_CHUNK_SZ)
>>> && (length > 0));" since that's what it's really doing.
>>
>> Yes,
On Mon, May 22, 2017 at 11:11 PM, Li, Yi wrote:
> hi Alan
>
>
> On 5/22/2017 4:09 PM, Alan Tull wrote:
>>
>> On Sat, May 20, 2017 at 1:49 AM, wrote:
>>
>> Hi Yi,
>>
>>> From: Yi Li
>>>
>>> Since the FPGA image are getting
On Mon, May 22, 2017 at 11:11 PM, Li, Yi wrote:
> hi Alan
>
>
> On 5/22/2017 4:09 PM, Alan Tull wrote:
>>
>> On Sat, May 20, 2017 at 1:49 AM, wrote:
>>
>> Hi Yi,
>>
>>> From: Yi Li
>>>
>>> Since the FPGA image are getting bigger in size, this add an new API
>>> fpga_mgr_firmware_stream
>>
>>
hi Alan
On 5/22/2017 4:09 PM, Alan Tull wrote:
On Sat, May 20, 2017 at 1:49 AM, wrote:
Hi Yi,
From: Yi Li
Since the FPGA image are getting bigger in size, this add an new API
fpga_mgr_firmware_stream
You could replace the guts of the
hi Alan
On 5/22/2017 4:09 PM, Alan Tull wrote:
On Sat, May 20, 2017 at 1:49 AM, wrote:
Hi Yi,
From: Yi Li
Since the FPGA image are getting bigger in size, this add an new API
fpga_mgr_firmware_stream
You could replace the guts of the current fpga_mgr_firmware_load()
with this new API
On Sat, May 20, 2017 at 1:49 AM, wrote:
Hi Yi,
> From: Yi Li
>
> Since the FPGA image are getting bigger in size, this add an new API
> fpga_mgr_firmware_stream
You could replace the guts of the current fpga_mgr_firmware_load()
with this new
On Sat, May 20, 2017 at 1:49 AM, wrote:
Hi Yi,
> From: Yi Li
>
> Since the FPGA image are getting bigger in size, this add an new API
> fpga_mgr_firmware_stream
You could replace the guts of the current fpga_mgr_firmware_load()
with this new API (keep the old name). Unless anyone can think
From: Yi Li
Since the FPGA image are getting bigger in size, this add an new API
fpga_mgr_firmware_stream in FPGA manager, which will stream FPGA image in
4KB trunks.
Signed-off-by: Yi Li
---
drivers/fpga/fpga-mgr.c | 111
From: Yi Li
Since the FPGA image are getting bigger in size, this add an new API
fpga_mgr_firmware_stream in FPGA manager, which will stream FPGA image in
4KB trunks.
Signed-off-by: Yi Li
---
drivers/fpga/fpga-mgr.c | 111 ++
14 matches
Mail list logo