Date: Wed, 29 Dec 2004 14:46:03 +0000 From: Peter Edwards <peadar.edwards@gmail.com> To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: current@freebsd.org Subject: Re: fxp EEPROM checksum mismatch in recent -CURRENT Message-ID: <34cb7c840412290646f4392bd@mail.gmail.com> In-Reply-To: <xzpwtv1te7n.fsf@dwp.des.no> References: <xzpu0qa2pzi.fsf@dwp.des.no> <34cb7c840412290444497d2dd7@mail.gmail.com> <xzpwtv1te7n.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Actually, looking at: http://www.intel.com/technology/IAPC/downloads/pm1_1.pdf If I'm reading it right, the delays for each state change need to be implemented as per the "minimum system software guaranteed delays" column in table 18 (in section 5.6.1, on page 50) I'll fix up the patch to implement this, and post it for review if no one gets there before me. On Wed, 29 Dec 2004 14:40:28 +0100, Dag-Erling Sm=F8rgrav <des@des.no> wrot= e: > Peter Edwards <peadar.edwards@gmail.com> writes: > > Tracing further, it looks like on waking up from D3 into D0, the fxp > > device needs some time to settle, or the config write to restore the > > BAR doesn't "take". That explains why it works if it's dragged in from > > the loader: the device probes without ever going to sleep. >=20 > That explains why the problem disappeared when I compiled fxp into the > kernel. Great detective work! I'll test your patch and let you know > if it works for me. >=20 > DES > -- > Dag-Erling Sm=F8rgrav - des@des.no >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34cb7c840412290646f4392bd>