Hello!
Nico you said here, "Also, generally, you need a build of FSP with
debugging enabled. The  public builds usually are not."

I agree that the public builds usually are not so enabled. What would
need to be done to enable such a function?

Obviously to further dig into these issues, I'm going to need to be
more involved, but, ah, that's not doable this month.
-----
Gregg C Levine gregg.drwho8@gmail.com"This signature fought the Time
Wars, time and again."
On Sat, Feb 9, 2019 at 7:25 AM Nico Huber <nico.h@gmx.de> wrote:
>
> Hi Zvika,
>
> On 09.02.19 12:23, Zvi Vered wrote:
> > I noticed that starting from version 4.9, I can set the debug level of FSP.
> >
> > I downloaded  FSP for Bay trail and used Intel's BCT to modify it.
> > But coreboot hangs after calling to the FSP binary.
> >
> > How can I use the "FSP debug level" ?
>
> This option is only implemented for the Broadwell-DE FSP. I've pushed a
> patch to move it accordingly[1], sorry for the confusion.
>
> Also, generally, you need a build of FSP with debugging enabled. The
> public builds usually are not.
>
> Nico
>
> [1] https://review.coreboot.org/c/coreboot/+/31300
> _______________________________________________
> coreboot mailing list -- coreboot@coreboot.org
> To unsubscribe send an email to coreboot-leave@coreboot.org
_______________________________________________
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-leave@coreboot.org