[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220219104255.smgqcqlez6sdo4hk@x260>
Date: Sat, 19 Feb 2022 13:42:55 +0300
From: Ivan Bornyakov <i.bornyakov@...rotek.ru>
To: Xu Yilun <yilun.xu@...el.com>
Cc: mdf@...nel.org, hao.wu@...el.com, trix@...hat.com,
conor.dooley@...rochip.com, linux-kernel@...r.kernel.org,
linux-fpga@...r.kernel.org, system@...rotek.ru
Subject: Re: [PATCH v4] fpga: microchip-spi: add Microchip FPGA manager
On Sat, Feb 19, 2022 at 09:16:27AM +0300, Ivan Bornyakov wrote:
> On Sat, Feb 19, 2022 at 12:05:55AM +0800, Xu Yilun wrote:
> >
> > Maybe the bitstream info at the head of the image could be parsed in
> > write_init(), and this requires the driver fill the
> > fpga_manager_ops.initial_header_size
> >
>
> Header size is not known beforehand and is stored in 25th byte of the
> image.
>
Actually I was not quite accurate here. The header itself seems to be of
constant size according to
https://coredocs.s3.amazonaws.com/DirectC/2021_2/spi_directc.pdf
(4. Data File Format)
But the lookup table is definitely of a variable size. Moreover
bitstream start and size both are somewhere in the image and needed
to be located through lookup table.
Powered by blists - more mailing lists