On Tue 11 Oct 06:39 PDT 2016, Matt Redfearn wrote:
> It is often desirable to be able to change the running firmware on a
> remote processor dynamically. This used to require a complete
> destruction and readdition of the struct rproc, but now that the
> firmware name is fixed length, it can be
On Tue 11 Oct 06:39 PDT 2016, Matt Redfearn wrote:
> It is often desirable to be able to change the running firmware on a
> remote processor dynamically. This used to require a complete
> destruction and readdition of the struct rproc, but now that the
> firmware name is fixed length, it can be
It is often desirable to be able to change the running firmware on a
remote processor dynamically. This used to require a complete
destruction and readdition of the struct rproc, but now that the
firmware name is fixed length, it can be updated freely.
So long as the remote processor is in
It is often desirable to be able to change the running firmware on a
remote processor dynamically. This used to require a complete
destruction and readdition of the struct rproc, but now that the
firmware name is fixed length, it can be updated freely.
So long as the remote processor is in
4 matches
Mail list logo
