On Tue, 22 Sep 2020 13:40:15 +0200 Stanislaw Kardach wrote:
> > So the driver loads the firmware contents, interprets them and programs
> > the device appropriately?
> >
> > Real firmware files are not usually interpreted or parsed by the driver.
>
> Correct. I'm using the firmware file as a de
On Mon, Sep 21, 2020 at 04:26:43PM -0700, Jakub Kicinski wrote:
> Date: Mon, 21 Sep 2020 16:26:43 -0700
> From: Jakub Kicinski
> To: Stanislaw Kardach
> Cc: da...@davemloft.net, sgout...@marvell.com, netdev@vger.kernel.org,
> k...@semihalf.com
> Subject: Re: [PATCH net-next v2
On Mon, 21 Sep 2020 19:54:42 +0200 Stanislaw Kardach wrote:
> Add ability to load a set of custom KPU entries via firmware APIs. This
> allows for flexible support for custom protocol parsing and CAM matching.
>
> The firmware file name is specified by a module parameter (kpu_profile)
> to allow r
Add ability to load a set of custom KPU entries via firmware APIs. This
allows for flexible support for custom protocol parsing and CAM matching.
The firmware file name is specified by a module parameter (kpu_profile)
to allow re-using the same kernel and initramfs package on nodes in
different pa
