Re: [coreboot] coreboot Digest, Vol 165, Issue 9

Voted, no one tried to run me over this time. daytime definitely helps, though i did wind up talking to a drunken schizophrenic, but he wasn't rude to me (just other people).  and i'm definitely keeping this signature line, how else can i keep more promises than i've made?

"Better dead than red." Famous conservative saying.....

6. Nov 2018 15:43 by [e-mail] :
> Send coreboot mailing list submissions to
> > [e-mail]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> > https://mail.coreboot.org/mailman/listinfo/coreboot https://mail.coreboot.org/mailman/listinfo/coreboot
>
> or, via email, send a message with subject or body 'help' to
> > [e-mail]
>
> You can reach the person managing the list at
> > [e-mail]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of coreboot digest..."
>
> Today's Topics:
> Re: Hardware diagnostic (yanvasilij yan)
> New Defects reported by Coverity Scan for coreboot
> (> [e-mail] > )
> Re: How to get correct memory params for FSP (Alex Feinman)
> Re: How to get correct memory params for FSP (R S)
> Re: How to get correct memory params for FSP (Alex Feinman)
> Can we please remove the FSP TempRamInit option (where
> applicable) (Nico Huber)
> Re: How to get correct memory params for FSP (R S)
> Use VBIOS from vendor's original bin file (Zvi Vered)
> Re: How to get correct memory params for FSP (Alex Feinman)
> Re: Can we please remove the FSP TempRamInit option (where
> applicable) (Lance Zhao)
> Re: Use VBIOS from vendor's original bin file (Mike Banon)
>
> Message: 1
> Date: Tue, 6 Nov 2018 16:51:49 +0500
> From: yanvasilij yan <> [e-mail] > >
> To: > [e-mail] 
> Cc: > [e-mail] > , > [e-mail] 
> Subject: Re: [coreboot] Hardware diagnostic
> Message-ID:
>    <> CAATv5Wb7yg3u6OLJjXr5E_iCXSn_2uXeB58_Fo-=[e-mail] > >
> Content-Type: text/plain; charset="utf-8"
>
> Thank lot too all!
>
> Sory for last response!
>
> You were right, the problem was in power up sequence. After fixing all
> become correct. The 0x8086/0x0000 device disappeared, and payload
> succesfuly downloaded.
>
> Peter Stuge,  thank you for detailed comments!
>
> Nico Huber, thank you for active participation!
>
> ??, 28 ???. 2018 ?. ? 4:18, Nico Huber <> [e-mail] > >:
> > On 10/28/18 12:25 AM, Peter Stuge wrote:
> > > Why are there no RAM regions? I don't know.
> >
> > Quite simple, because the code that adds them is tied to 8086:0f00.
> > > > nico_h in the IRC chat noticed that in non-working board appears a
> >
> > starnge
> > > > device with vid/did PCI: 00:00.0 [8086/0000].
> > >
> > > The 0000 is a HUGE red sign, screaming to be thoroughly investigated.
> > >
> > > This also hints that the power up changes may be the problem.
> >
> > I agree, but note that in the datasheet (or EDS at least), the DID is
> > not read-only. A strap (that I coudn't find more about) is supposed to
> > set the initial value plus there is a message mentioned (to be sent to
> > sth. I didn't look into) that may change it.
> >
> > So alternatively to diagnosing the hardware changes, you could also
> > follow the bread crumbs in the documentation.
> >
> > Nico