mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chien, Richard (Options Engineering)" <richard.chien@hpe.com>
To: Andrew Lunn <andrew@lunn.ch>, Richard chien <m8809301@gmail.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"jesse.brandeburg@intel.com" <jesse.brandeburg@intel.com>,
	"anthony.l.nguyen@intel.com" <anthony.l.nguyen@intel.com>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] ixgbe: Add support for firmware update
Date: Tue, 11 Jun 2024 07:12:58 +0000	[thread overview]
Message-ID: <PH7PR84MB1581644F8E16BBD49AC451BEE8C72@PH7PR84MB1581.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <e9b5eef7-8325-4d71-bbb6-ba063733484c@lunn.ch>

> I would also think about why Intel has not submitted this code before?
> Maybe because it does things the wrong way? Please look at how other
> Ethernet drivers support firmware. Is it the same? It might be you need to
> throw away this code and reimplement it to mainline standards, maybe using
> devlink flash, or ethtool -f.

See Jacob's reply for details.
 
> One additional question. Is the firmware part of linux-firmware? Given this is
> Intel, i expect the firmware is distributeable, but have they distributed it?

It is the Intel 10G NIC firmware embedded into HPE firmware update packages and redistributed to the end user.

Thanks,
Richard

      reply	other threads:[~2024-06-11  7:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-09  8:57 Richard chien
2024-06-09 11:23 ` Markus Elfring
2024-06-09 22:33 ` kernel test robot
2024-06-10 19:36 ` Andrew Lunn
2024-06-11  7:12   ` Chien, Richard (Options Engineering) [this message]

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=PH7PR84MB1581644F8E16BBD49AC451BEE8C72@PH7PR84MB1581.NAMPRD84.PROD.OUTLOOK.COM \
    --to=richard.chien@hpe.com \
    --cc=andrew@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m8809301@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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
all inboxes | Powered by JetHome®