All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: David Miller <davem@davemloft.net>
Cc: jkosina@suse.cz, jeffrey.t.kirsher@intel.com, jeff@garzik.org,
	mingo@elte.hu, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, jesse.brandeburg@intel.com,
	john.ronciak@intel.com, bruce.w.allan@intel.com
Subject: Re: [PATCH 2/3] e1000e: Useset_memory_ro()/set_memory_rw() to protect flash memory
Date: Wed, 24 Sep 2008 12:51:01 +0200	[thread overview]
Message-ID: <48DA1B95.5030806@s5r6.in-berlin.de> (raw)
In-Reply-To: <20080923.164745.12711639.davem@davemloft.net>

David Miller wrote:
> From: Jiri Kosina <jkosina@suse.cz>
> Date: Wed, 24 Sep 2008 01:45:53 +0200 (CEST)
> 
>> Yes, probably not a vanilla kernel material, but could be very well used 
>> for testing to further isolate whether it is kernel or userspace 
>> corrupting the memory mapped eeprom.
> 
> Absolutely.

Would it help and would it be feasible to drastically shorten the 
lifetime of the MMIO mapping?  I.e. only have it mapped briefly during 
the driver probe, and temporarily whenever a userspace tool like ethtool 
needs it.
-- 
Stefan Richter
-=====-==--- =--= ==---
http://arcgraph.de/sr/

  reply	other threads:[~2008-09-24 10:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23 22:45 [PATCH 2/3] e1000e: Useset_memory_ro()/set_memory_rw() to protect flash memory Jeff Kirsher
2008-09-23 23:29 ` David Miller
2008-09-23 23:45   ` Jiri Kosina
2008-09-23 23:47     ` David Miller
2008-09-24 10:51       ` Stefan Richter [this message]
2008-09-24 17:53 ` Kyle McMartin
2008-09-24 18:13   ` Allan, Bruce W
2008-09-24 22:55   ` Jiri Kosina

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=48DA1B95.5030806@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=bruce.w.allan@intel.com \
    --cc=davem@davemloft.net \
    --cc=jeff@garzik.org \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=jkosina@suse.cz \
    --cc=john.ronciak@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 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.