public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Roman Bacik <roman.bacik@broadcom.com>
To: "Marek Behún" <kabel@kernel.org>
Cc: Simon Glass <sjg@chromium.org>,
	U-Boot Mailing List <u-boot@lists.denx.de>,
	Bharat Gooty <bharat.gooty@broadcom.com>,
	Aswath Govindraju <a-govindraju@ti.com>,
	 Bin Meng <bmeng.cn@gmail.com>,
	Franck LENORMAND <franck.lenormand@nxp.com>,
	 Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Kory Maincent <kory.maincent@bootlin.com>,
	 Michal Simek <michal.simek@xilinx.com>,
	Patrick Delaunay <patrick.delaunay@foss.st.com>,
	 Peng Fan <peng.fan@nxp.com>,
	Priyanka Jain <priyanka.jain@nxp.com>,
	 Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>,
	Sean Anderson <sean.anderson@seco.com>
Subject: RE: [PATCH v3 2/2] cmd: brcm: netXtreme commands
Date: Wed, 27 Oct 2021 10:58:35 -0700	[thread overview]
Message-ID: <72f20fb53c98ef42a90f73d2fa4914dc@mail.gmail.com> (raw)
In-Reply-To: <20211027193934.4f537495@thinkpad>

[-- Attachment #1: Type: text/plain, Size: 2838 bytes --]

Hi Marek,

> -----Original Message-----
> From: Marek Behún <kabel@kernel.org>
> Sent: Wednesday, October 27, 2021 10:40 AM
> To: Roman Bacik <roman.bacik@broadcom.com>
> Cc: Simon Glass <sjg@chromium.org>; U-Boot Mailing List <u-
> boot@lists.denx.de>; Bharat Gooty <bharat.gooty@broadcom.com>;
> Aswath Govindraju <a-govindraju@ti.com>; Bin Meng
> <bmeng.cn@gmail.com>; Franck LENORMAND
> <franck.lenormand@nxp.com>; Heinrich Schuchardt
> <xypron.glpk@gmx.de>; Kory Maincent <kory.maincent@bootlin.com>;
> Michal Simek <michal.simek@xilinx.com>; Patrick Delaunay
> <patrick.delaunay@foss.st.com>; Peng Fan <peng.fan@nxp.com>; Priyanka
> Jain <priyanka.jain@nxp.com>; Rayagonda Kokatanur
> <rayagonda.kokatanur@broadcom.com>; Sean Anderson
> <sean.anderson@seco.com>
> Subject: Re: [PATCH v3 2/2] cmd: brcm: netXtreme commands
>
> On Wed, 27 Oct 2021 10:02:41 -0700
> Roman Bacik <roman.bacik@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.

Thank you very much for your suggestion. To simplify, we will decouple
this issue from the current bnxt driver submission.

>
> 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

Thanks,

Roman

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]

  reply	other threads:[~2021-10-27 17:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 23:44 [PATCH v3 1/2] net: brcm: netXtreme driver Roman Bacik
2021-10-25 23:44 ` [PATCH v3 2/2] cmd: brcm: netXtreme commands Roman Bacik
2021-10-26 13:17   ` Marek Behún
2021-10-26 15:14     ` Roman Bacik
2021-10-26 15:55       ` Marek Behún
2021-10-26 16:02         ` Roman Bacik
2021-10-26 16:40           ` Roman Bacik
2021-10-26 16:52             ` Marek Behún
2021-10-26 16:59               ` Roman Bacik
2021-10-26 16:49           ` Marek Behún
2021-10-27 15:05             ` Roman Bacik
2021-10-27 15:41               ` Simon Glass
2021-10-27 16:05                 ` Roman Bacik
2021-10-27 16:35               ` Marek Behún
2021-10-27 16:47                 ` Roman Bacik
2021-10-27 17:02                   ` Roman Bacik
2021-10-27 17:39                     ` Marek Behún
2021-10-27 17:58                       ` Roman Bacik [this message]
2021-10-27 18:02                         ` Marek Behún

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=72f20fb53c98ef42a90f73d2fa4914dc@mail.gmail.com \
    --to=roman.bacik@broadcom.com \
    --cc=a-govindraju@ti.com \
    --cc=bharat.gooty@broadcom.com \
    --cc=bmeng.cn@gmail.com \
    --cc=franck.lenormand@nxp.com \
    --cc=kabel@kernel.org \
    --cc=kory.maincent@bootlin.com \
    --cc=michal.simek@xilinx.com \
    --cc=patrick.delaunay@foss.st.com \
    --cc=peng.fan@nxp.com \
    --cc=priyanka.jain@nxp.com \
    --cc=rayagonda.kokatanur@broadcom.com \
    --cc=sean.anderson@seco.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox