[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <36D9DB17C6DE9E40B059440DB8D95F5206446B4E@orsmsx418.amr.corp.intel.com>
Date: Fri, 26 Sep 2008 15:23:39 -0700
From: "Brandeburg, Jesse" <jesse.brandeburg@...el.com>
To: "Krzysztof Halasa" <khc@...waw.pl>, "Tim Gardner" <timg@....com>
Cc: "Jesse Barnes" <jbarnes@...tuousgeek.org>,
"Arjan van de Ven" <arjan@...ux.intel.com>,
"Jiri Kosina" <jkosina@...e.cz>,
"LKML" <linux-kernel@...r.kernel.org>, <agospoda@...hat.com>,
"Ronciak, John" <john.ronciak@...el.com>,
"Allan, Bruce W" <bruce.w.allan@...el.com>,
"Graham, David" <david.graham@...el.com>, <kkiel@...e.de>,
<tglx@...utronix.de>, <chris.jones@...onical.com>,
<arjan@...ux.jf.intel.com>
Subject: RE: e1000e NVM corruption issue status
Krzysztof Halasa wrote:
> But... do you really have a flash chip there? I think it's more about
> EEPROM (a serial usually 8-pin small chip, keeping the MAC address and
> hardware configuration). Flash chips are used for diskless booting
> (though corrupting them can make the machine unbootable of course).
>
> Sure, writing to a parallel flash chip is easy, much easier than to
> serial EEPROM.
ICH 8/9/10 machines with Intel gigabit part integrated (82566/82567)
share the system Flash space with all the other system devices, BIOS,
etc. The gigabit region is the currently only "unprotected" region I
know of. It is never directly memory mapped, but the registers that
program to it are memory mapped from our BAR1, like Tim said, possibly
only requiring an errant write of a few bits of ones, to erase it (I've
been trying to confirm that)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists