No subject


Sun Jan 27 20:46:20 CET 2008


&gt; on LAN bit in the EEPROM is set *(which it is)*.<br><br></div>You could try changing this bit in the EEPROM before running<br>coreboot and see if you get different results from the PCI scan.<br><div class="Ih2E3d"><br>
<br>&gt; When the LAN controller is in Wake on LAN mode:<br>&gt; ? The LAN controller scans incoming packets for a Magic Packet and<br>&gt; asserts the PME# signal for 52 ms when a one is detected in Wake on<br>&gt; LAN mode.<br>
<br>..<br></div><div class="Ih2E3d">&gt; ? The PCI Configuration registers are accessible to the host *(this<br>&gt; is what I&#39;m looking for!!)*.<br><br></div>Right, and this says that they are accessible even when the NIC is in<br>
WoL mode.<br><div class="Ih2E3d"><br><br>&gt; So, if this is correct I think I was right in saying the nic seemed<br>&gt; like it was powered off?? At this point I need to figure out how to<br>&gt; assert a PME# signal to wake up the nic. Maybe from the Power<br>
&gt; Managment Control register??<br><br></div>Note that PME# is asserted by the NIC. Ie. PME# is considered an<br>output from the NIC. Remember that Wake on LAN means that the NIC<br>wakes up the computer if a special packet is received.<br>
<br>I&#39;m afraid I don&#39;t think this is causing the problem you&#39;re seeing.<br>:\<br><font color="#888888"><br><br>//Peter<br></font><div><div></div><div class="Wj3C7c"><br>--<br>coreboot mailing list<br><a href="mailto:coreboot at coreboot.org">coreboot at coreboot.org</a><br>
<a href="http://www.coreboot.org/mailman/listinfo/coreboot" target="_blank">http://www.coreboot.org/mailman/listinfo/coreboot</a><br></div></div></blockquote></div><br>

------=_Part_742_15635457.1202240992449--



More information about the coreboot mailing list