Re: fxp EEPROM checksum mismatch in recent -CURRENT

From: Peter Edwards <peadar.edwards_at_gmail.com>
Date: Wed, 29 Dec 2004 14:46:03 +0000
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ørgrav <des_at_des.no> wrote:
> Peter Edwards <peadar.edwards_at_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.
> 
> 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.
> 
> DES
> --
> Dag-Erling Smørgrav - des_at_des.no
>
Received on Wed Dec 29 2004 - 13:46:04 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:25 UTC