From: Ben Hutchings <bhutchings@solarflare.com>
To: Ajit Khaparde <ajitk@serverengines.com>
Cc: davem@davemloft.net, jgarzik@pobox.com, netdev@vger.kernel.org
Subject: Re: [PATCH] ethtool: Add "-f" option to flash firmware image to a network device.
Date: Wed, 05 Aug 2009 13:48:23 +0100 [thread overview]
Message-ID: <1249476503.2781.3.camel@achroite> (raw)
In-Reply-To: <20090805123143.GA6592@serverengines.com>
On Wed, 2009-08-05 at 18:01 +0530, Ajit Khaparde wrote:
> Attached is a patch for ethtool utility to add a new "-f" option.
> This will enable flashing a firmware image to a network interface.
Which firmware? There can be several firmware images for controller,
PHY, host boot "ROM" and others.
[...]
> @@ -2398,6 +2404,20 @@ static int do_grxclass(int fd, struct ifreq
> *ifr)
> return 0;
> }
>
> +static int do_flash(int fd, struct ifreq *ifr)
> +{
> + int err;
> + struct ethtool_value ecmd;
> +
> + ecmd.cmd = ETHTOOL_FLASHDEV;
> + ifr->ifr_data = (caddr_t)&ecmd;
> + err = send_ioctl(fd, ifr);
> + if (err < 0)
> + perror("Flashing failed");
[..]
Where does the image come from? The running code? What about static
variables that have changed since startup?
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2009-08-05 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 12:31 [PATCH] ethtool: Add "-f" option to flash firmware image to a network device Ajit Khaparde
2009-08-05 12:48 ` Ben Hutchings [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=1249476503.2781.3.camel@achroite \
--to=bhutchings@solarflare.com \
--cc=ajitk@serverengines.com \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).