Sun Dec 9 17:34:17 CET 2012
"In the LAN controller the D0 state is partitioned into two substates, D0
Uninitialized (D0u) and D0 Active (D0a). [...] Initialization of the CSR,
Memory, or I/O Base Registers in the PCI Configuration space switches the
LAN controller D0u state to the D0a state."
"The integrated LAN controller will be disabled if no Platform LAN Connect
component is detected (See Section 184.108.40.206)."
On Feb 5, 2008 11:44 AM, Peter Stuge <peter at stuge.se> wrote:
> On Tue, Feb 05, 2008 at 10:51:39AM -0500, joe at smittys.pointclark.netwrote:
> > So I found this in the ICH4 datasheet:
> > The LAN controller enters Wake on LAN mode after reset if the Wake
> > on LAN bit in the EEPROM is set *(which it is)*.
> You could try changing this bit in the EEPROM before running
> coreboot and see if you get different results from the PCI scan.
> > When the LAN controller is in Wake on LAN mode:
> > ? The LAN controller scans incoming packets for a Magic Packet and
> > asserts the PME# signal for 52 ms when a one is detected in Wake on
> > LAN mode.
> > ? The PCI Configuration registers are accessible to the host *(this
> > is what I'm looking for!!)*.
> Right, and this says that they are accessible even when the NIC is in
> WoL mode.
> > So, if this is correct I think I was right in saying the nic seemed
> > like it was powered off?? At this point I need to figure out how to
> > assert a PME# signal to wake up the nic. Maybe from the Power
> > Managment Control register??
> Note that PME# is asserted by the NIC. Ie. PME# is considered an
> output from the NIC. Remember that Wake on LAN means that the NIC
> wakes up the computer if a special packet is received.
> I'm afraid I don't think this is causing the problem you're seeing.
> coreboot mailing list
> coreboot at coreboot.org
Content-Type: text/html; charset=ISO-8859-1
More information about the coreboot