[PATCH v3 2/2] cmd: brcm: netXtreme commands

Marek Behún kabel at kernel.org
Wed Oct 27 19:39:34 CEST 2021


On Wed, 27 Oct 2021 10:02:41 -0700
Roman Bacik <roman.bacik at broadcom.com> wrote:

> Marek, Simon,
> 
> Thank you very much for your comments. We will remove bnxt commands and will
> probe bnxt driver each boot in the next version.
> Thanks,

Roman

I think that the idea of not loading fw or initializing the controller
during every boot, but only when needed, is quite reasonable.

But it has to be done without the need to call custom commands, which
the user may not know about.

It has to be done in such a way that if the user calls for example the
  dhcp
command, it will work.

I think this could be achieved by creating a new DM driver flag, and
wiring the DM and/or PCI code so that when this flag is set, the PCI
subsystem won't probe the driver, only bind the driver.

That way U-Boot will know that there is another ethernet controller
which can be used by network commands when the `ethact` variable is set
to point to that controller.

Marek


More information about the U-Boot mailing list