From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [e1000-patches] [PATCH] igb: read flash with iomem=strict
Date: Tue, 12 Nov 2019 11:45:23 -0800 [thread overview]
Message-ID: <20191112114249.00002280@intel.com> (raw)
In-Reply-To: <498edf36e634b9590fd7f58fa7febde226bb3e6e.camel@intel.com>
On Tue, 12 Nov 2019 11:05:38 -0800 Jeff wrote:
> On Tue, 2019-11-12 at 13:03 +0000, Loktionov, Aleksandr wrote:
> > When Secure Boot is enabled access to the /dev/mem is forbidden for user-
> > space applications and clients are reporting inability to use tools in
> > Secure Boot Mode. The way to perform NVM update is to use igb driver.
> > Currently 1G Linux Base Driver has API which allows only EEPROM access.
> > There is a need to extend IOCTL API to allow NVM and registers access.
> > These defines are necessary for NVM access functions.
> >
> > Signed-off-by: Adam Ludkiewicz <adam.ludkiewicz@intel.com>
> > ---
>
> This patch only adds defines and macros which are not being used in the
> driver currently. It appears you are missing the code to actually use
> these defines. Your missing the changes that Adam made to igb_ethtool.c,
> which are currently being reviewed internally.
>
> Since this is an incomplete patch, I will drop it from the queue and will
> await a v2 of the patch that has the complete changes needed in the driver.
Not only that, but this is the same code that was just rejected for
the ice driver. I think we should NOT be trying to push this upstream,
knowing that it will likely be rejected.
next prev parent reply other threads:[~2019-11-12 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 13:03 [Intel-wired-lan] [e1000-patches] [PATCH] igb: read flash with iomem=strict Loktionov, Aleksandr
2019-11-12 19:05 ` Jeff Kirsher
2019-11-12 19:45 ` Jesse Brandeburg [this message]
2019-11-13 10:51 ` Loktionov, Aleksandr
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=20191112114249.00002280@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.