From: Ben Hutchings <bhutchings@solarflare.com>
To: "Allan, Bruce W" <bruce.w.allan@intel.com>
Cc: David Miller <davem@davemloft.net>,
"csnook@redhat.com" <csnook@redhat.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [v2,PCI] move ICHx GbE NVM write-protection from e1000e to PCI quirk
Date: Mon, 17 Nov 2008 20:12:11 +0000 [thread overview]
Message-ID: <1226952732.3014.33.camel@achroite> (raw)
In-Reply-To: <B27EBC40D200ED48A3F4CC2EBEABAE0B238BF6E9@orsmsx501.amr.corp.intel.com>
On Mon, 2008-11-17 at 12:02 -0800, Allan, Bruce W wrote:
[...]
> Once the NVRAM is write-protected the driver cannot revoke that
> protection, only a system reset will do that. The kernel command line
> option to disable the write protection is so that if/when a user needs
> to change a value in the NVRAM it can still be done.
Although the ICHx write-protection bit is irreversible without a reset,
it works with SPI flash chips and these normally have their own write-
protection bits that can be switched on and off.
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.
next prev parent reply other threads:[~2008-11-17 20:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 3:12 [v2,PCI] move ICHx GbE NVM write-protection from e1000e to PCI quirk David Miller
2008-11-17 19:40 ` Chris Snook
2008-11-17 19:49 ` David Miller
2008-11-17 20:02 ` Allan, Bruce W
2008-11-17 20:12 ` Ben Hutchings [this message]
2008-11-17 20:20 ` David Miller
2008-11-17 23:56 ` Allan, Bruce W
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=1226952732.3014.33.camel@achroite \
--to=bhutchings@solarflare.com \
--cc=bruce.w.allan@intel.com \
--cc=csnook@redhat.com \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.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